"##MS_PolicyEventProcessingLogin##" errors

Question

"##MS_PolicyEventProcessingLogin##" errors

smitty-1088185

SSCrazy

Points: 2321
More actions
June 22, 2010 at 7:50 pm

#224131

I installed the Oracle 11g client on my (Windows 2008 SPK2/SQL 2008 R2) and set up a Linked server to an Oracle database and now I'm getting the same error message ever 5 seconds in the SQL logs. Not much information on Google about the error. Any help would be appreciated.
Thanks in advance.
*******************************************************
Date6/22/2010 9:44:57 PM
LogSQL Server (Current - 6/22/2010 2:19:00 PM)
Sourcespid32s
Message
The activated proc '[dbo].[sp_syspolicy_events_reader]' running on queue 'msdb.dbo.syspolicy_event_queue' output the following: 'Cannot execute as the database principal because the principal "##MS_PolicyEventProcessingLogin##" does not exist, this type of principal cannot be impersonated, or you do not have permission.'

Viewing 11 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply

Minaz Amin SSChampion Points: 11052 More actions · Answer 1

Message
The activated proc '[dbo].[sp_syspolicy_events_reader]' running on queue 'msdb.dbo.syspolicy_event_queue' output the following: 'Cannot execute as the database principal because the principal "##MS_PolicyEventProcessingLogin##" does not exist, this type of principal cannot be impersonated, or you do not have permission.'

Make sure the ##MS_PolicyEventProcessingLogin## exists in the MSDB and MASTER database.

SELECT * FROM master.sys.database_principals WHERE [name] LIKE '%##%'

SELECT * FROM msdb.sys.database_principals WHERE [name] LIKE '%##%'

If possible remap the user in the MSDB & Master database.

"More Green More Oxygen !! Plant a tree today"

smitty-1088185 SSCrazy Points: 2321 More actions · Answer 2

It was an orphaned account in the MSDB database. The following two commands fixed it.

exec sp_change_users_login ‘report’

EXEC sp_change_users_login 'Auto_Fix', '##MS_PolicyEventProcessingLogin##',NULL, 'Password01!';

sqldbaonly SSC Enthusiast Points: 186 More actions · Answer 3

I had did all but Issue is not sloved.

Can please suggest other way ?

kenyeung70 SSC Enthusiast Points: 188 More actions · Answer 4

Got the same error message in the error log.

Did the above scripts but it returned nothing; implying no orphaned login. And the error messages were still logging in the error log.

Any other solution would be appreciated.

kenyeung70 SSC Enthusiast Points: 188 More actions · Answer 5

kenyeung70 (4/24/2014)
Got the same error message in the error log.
Did the above scripts but it returned nothing; implying no orphaned login. And the error messages were still logging in the error log.
Any other solution would be appreciated.

I found a fix on my problem. I have to run the above scripts two times; each with "USE master;" and "USE msdb;" before the scripts. How the error message is no longer logged in the error log file.

sql.srinivasdba SSC Enthusiast Points: 101 More actions · Answer 6

Fixed my problem by running Orphan users Script for two times on msdb, master databases. Thanks

Srini

john.martin 86842 SSC Journeyman Points: 92 More actions · Answer 7

john.martin 86842

SSC Journeyman

Points: 92

May 6, 2015 at 2:59 pm

#1796068

.

Dianne Scott SSC Enthusiast Points: 107 More actions · Answer 8

Thank you!! My error was similar and the orphaned user in msdb was the issue. 😀

GK01 SSC Veteran Points: 298 More actions · Answer 9

smitty-1088185 (6/23/2010)
It was an orphaned account in the MSDB database. The following two commands fixed it.
exec sp_change_users_login ‘report’
EXEC sp_change_users_login 'Auto_Fix', '##MS_PolicyEventProcessingLogin##',NULL, 'Password01!';

Thanks a lot. This works.

richard.willemain SSC Enthusiast Points: 121 More actions · Answer 10

Using WINDOWS Authentication only., and login is not an orphaned used for master, nor msdb.

Still looking for a solution with SS_2014 SP2.