Ms Sql Server Error 15517
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: Error 15517 SQL Server > SQL Service Broker Question sql server error 15517 replication 0 Sign in to vote please need help ..this the wrong message cannot find the principal 'dbo', because it does not exist or you do not have permission. shown in my logAn exception occurred while enqueueing a message in the target queue. Error: 15517
Error 15517 Sql Server 2012
May 26, 2009 6:55 AM Reply | Quote All replies 1 Sign in to vote Most probably the ownership of the queue's database is broken somehow. Try to ensure the owner is a valid server login. You may do that by running ALTER AUTHORIZATION on DATABASE::[your_db_name] to [some_valid_login] Proposed as answer by Butschkow Friday, July 15, 2011 7:45 AM Tuesday, principal dbo does not exist May 26, 2009 5:25 PM Reply | Quote Moderator 0 Sign in to vote Most probably the ownership of the queue's database is broken somehow. Try to ensure the owner is a valid server login. You may do that by running ALTER AUTHORIZATION on DATABASE::[your_db_name] to [some_valid_login] a new error shown Error Message. Cannot show requested dialog. Additional information: Cannot show requested dialog. (SqlMgmt) Property Owner is not available for Database ’[ ]’. This property may not exist for this object, or may not be retrievable due to insufficient access rights. (Microsoft.SqlServer.SmoMCP MCSA MCSE MCT Wednesday, May 27, 2009 7:11 AM Reply | Quote 0 Sign in to vote I don't believe this is a broker issue, but this forum thread may help you: http://social.msdn.microsoft.com/forums/en-US/sqltools/thread/91a27e23-c760-4ac1-80f4-0fac220c1adb/ Wednesday, May 27, 2009 3:51 PM Reply | Quote Moderator 0 Sign in to vote {$content} The link you provided is very useful, Now I have a more clear idea about it. Monday, November 08, 2010 1:50 PM Reply | Quote 2 Sign in to vote This error is related to an orphaned data
does not exist ★★★★★★★★★★★★★★★ Chris Skorlinski [MSFT]February 26, 20109 Share 0 0 LogReader fails with error 15517: 2010-02-25 21:16:35.054 Status: 0, code: mssql_repl20011 20011, text: ‘The process could not execute ‘sp_replcmds' on ‘CHRISSKACER'.'.2010-02-25 21:16:35.056 The
The Process Could Not Execute 'sp_replcmds'
process could not execute ‘sp_replcmds' on ‘CHRISSKACER'.2010-02-25 21:16:35.057 Status: 0, code: 15517, text: ‘Cannot execute as the database
Alter Authorization On 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 https://social.msdn.microsoft.com/Forums/sqlserver/en-US/0dca9324-e274-4e7a-bb6b-e8709fea809c/error-15517?forum=sqlservicebroker could not execute ‘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 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/ 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 databaseUSEhave permission November 7, 2012 Riteshshah replication, sql server, SQL Server 2012 Error Fix - Cannot http://blog.extreme-advice.com/2012/11/07/error-fix-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/ execute as the database principal because the principal dbo does not http://dba.stackexchange.com/questions/96697/view-job-properties-fails-for-job-owner exist this type of principal cannot be impersonated or you do not have permission Earlier I have written one article to setup replication in SQL Server 2012 and remove replication from SQL Server 2012. One of the colleagues in my previous sql server company (Yes, I do keep relation with my ex. colleagues ) sent me an email to help. While he was trying to remove publication by following the instruction given in my article “remove replication from SQL Server 2012”, Error seems interesting and looks big but solution to this error is very easy sql server error and short. he comes across the following error: TITLE: Microsoft SQL Server Management Studio ------------------------------ Could not delete publication 'AdvertureWorks2012AddressObjects'. For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=11.0.2100.60&EvtSc=Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.Replication.ReplicationMenuItem&EvtID=CantDeletePublication&LinkId=20476 ------------------------------ ADDITIONAL INFORMATION: An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo) ------------------------------ 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. Changed database context to 'AdventureWorks2012'. (Microsoft SQL Server,Error: 15517) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=11.00.2218&EvtSrc=MSSQLServer&EvtID=15517&LinkId=20476 Error would looks like this screen capture: If you are trying removing the publication with the login which has insufficient privileges, you might come across this error. There is one small command to execute to give proper permission to your login. Execute following command in your SQL Server Instance. ALTER AUTHORIZATION ON DATABASE::[DatabaseName] TO [LoginName]; As soon as you will have proper permission, you will be able to remove publication. If you like this article, do like “Extreme-Advice
log in tour help Tour Start here 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 the company Business Learn more about hiring developers or posting ads with us Database Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top View Job Properties Fails for Job Owner up vote 0 down vote favorite Domain user MyDomain\UserA has a login with a server role of public and is a user of the msdb database with membership in the SQLAgentUserRole. The user owns a job, Daily Job. When logged in as the user, if I try to view the job properties, I get this error: Cannot execute as the database principal because the principal "guest" does not exist, this type of principal cannot be impersonated, or you do not have permission. (Microsoft Server, Error: 15517) If I right click on Jobs and Select New Job... I get the exact same error. I have even given the user membership in SQLAgentOperatorRole but get the same error. In all my searching online, the only similar issue I've found is this question on MSDN, which is unanswered. Any ideas? I'm at a loss here. sql-server sql-server-2012 share|improve this question asked Mar 31 '15 at 16:25 Kevin Kelso 357 So is d.name NULL in the following query, or populated: select j.name, j.owner_sid, s.name, d.name from msdb.dbo.sysjobs AS j INNER JOIN master.sys.server_principals AS s ON j.owner_sid = s.sid LEFT OUTER JOIN msdb.sys.database_principals AS d ON s.sid = d.sid; –Aaron Bertrand♦ Mar 31 '15 at 17:05 @AaronBertrand d.name is populated with MyDomain\UserA –Kevin Kelso Mar 31 '15 at 17:09 Can you give some details about what the job does, what kinds of steps it has, any advanced options, that kind of thing? I'm guessing it has dependencies on databases that this login does not have access to... –Aaro