You are currently offline, waiting for your internet to reconnect

You cannot run a statement or a module that includes the EXECUTE AS clause after you restore a database in SQL Server 2005

Extended support for SQL Server 2005 ends on April 12, 2016

If you are still running SQL Server 2005 after April 12, 2016, you will no longer receive security updates and technical support. We recommend upgrading to SQL Server 2014 and Azure SQL Database to achieve breakthrough performance, maintain security and compliance, and optimize your data platform infrastructure. Learn more about the options for upgrading from SQL Server 2005 to a supported version here.

Bug #: 397455 (SQLBUDT)
SYMPTOMS
When you run a statement or a module that includes the EXECUTE AS clause in Microsoft SQL Server 2005, you may receive the following error message:
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.
This problem occurs when all the following conditions are true:
  • You back up a database from an instance of SQL Server 2005. Then, you restore the database to an instance of SQL Server 2005 that is installed on another computer.
  • The statement or the module is executed as the dbo (database owner) user.
  • The owner of the database is a domain user or a SQL Server authorization login.

    Notes
    • If a domain user owns the database, the computer on which you restore the database cannot access the domain.
    • If a SQL Server authorization login owns the database, the login does not exist in the new instance of SQL Server 2005.
CAUSE
This problem occurs because SQL Server 2005 cannot obtain the information about the context when you try to impersonate a database user to run a statement or a module.

SQL Server cannot obtain the information about the context that you are trying to impersonate under the conditions that are listed in the "Symptoms" section. If you impersonate a SQL Server authorization login, SQL Server cannot find a login that matches the security identifier (SID) of the impersonated user. If you impersonate a domain user, the domain controller cannot find the information about the specific user who matches the SID of the impersonated user.
WORKAROUND
To work around this problem, change the database owner to a valid login or domain user. To do this, run the following statements:
USE <DatabaseName>GOsp_changedbowner '<NewLogin>'
Note <DatabaseName> represents the name of the database. <NewLogin> represents the name of the login that you want to set.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Properties

Article ID: 913423 - Last Review: 02/14/2006 07:39:11 - Revision: 1.2

Microsoft SQL Server 2005 Standard Edition, Microsoft SQL Server 2005 Developer Edition, Microsoft SQL Server 2005 Enterprise Edition, Microsoft SQL Server 2005 Express Edition, Microsoft SQL Server 2005 Workgroup Edition

  • kbsql2005engine kbprb kbexpertiseadvanced KB913423
Feedback
html>