Could not execute sp_replcmds
Hello,
I am setting up transactional replication on a SQL 2008 publisher and use a separate SQL 2008 distributor. Reviewing Replication Monitor, I see the following errors:
Error messages:
· The process could not execute 'sp_replcmds' on 'ServerName'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20011)
Get help: http://help/MSSQL_REPL20011· Could not obtain information about Windows NT group/user 'domain\username', error code 0x2. (Source: MSSQLServer, Error number: 15404)
Get help: http://help/15404· The process could not execute 'sp_replcmds' on 'ServerName'. (Source: MSSQL_REPL, Error number: MSSQL_REPL22037)
Get help: http://help/MSSQL_REPL22037I attempt to execute sp_replcmds on the publisher via SSMS and get the highlighted error back. So I don't think this has anything to do with the Log Agent job permissions. It's happening on the distributor AND publisher.
My issue is that the user “domain\username” should not be anywhere on our servers, though it is a valid login in the domain. I looked at the groups of which this user is a member and the groups is not any of our security groups on the SQL Server. I checked all the local groups on the server and this user isn’t a member of any group nor is any group he’s a member of a member of any local group. So I’m pretty baffled with what’s going on. I dropped and re-created the replication streams a couple times and this error comes up each time. What's also interesting is that when I delete the publication, I get that same highlighted error.
Does anyone know what’s going on? I have since upgraded SQL 2008 to SP1 and the error persists.
Thanks so much,
Melanie
Answers
Hi,
What’s login account that you currently use to connect to SQL Server? Please make sure this login has sysadmin role. There is another similar thread:
http://social.msdn.microsoft.com/forums/en-US/sqlreplication/thread/52601866-23d6-4150-bcf5-dfcad24f43c3/
If there are any more questions, please let me know.
Thanks.
***Xiao Min Tan***Microsoft Online Community***- Marked As Answer byChunSong Feng -MSFTMSFT, ModeratorMonday, November 16, 2009 3:28 AM
- Thanks everyone. The domain account used for the SQL Services on my server is using an account that is authenticated to the AD. It's the same account used on probably 10 other servers, which are all functioning well. The account wasn't locked out (all other servers using account work fine).
I am attempting to setup replication on two domain servers - two new virtual machines using a distributor that's a distributor for other replication streams in the environment as well.
What's interesting is that this alone worked (suggested by a work colleague):
ALTER AUTHORIZATION ON DATABASE::<database name> to sa
where sa is the dbowner.- Marked As Answer byXiao-Min Tan – MSFTMSFT, ModeratorMonday, November 16, 2009 3:26 AM
- Proposed As Answer byXiao-Min Tan – MSFTMSFT, ModeratorTuesday, November 10, 2009 1:44 AM
All Replies
- can you see the step by step setup process for replicaiton.
http://vinay-thakur.spaces.live.com/default.aspx?_c01_BlogPart=blogentry&_c=BlogPart&handle=cns!645E3FC14D5130F2!592
HTH
Vinay
Vinay Thakur http://vinay-thakur.spaces.live.com/ http://twitter.com/ThakurVinay - Thanks for your pointer, Vinay. For the most part, I followed the steps as outlined on your page's SQL Server 2005 transactional replication link, but for SQL 2008.
Hi,
What’s login account that you currently use to connect to SQL Server? Please make sure this login has sysadmin role. There is another similar thread:
http://social.msdn.microsoft.com/forums/en-US/sqlreplication/thread/52601866-23d6-4150-bcf5-dfcad24f43c3/
If there are any more questions, please let me know.
Thanks.
***Xiao Min Tan***Microsoft Online Community***- Marked As Answer byChunSong Feng -MSFTMSFT, ModeratorMonday, November 16, 2009 3:28 AM
- Ur domain account is not getting authenticated at AD.
are u trying to setup replication on domain machines or local machine (on ur local laptop or virtual machine).
Mohd Sufian www.sqlship.wordpress.com Please mark the post as Answered if it helped. - He have the same issue occasionally.
Always turns out that our system admin account, which replication is running under, is locked. As soon as the account is unlocked, the error goes away. Still not sure why the account is getting locked, but thats another issue :-) - Thanks everyone. The domain account used for the SQL Services on my server is using an account that is authenticated to the AD. It's the same account used on probably 10 other servers, which are all functioning well. The account wasn't locked out (all other servers using account work fine).
I am attempting to setup replication on two domain servers - two new virtual machines using a distributor that's a distributor for other replication streams in the environment as well.
What's interesting is that this alone worked (suggested by a work colleague):
ALTER AUTHORIZATION ON DATABASE::<database name> to sa
where sa is the dbowner.- Marked As Answer byXiao-Min Tan – MSFTMSFT, ModeratorMonday, November 16, 2009 3:26 AM
- Proposed As Answer byXiao-Min Tan – MSFTMSFT, ModeratorTuesday, November 10, 2009 1:44 AM


