February 20, 2009 at 9:24 am
Hi, logreader on transactional replication failed with this error
Another logreader agent for subscription is running. Before I kill the replication I would like to know what could be the causes and how to fix it without deleting publications/subscriptions.
Thank you in advance, LL
February 20, 2009 at 12:32 pm
How many subscribers do you have using that log reader?
Take a look at the log reader job under SQL Server Agent, what's its status? I've seen this before, were that logreader appears to be stopped under the Replication Monitor, but still running as a job. Try stopping the job, refresh to make sure it's stopped, and then start it again.
February 20, 2009 at 1:06 pm
llokshin (2/20/2009)
Hi, logreader on transactional replication failed with this error
What error?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 20, 2009 at 3:17 pm
didn't help, had to drop all subscriptions and publications. There is more to it. Some jobs started to hang too well past their next schedule run. I restarted Sql Server Agent and it helped to start some of the jobs but not all of them. All of it started to happen after installation of the latest microsoft security patch of our clustered environment. There were many errors related to it in event viewer. Also Red Gate backups started to hang. Tonight we will reinstall it and see if it changes anything,
thank you,
LL
February 20, 2009 at 3:33 pm
You require to start the Job under the SQL Server Agent. You donot need to remove the existing replication.
Just go to SQL Server Agent (or start it) --> Check the Jobs --> Start the Job for respective publications. Then you reinitialize the publication and check the monitor.
Hope this should resolve you problem
Thapa
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply