December 18, 2015 at 7:29 am
When I try and start the Log Reader Agent for Transaction Push REplication I get the following error:
The process could not execute 'sp_replcmds' on 'ASSET2629\PUBLISHER'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20011)
Get help: http://help/MSSQL_REPL20011
Cannot execute as the database principal because the principal "dbo" does not exist, this type of principal cannot be impersonated, or you do not have permission. (Source: MSSQLServer, Error number: 15517)
Get help: http://help/15517
The process could not execute 'sp_replcmds' on 'ASSET2629\PUBLISHER'. (Source: MSSQL_REPL, Error number: MSSQL_REPL22037)
Get help: http://help/MSSQL_REPL22037
I missed something.
I googled but I did not find a solution.
Any ideas?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
December 18, 2015 at 8:03 am
Welsh Corgi (12/18/2015)
The process could not execute 'sp_replcmds' on 'ASSET2629\PUBLISHER'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20011)
Get help: http://help/MSSQL_REPL20011
Cannot execute as the database principal because the principal "dbo" does not exist, this type of principal cannot be impersonated, or you do not have permission. (Source: MSSQLServer, Error number: 15517)
Get help: http://help/15517
The process could not execute 'sp_replcmds' on 'ASSET2629\PUBLISHER'. (Source: MSSQL_REPL, Error number: MSSQL_REPL22037)
Get help: http://help/MSSQL_REPL22037
I missed something.
I googled but I did not find a solution.
Any ideas?
I changed permissions for the Log Reader Account and now I get the following error:
Only one Log Reader Agent or log-related procedure (sp_repldone, sp_replcmds, and sp_replshowcmds) can connect to a database at a time. If you executed a log-related procedure, drop the connection over which the procedure was executed or execute sp_replflush over that connection before starting the Log Reader Agent or executing another log-related procedure. (Source: MSSQLServer, Error number: 18752)
I can't find another process that is running.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
December 18, 2015 at 8:08 am
For your original problem, a Google search provided a large number of results. https://www.google.co.uk/?gws_rd=ssl#safe=active&q=%22Cannot+execute+as+the+database+principal+because+the+principal+%22+replication
Check the owner of the Publisher DB - make sure it is a valid account.
For the new issue that you've created - https://www.google.co.uk/?gws_rd=ssl#safe=active&q=%22Only+one+Log+Reader+Agent+or+log-related+procedure+(sp_repldone%2C+sp_replcmds%2C+and+sp_replshowcmds)+can+connect+to+a+database+at+a+time%22
December 18, 2015 at 8:14 am
BrainDonor (12/18/2015)
For your original problem, a Google search provided a large number of results. https://www.google.co.uk/?gws_rd=ssl#safe=active&q=%22Cannot+execute+as+the+database+principal+because+the+principal+%22+replicationCheck the owner of the Publisher DB - make sure it is a valid account.
For the new issue that you've created - https://www.google.co.uk/?gws_rd=ssl#safe=active&q=%22Only+one+Log+Reader+Agent+or+log-related+procedure+(sp_repldone%2C+sp_replcmds%2C+and+sp_replshowcmds)+can+connect+to+a+database+at+a+time%22
Yes. There are a large number of matches on google.
Unfortunately none of the worked.
All of the Database have a sysadmin owner.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
December 18, 2015 at 9:45 am
The log reader is working. Changed from a Domain Account to SA.
Agent 'ASSET2629\PUBLISHER-AdventureWorks2014Pub-MyFirstPublication-ASSET2629\SUBSCRIBER-3' is retrying after an error. 67 retries attempted. See agent job history in the Jobs folder for more details.
Now I can't get Distributer to Subscriber History to work.
Error messages:
The process could not connect to Subscriber 'ASSET2629\SUBSCRIBER'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20084)
Get help: http://help/MSSQL_REPL20084
Login failed for user 'MyDomain\ASSET2629$'. (Source: MSSQLServer, Error number: 18456)
Get help: http://help/18456
There is not a User ASSET2629. I do not know where that came from.
Any ideas?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
December 18, 2015 at 10:16 am
I added the repl_distribution as a user on the subscriber.
No Luck.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
December 20, 2015 at 10:59 pm
Take a look at this article: http://www.sqlservercentral.com/blogs/brian_kelley/2013/04/22/troubleshooting-sql-server-error-15517/
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply