Re: URGENT: distribution agent failure: NT AUTHORITY\ANONYMOUS LOGON

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Hilary Cotter (hilary.cotter_at_gmail.com)
Date: 12/25/04 

Date: Fri, 24 Dec 2004 19:07:38 -0500

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@discussions.microsoft.com> wrote in message 
news:27c201c4ea0b$b39a7300$a401280a@phx.gbl...
> 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
>
>>-----Original Message-----
>>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@discussions.microsoft.com> wrote in
> message
>>news:259601c4e95f$785ef330$a401280a@phx.gbl...
>>> 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
>>
>>
>>.
>>

Relevant Pages

  • Re: Single point of failure
    ... RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. ... Looking for a SQL Server replication book? ... "Hilary Cotter" wrote: ...
    (microsoft.public.sqlserver.replication)
  • Re: Single point of failure
    ... "Hilary Cotter" wrote: ... Looking for a SQL Server replication book? ... publisher and subscriber to each other and to the other publishers ...
    (microsoft.public.sqlserver.replication)
  • Re: Implementation of Replication en SQL SERVER 2K
    ... Hilary Cotter ... Looking for a SQL Server replication book? ... "Alvaro Rebolledo" wrote in ... >> Looking for a SQL Server replication book? ...
    (microsoft.public.sqlserver.replication)
  • Re: Article Defaults --> cant change
    ... >> Hilary Cotter ... >> Looking for a SQL Server replication book? ... >>> We don't want data deleted on the subscribers when data is deleted on ...
    (microsoft.public.sqlserver.replication)
  • Re: Merge replication gives "Invalid date format" during merge step
    ... Hilary Cotter wrote: ... If I remove the publication, remove the TimeToAnswer column, then ... The SQL Server is installed using the US CD (I don't think there's a UK ...
    (microsoft.public.sqlserver.replication)