Cannot create subscriber on MSDE2000

I am very new at SQL replication. I set up a publication and distributor at
our SQL 2000 server. All went fine. Now I am trying to create a laptop
subscriber to use (I think) an anonymous subscription. I setup the laptop
with MSDE 2000 SP3. I now want to create a subscription while connected to
the network. I want to use the Windows Syncronizer to synch the database.
I cannot find out how to create the initial subscription database on the
laptop. When I try to manually configure the Windows Synchronizer, I get an
error "The process could not access database 'MCFIData' on server 'LAPTOP1'.
Database is invalid or cannot be accessed"
Well DUH...I was told that it would be created if it does not exist. Any
help would be appreciated. Thanks.
David
Ignore this. I did not have the SQL Agent running on the laptop with MSDE
2000 SP3. I'm not sure why, but there was no prompt for this option when I
installed MSDE. Also there was no instruction to do so on the documentation
for setting up MSDE to be a subsriber!
David
"David" <dlchase@.lifetimeinc.com> wrote in message
news:elqk$rE%23FHA.1248@.TK2MSFTNGP14.phx.gbl...
>I am very new at SQL replication. I set up a publication and distributor
>at our SQL 2000 server. All went fine. Now I am trying to create a laptop
>subscriber to use (I think) an anonymous subscription. I setup the laptop
>with MSDE 2000 SP3. I now want to create a subscription while connected to
>the network. I want to use the Windows Syncronizer to synch the database.
>I cannot find out how to create the initial subscription database on the
>laptop. When I try to manually configure the Windows Synchronizer, I get
>an error "The process could not access database 'MCFIData' on server
>'LAPTOP1'. Database is invalid or cannot be accessed"
> Well DUH...I was told that it would be created if it does not exist. Any
> help would be appreciated. Thanks.
> David
>

Cannot connect to subscriber

Setup:
- SQL2000 SP3 running on Windows2000 servers.
I have a merge replication running between three identical servers. Two of
the servers, the publisher and subscriber1, receive data from different
sources and are synced every day at 4am. Subscriber2 is a query server only
and is updated by the publisher at 5am.
Replication has been running flawlessly since we upgraded everything nearly
a year ago. This morning the merge agent for Subscriber1 failed with the
following error (XXXX is the server name):
"The process could not connect to Subscriber 'XXXX'.
(Source: XXXX (Agent); Error number: 20084)"
"Cannot generate SSPI context
(Source: XXXX (Data source); Error number: 11004)"
Subscriber2 succeeded. Nothing has changed on the servers, and the logon
credential are the same for each.
I'm at a loss here. Anyone have any idea what might be happening and how to
fix it?
Thanks,
John Steen
There are some patches which seem to be causing this problem. The first
thing I would do is try to connect to the problem machine using SQL
Authentication. This might indicate that someone has changed the server from
mixed authentication to windows. Then try Windows - do you get the SSPI
error there too?
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
"John Steen" <moderndads(nospam)@.hotmail.com> wrote in message
news:ABA30CE3-CA41-481E-9195-35482227D318@.microsoft.com...
> Setup:
> - SQL2000 SP3 running on Windows2000 servers.
> I have a merge replication running between three identical servers. Two
of
> the servers, the publisher and subscriber1, receive data from different
> sources and are synced every day at 4am. Subscriber2 is a query server
only
> and is updated by the publisher at 5am.
> Replication has been running flawlessly since we upgraded everything
nearly
> a year ago. This morning the merge agent for Subscriber1 failed with the
> following error (XXXX is the server name):
> "The process could not connect to Subscriber 'XXXX'.
> (Source: XXXX (Agent); Error number: 20084)"
> "Cannot generate SSPI context
> (Source: XXXX (Data source); Error number: 11004)"
> Subscriber2 succeeded. Nothing has changed on the servers, and the logon
> credential are the same for each.
> I'm at a loss here. Anyone have any idea what might be happening and how
to
> fix it?
> Thanks,
> John Steen
>
|||Thanks for getting back to me so quickly, Hilary.
All three servers are using mixed authentication and identical credentials,
and there have been no patches or updates applied. I ran the merge agent for
Subscriber1 this morning manually and it succeeded. I did the same thing for
Subscriber2 but it failed. A second attempt succeeded. So it doesn't seem
to be an authentication issue.
We have a BU Exec SQL agent that does a differential backup at the same time
the merge agents run, so I'm going to to change the time that the agents run
to see if there's a conflict of some sort. If not, then I'll push it off to
our telecom people.
Thanks,
John
John Steen
remove (nospam) from e-mail address to send me a message
"Hilary Cotter" wrote:

> There are some patches which seem to be causing this problem. The first
> thing I would do is try to connect to the problem machine using SQL
> Authentication. This might indicate that someone has changed the server from
> mixed authentication to windows. Then try Windows - do you get the SSPI
> error there too?
> --
> 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
> "John Steen" <moderndads(nospam)@.hotmail.com> wrote in message
> news:ABA30CE3-CA41-481E-9195-35482227D318@.microsoft.com...
> of
> only
> nearly
> to
>
>