Microsoft Sql Server 2008 Error 15517
Contents |
up Get Your Own Blog If you would like to blog on SQLServerCentral.com then send an email to webmaster@sqlservercentral.com. Contact sql server error 15517 replication the author Please log in or register to contact the author of this
Cannot Find The Principal 'dbo', Because It Does Not Exist Or You Do Not Have Permission.
blog All Blogs All Bloggers on SQL Server Central Feeds Subscribe to this blog Archives for this blog December event id 28005 2013 November 2013 October 2013 September 2013 August 2013 July 2013 June 2013 May 2013 April 2013 March 2013 February 2013 January 2013 December 2012 November 2012 October 2012 September 2012 August error 15517 sql server 2012 2012 July 2012 June 2012 May 2012 April 2012 March 2012 February 2012 January 2012 December 2011 November 2011 October 2011 September 2011 August 2011 July 2011 June 2011 May 2011 April 2011 March 2011 February 2011 January 2011 December 2010 November 2010 October 2010 September 2010 August 2010 July 2010 June 2010 May 2010 April 2010 March 2010 February 2010 January 2010
Principal Dbo Does Not Exist
December 2009 November 2009 October 2009 September 2009 August 2009 July 2009 June 2009 May 2009 April 2009 March 2009 February 2009 January 2009 December 2008 November 2008 October 2008 September 2008 August 2008 July 2008 June 2008 May 2008 April 2008 March 2008 February 2008 January 2008 December 2007 November 2007 October 2007 September 2007 July 2007 June 2007 May 2007 April 2007 March 2007 February 2007 January 2007 December 2006 November 2006 October 2006 September 2006 August 2006 July 2006 June 2006 May 2006 April 2006 March 2006 February 2006 January 2006 December 2005 November 2005 September 2005 July 2005 K. Brian Kelley - Databases, Infrastructure, and Security IT Security, MySQL, Perl, SQL Server, and Windows technologies. Troubleshooting SQL Server Error 15517 Posted on 22 April 2013 Comments Briefcase Print Last weekI had the following error message repeating over and over again in the SQL Server log of one of my servers. It was repeating somuch that the logs were growing very large, very fast: MessageAn exception occurred while enqueueing a message in the target queue. Error: 15517, State: 1. Cannot execute as th
does not exist mssql_repl20011 ★★★★★★★★★★★★★★★ Chris Skorlinski [MSFT]February 26, 20109 Share 0 the process could not execute 'sp_replcmds' 0 LogReader fails with error 15517: 2010-02-25 21:16:35.054 Status: 0, code: 20011, text:
Alter Authorization On Database
‘The process could not execute ‘sp_replcmds' on ‘CHRISSKACER'.'.2010-02-25 21:16:35.056 The process could not execute ‘sp_replcmds' on ‘CHRISSKACER'.2010-02-25 21:16:35.057 Status: 0, http://www.sqlservercentral.com/blogs/brian_kelley/2013/04/22/troubleshooting-sql-server-error-15517/ code: 15517, text: ‘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.'.2010-02-25 21:16:35.058 Status: 0, code: 22037, text: ‘The process could not execute https://blogs.msdn.microsoft.com/repltalk/2010/02/26/logreader-fails-with-cannot-execute-as-the-database-principal-because-the-principal-dbo-does-not-exist/ ‘sp_replcmds' on ‘CHRISSKACER'.'. The SQL Agent was configured to run using ‘ChrisSkAcer\Chris'. In login properties, this account has “system administrator” rights. To eliminate JOB properties or SQL Agent authentication as problem, tried running LogRead.exe from CMD prompt while logged on using the same administrator count. c>logread.exe -Publisher [CHRISSKACER] -PublisherDB [AdventureWorksLT] -Distributor [CHRISSKACER] -DistributorSecurityMode 1 -continuous >>same error. -Connected to Publisher via SSMS and executed LogReader "read" stored proc as ‘sa' sp_replcmds >>same error. -display SQL Server login token (also called Security ID or SID)select * from sys.login_token ChrisSkAcer\Chris0x5EEC29DAFF38CF043B0FFE4AEB030000
-display dbo token in Published databaseUSEhere for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow http://stackoverflow.com/questions/11383145/sql-server-2008-service-broker-tutorial-cannot-receive-the-message-exception the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up SQL Server 2008 Service Broker tutorial — cannot receive the message (exception in transmission_status) up vote 19 down sql server vote favorite 7 I am learning how to use the Service Broker of SQL Server 2008 R2. When following the tutorial Completing a Conversation in a Single Database. Following the Lesson 1, I have successfully created the message types, contract, the queues and services. Following the Lesson 2, I have probably sent the message. However, when trying to receive the message, I get the NULL for the ReceivedRequestMsg instead of the sent content. does not exist When looking at the sys.transmission_queue, the transmission_status for the message says: An exception occurred while enqueueing a message in the target queue. Error: 15517, State: 1. 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. I have installed SQL Server using the Windows login like Mycomp\Petr. I am using that login also for the lessons. Can you guess what is the problem? What should I check and or set to make it working? Edited 2012/07/16: For helping to reproduce the problem, here is what I did. Can you reproduce the error if you follow the next steps? Firstly, I am using Windows 7 Enterprise SP1, and Microsoft SQL Server 2008 R2, Developer Edition, 64-bit (ver. 10.50.2500.0, Root Directory located at C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL_PRIKRYL05\MSSQL). Following the tutorial advice, I have downloaded the AdventureWorks2008R2_Data.mdf sample database, and copied it into C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL_PRIKRYL05\MSSQL\DATA\AdventureWorks2008R2_Data.mdf The SQL Server Management Studio had to be launched "As Administrator" to be able to attach the data later. Then I connected the SQL Server. Right click on Databases, context menu Attach..., button Add..., pointed to AdventureWorks2008R2_Data.mdf + OK. Then selected the AdventureWorks2008R2_Log.ldf from the grid below (reported as Not found) and pressed the R