|
Hi Jude,
It is sort of difficult for me to visualize exactly
what is going on with the description you gave previously (or any kind of
description that you can possibly provide over the newsgroup) but I would guess
that the subscriber SQL Server Agent service account was somehow added to the
publication access list of the publication on the DMZ. If this is the case then
you will likely see the kind of error message that you saw when
browsing the publication properties through the UI (which also enumerates
entries in the publication acces list). To find out, select from the
MSpublication_access table in the distribution database and see
if the account for your Subscriber's SQL Server Agent service
account shows up. If so, manually removing the row will likely resolve
the issue for you.
-Raymond
Raymond,
Thank you for
this answer, I am going to check to make sure I have my alternate snapshot
folder set as you suggest.
If I may impose, when browsing
for the publication on the DMZ to setup an anonymous pull subscription, why
would I receive an error message about the domain account on the Subscriber
that runs the SQL Server Agent service?
Why is it referring to this
account at all?
Certainly both servers Sql
Server agent accounts do not have to be the same, especially when one of the
servers is out on the net & not even on the domain?
Any light you can shed on this
will be greatly appreciated.
Thanx!!!!
--
Jude
Hi Jude,
While using nosync subscription is a perfectly
valid option, the problem that your experienced seems to be the
kind that is relatively straightforward to resolve. If I
understand the situation correctly, you have manually copied the
snapshot files to a different location on the subscriber and attempted to
apply the snapshot from the new location via the use of the alternate
snapshot folder property of the pull subscription. One non-intuitive
quirk that typically catches people off-guard is to set the alternate
snapshot location directly to where the snapshot files are rather
than to where the unc or ftp folder is. That is, you
need to have the
<unc|ftp>\<Publisher>_<PublisherDB>_<Publication>\<timestamp>\<snapshot
files> folder structure underneath your alternate snapshot folder.
So, if you manually copy the snapshot files around, you would need to
recreate the same folder structure that I mention previously in your
target location and then point the alternate snapshot folder to the "root"
of that sub-structure. I would be interested to know if your scenario has
more twists than what I expected.
-Raymond
At this point I'll try
anything!!!!!!!!!!
What do you mean?
Where do I try a nosync?
--
JUDE
can
you try a nosync?
--
Hilary Cotter
Looking for a SQL
Server replication book?
http://www.nwsu.com/0974973602.html
Looking
for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"JLS"
<jlshoop@xxxxxxxxxxx>
wrote in message
news:ebk7Zx49FHA.1996@xxxxxxxxxxxxxxxxxxxx...
I
tried yet another approach....
I pulled the initial snapshot
folder off the publisher & put it on the
subscriber. In
the subscription properties, I told it to look in this
folder on the
subscriber, but I get an error message that the process could
not
read the file.
I'm just trying everything & I think I'm down
to my problem has to do with
the initial snapshot. PLEASE
shove me in the right direction.....
"JLS" <jlshoop@xxxxxxxxxxx> wrote in
message
news:OvacGx39FHA.2616@xxxxxxxxxxxxxxxxxxxx...
I have setup everything from my domain to the dmz following the document
from Replication Answers.com "Replication Across Non-Trusted Domains
or
Using the Internet"
When setting up the anonymous
pull subscription, browsing for the DMZ
publication, I see the DMZ
server (Publisher) but when I click the (+) to
view publications I
am receiving the error message;
"Could not obtain information
about Windows NT group / user 'DOMAIN
NAME/SQLAdministrator'
"
This is the account that runs my Sql Server Agent of the sql
server in the
domain (The Subscriber)
I don't want to
use this account, the DMZ server is a part of the
domain!!!! I
have setup a sql account on both the domain sql server & the
dmz
sql server.
What am I missing? Where would it be
retrieving this account?
I feel like I am so close.
I was actually able to create a subscription
by using Hilary's book
& scripts from QA (But couldn't get the Agent to
start -
Start/Stop Agent were grayed out)
--
JLS
|
