Microsoft
Software
Hardware
Network
Question : SQL Errors - Cannot execute as the database principal
We've enabled SQL notifications on our databases, and recently upgraded out servers. Hence backing up and restoring the databases to the new server. In doing this, we now generate massive logs with the following errors (about 10 a second).
The activated proc [dbo].[SqlQueryNotificatio
nStoredPro
cedure-927
22d2e-21fc
-40b9-8398
-63b89cafb
97a] running on queue DATABASENAME.dbo.SqlQueryN
otificatio
nService-9
2722d2e-21
fc-40b9-83
98-63b89ca
fb97a output the following: '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.'
Running select name,suser_sname(owner_sid
) as owner from sys.databases; shows a login of sa for some databases (no errors, no notifications set up in here) and domain\username for the databases we have errors with.
Running USE DATABAENAME GO sp_changedbowner 'sa'; or with 'domain\user' causes the following error: Cannot find the principal 'domain\user', because it does not exist or you do not have permission.
Any ideas how to fix these? It's filling up our HDD space quite quickly.
Thanks.
Answer : SQL Errors - Cannot execute as the database principal
Are you logged in as an account which has sysadmin?
Random Solutions
WSUS sync problem
no value and value
Sql query returning different results each time it is run even though conditions are the same.
MYSQL Query Help
GridView.Column.Count = 0 When AutoGenerateColumns="True"<wbr />.
Draw on Window Desktop Background
I want to have my command button use the generic pdf printer when it is clicked
Can't access Windows XP shares from Windows 7 after a BIOS reset
File format is invalid
Restore a full backup of a disktop?