hi,

I am working on sql server 2000 replication. One of our
sql servers has multipul publications that push out to
several subscribers, and some of the subscribers are the
database on the same publisher server. and I've
encountered the following failures with only one of its
publications. This particular publication is from one
database push to another database on this same publisher
server. And we have a seperate server to act as
distributor for all server's replications:

----------
Executed as user: domain_name\distributor_server_name.
Replication-Replication Distribution Subsystem: agent
distribution_agent_name failed. Login failed for user 'NT
AUTHORITY\ANONYMOUS LOGON'. The process could not connect
to Distributor 'distributor_server_name'. The step failed.
----------

I've verified all login configurations on the publisher
and subscriber (in this case, they are of the same
server), and the distributor. All correct.

what process/agent's logon account is this error complaint
about (user 'NT AUTHORITY\ANONYMOUS LOGON')?

many thanks!!

JJ

Is builtin\administrators part of your system administrators role? It sounds
like someone has removed this group.

What account is your SQL Server running under as well?

--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"JJ Wang" <anonymous (AT) discussions (DOT) microsoft.com> wrote

thanks Hilary.

builtin\administrators is part of our system
administrators role. and our sql servers are running
under their own domain account which is also system admin
role on the servers.

the wierd thing is that only this one publication is
failing, rest of the publications from the same server are
working fine.

JJ

what sort of a publication is this? Transactional? Transactional with
immediate/queued updating?

--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"JJ Wang" <anonymous (AT) discussions (DOT) microsoft.com> wrote

hi Hilary,

thanks for all your help. it's resolved. the problem was
that we set the dist-agent to run on the publisher instead
of on our distributor. and this setting is buggy because
it uses domain account to authenticate to the remote
server.

we set the agent to run on the distributor and it has been
running like a charm.

it's transactional dist.

thanks again for all your help!!

JJ