Question

Locked

SQL Error 9724

By jaishiv_singh ·
Hi,

I have been receiving the following error from my SQL Database Server, and upon veiwing the event log it seems that this error is generated around 6 per minute.

SQL: MSSQL 2005
Microsoft SQL Server Management Studio: 9.00.3042.00

The following is the error:
----------------------------------------------------------------
Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event I 9724
Date: 2/17/2009
Time: 12:24:07 PM
User: N/A
Computer: FJHRB000
Description:
The activated proc [dbo].[SqlQueryNotificationStoredProcedure-9742e284-1a83-4ca9-90eb-7546be9fce97] running on queue HRnet.dbo.SqlQueryNotificationService-9742e284-1a83-4ca9-90eb-7546be9fce97 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.'

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 000025fc 0000000a 00000009 004a0046
0010: 00520048 00300042 00300030 00060000
0020: 00480000 006e0052 00740065 0000

------------------------------------------------------------------

Can you please help me find out cause of it and how to resolve this.

Thanks,

Jaishiv Singh
jaishiv_singh@hotmail.com

This conversation is currently closed to new comments.

2 total posts (Page 1 of 1)  
Thread display: Collapse - | Expand +

All Answers

Collapse -

Cause is listed in event log entry

by seanferd In reply to SQL Error 9724

'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.'

The activated proc [dbo].[SqlQueryNotificationStoredProcedure-9742e284-1a83-4ca9-90eb-7546be9fce97] running on queue HRnet.dbo.SqlQueryNotificationService

So the proc says it can't execute as the principal, because there is a problem with "dbo", which is supposed to be the principal.

It does not exist at all (dbo is missing)
or
"dbo" does not have permissions (proper & functioning login{authorization]? appropriate privileges?)
or
This won't work impersonated due to the level of permission required, which is not available to impersonated principals.


That's as far as I can parse this, so please post your code and the forum what you are trying to accomplish so others can offer some help.

Also mention any software changes (updates) made before this problem occurred.

Collapse -

Could be a few things that

by Tony Hopkinson In reply to SQL Error 9724

In 2k5, dbo is now a schema not a 'user', so dbo in database1 is not dbo in database2

You need to check the authoristaion/permissions of the service.

As a PS if you've upgraded from a 2k, check the database compatibility mode. It should be 90 for 2k5 (2k was 80). All sorts of built in SPs in 2k5 give you weird and wonderful error messages if you run them on a mode 80 db.

SQl Server Mangaement Studio, right click over the database, select properties.

Back to Networks Forum
2 total posts (Page 1 of 1)  

Related Discussions

Related Forums