December 21, 2016 at 12:25 am
Getting error on replication, log reader agent:
Log reader fails with “The process could not execute ‘sp_replcmds’ on <DB01> ” error
Needs to be sorted asap, has anyone come across this one?
Thanks in advance.
...
December 21, 2016 at 12:36 am
HappyGeek (12/21/2016)
Getting error on replication, log reader agent:Log reader fails with “The process could not execute ‘sp_replcmds’ on <DB01> ” error
Needs to be sorted asap, has anyone come across this one?
Thanks in advance.
Any errors in the SQL Server log or Windows Event Log?
😎
December 21, 2016 at 12:42 am
Does the database have an owner if so which account is it.
December 21, 2016 at 3:14 am
Many thanks for the replies, database owner is sa, there is an entry in event viewer which suggests the login may have changed but not sure how to check or correct, issue ongoing, advice really appreciated.
...
December 21, 2016 at 10:26 am
HappyGeek (12/21/2016)
Many thanks for the replies, database owner is sa, there is an entry in event viewer which suggests the login may have changed but not sure how to check or correct, issue ongoing, advice really appreciated.
It's hard to say without seeing the error message. So it's just guesses at this point but does the log reader agent have access to the distributor? Have you checked the logs wherever the distributor is?
What the value for MaxCmdsInTran parameter for the log reader agent?
What service packs, updates have been applied to the instance?
Sue
December 21, 2016 at 9:28 pm
This was removed by the editor as SPAM
December 22, 2016 at 10:59 am
JasonClark (12/21/2016)
The Error message come when database not having a valid owner, or the SQL Server unable to identify the owner of the database. You may run this statement:1USE PublishedDatabase
2GO
3EXEC sp_changedbowner 'sa'
4GO
This will help you to change the database ownership. Once this is changed it will start working.
ownership not a problem, even changing, did that, ultimately had to demolish the lot and start again, must be a new feature!
...
December 23, 2016 at 4:12 am
I got this error in two cases.
1. Db ownership (as other people said sp_changedbowner 'sa' - do not use GUI to do this).
2. Permission issues
Please check first what user is used to run logreader (Properties of Publication). You either run on SQL Service account (which will be service account of Distributor) or other Domain account. Anyway you need to check if that user has permissions to run that proc on publisher.
BartL
Replication Blog
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply