none
Error 15517

    Question

  • please need help ..

    this the wrong message shown in my log

    An exception occurred while enqueueing a message in the target queue. Error: 15517<c/> State: 1. Cannot execute as the database principal because the principal "dbo" does not exist<c/> this type of principal cannot be impersonated<c/> or you do not have permission.

    MCP MCSA MCSE MCT
    Tuesday, May 26, 2009 6:55 AM

All replies

  • 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, May 26, 2009 5:25 PM
  • 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.Smo


    MCP MCSA MCSE MCT
    Wednesday, May 27, 2009 7:11 AM
  • 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
  • {$content}

    The link you provided is very useful, Now I have a more clear idea about it.
    Monday, November 08, 2010 1:50 PM
  • This error is related to an orphaned database owner on your database. This can be verified by either looking at object explorer details and identifying the database(s) without an entry in the Owner column or running a select against sys.databases to see the database owner that is no longer valid.

    Once you have the databases then you can run:

    USE [DB Name]
    GO
    EXEC dbo.sp_changedbowner @loginame = N'sa', @map = false
    GO

    This will produce the result:

    The dependent aliases were dropped.

    And now the issue should be corrected and the errors will stop being generated in the Windows event log and SQL Server Error Log.

    Thursday, April 28, 2011 10:32 PM
  • Thanks Brown.. It really Helped.

    USE [DB Name]
    GO
    EXEC dbo.sp_changedbowner @loginame = N'sa', @map = false
    GO

    Saturday, May 12, 2012 5:59 PM