Saturday, February 25, 2012

Replication LogReader

Once i configured the replication throwing the following error on logreader

2007-02-08 16:47:39.641 Status: 0, code: 1007, text: 'Another logreader agent for the subscription(s) is running or the server is working on a previous request by the same agent.'.
2007-02-08 16:47:39.641 Another logreader agent for the subscription(s) is running or the server is working on a previous request by the same agent.
2007-02-08 16:47:39.641 Status: 0, code: 22037, text: 'The last step did not log any message!'.

Please let me know if you have any solutions to fix this issue.

Can you provide more detail about your replication setup?

Gary

|||My guesss is you have two logreader agent jobs running against the same publisher db. Stop one of the jobs, then delete/disable it, you should have only one logreader agent job per published database. If you do not have two jobs, then somehow the logreader agent process when you ran it the first time did not shut down properly. THe safest way to clear this issue is to restart the SQL Server service on the distributor machine.|||

I have multiple publisher and multiple subscriber for same db.when i configure it this way it is thorowing the above error?

No comments:

Post a Comment