Re: Distribution Agent Issue

Hi Paul:

Job owner is distributor_admin. Should I still change the owner to sa? And
yes, sp_browsereplcmds is returning data so I am not sure why distribution
agent is not pushing data.

I have second scenario where on another server Log Reader shows the status
as running but it doesnt read any transactions from the publisher's
transaction log. Any comments on this one?

Thanks in advance.

"Paul Ibison" wrote:

> Mark,
> check to see if the job owner is a domain user, and if so please change to
> sa.
> Also check to see that the log reader agent has started and that
> sp_browsereplcmds returns some rows.
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
>
.

Relevant Pages

  • Re: Replication and Log Size problems
    ... The log reader agent is intelligent enough to know the LSN it last read and marked as replicated, and then starts reading from there ... Looking for a SQL Server replication book? ... >>Looking for a SQL Server replication book? ...
    (microsoft.public.sqlserver.replication)
  • Re: The process is running and is waiting for a response from one of the backend pro
    ... stopping and restarting the SQL Server Agent ... > log reader agent is happy. ... > one of the backend processes. ...
    (microsoft.public.sqlserver.replication)
  • Re: Distribution Agent Issue
    ... check to see if the job owner is a domain user, and if so please change to ... Also check to see that the log reader agent has started and that ... Paul Ibison SQL Server MVP, ...
    (microsoft.public.sqlserver.replication)
  • Re: Queue reader agent aborting
    ... > For me the only reliable way to stop the queue reader and log reader ... agents is to stop the SQL Server agent. ... > Looking for a SQL Server replication book? ...
    (microsoft.public.sqlserver.replication)
  • Re: SQL 2000 SP3 and NT4 Domain Issues
    ... to set the job owner to sa. ... Jasper Smith (SQL Server MVP) ... "Mike Mattix" wrote in message ... > the second time I just stopped and restarted SQL Server (I was remote the ...
    (microsoft.public.sqlserver.security)