August 23, 2018 at 12:49 pm
Hello,
I have dropped all subscriptions and publications and have ran sp_removedbreplication on publication and subscription servers to make sure there are no lingering subscriptions or publications. I am getting the below error from the subscriber db server? I can't figure out where this is coming from and how to solve this.
Also, this started happening after I restored a current copy of production db on the subscriber db server. If that helps.
Any ideas? Appreciate it.
Replication-Replication Transaction-Log Reader Subsystem: agent MSSQLREPCL-uosdb_replication-3 failed. The process could not execute 'sp_repldone/sp_replcounters' on 'MSSQLREPCL'.
August 23, 2018 at 1:10 pm
JP10 - Thursday, August 23, 2018 12:49 PMHello,
I have dropped all subscriptions and publications and have ran sp_removedbreplication on publication and subscription servers to make sure there are no lingering subscriptions or publications. I am getting the below error from the subscriber db server? I can't figure out where this is coming from and how to solve this.Also, this started happening after I restored a current copy of production db on the subscriber db server. If that helps.
Any ideas? Appreciate it.
Replication-Replication Transaction-Log Reader Subsystem: agent MSSQLREPCL-uosdb_replication-3 failed. The process could not execute 'sp_repldone/sp_replcounters' on 'MSSQLREPCL'.
That looks like that log reader agent is still running - did you check for any SQL Server Agent replication jobs?
Sue
August 23, 2018 at 1:32 pm
Sue,
Thanks for the tip may have solved the problem. The problem looks like that SQL Log reader agent job was the culprit. But, I disabled it before and it was still creating the errors. So, I deleted it and now the errors are gone (I scripted it out and saved off the job before deleting it). I have the Log reader on subscriber db server as well because I daisy chain my replication. So, I have a Prod > Subscriber then Subscriber has a publication as well > another subscriber. It was the 1st subscriber that had the Log reader that was causing the errors.
Thanks,
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply