Thanks for getting back to me so quickly, Hilary.
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 see if there's a conflict of some sort. If not, then I'll push it off to
"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...
> > 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
> >
>
>
