November 4, 2010 at 11:07 am
I'm seeing the following errors in my Windows Application event log:
Cannot create the event notification 'SQLWEP_CE492A26_8D18_48CA_B4A0_0221AB3AD1DD', because you do not have permission.
SQLErrorInfo: 42000
HResult:0x80040e14
Source:Microsoft SQL Server Native Client 10.0
Changed database context to 'msdb'.
SQLErrorInfo: 01000
HResult:0x00000000
Source:Microsoft SQL Server Native Client 10.0
Any idea what this means? I had about 80 of these over the course of 4 seconds. They seems to always occur in pairs but the notification name is a different number. Running SQL 2K8 R2 CU1. Not a clustered server, but it is mirroring 5 databases.
November 4, 2010 at 11:09 am
I should also add there is nothing in the SQL logs at the same time these errors show up.
November 23, 2010 at 8:23 am
Still trying to figure out what is causing these. It seems related to mirroring. I've got DDL logging on the server and I see lots of CREATE_EVENT_NOTIFICATION events happening, all by NT Authority / System (which is not the account the SQL Server or Agent services are running under). The only SQL-related services running under the Local System account are SQL Server VSS Writer and SQL Full-test Filter Daemon Launcher.
My DDL logging shows lots of these events being created, but only some of them are failing and showing up in the Windows Event log. The majority seem to be created (and later dropped) just fine. In fact, going by the GUIDs, all the ones showing in my DDL logging work (and don't show in the event log) and the ones in the event log I do not see in the DDL logs (which makes sense, if they are failing).
These events start happening during a maintenance plan that pauses mirroring, disables some WMI alert I have set up for mirroring state changes, performs a DBCC CHECKDB and some index defrags, then re-enables mirroring and the alerts. In the Database Mirroring Monitor, I have no warnings enabled.
Mirroring seems to be working OK. Databases are synchronized. There are no messages in the SQL logs related to this.
I have no idea what is causing these errors to be written to the event log. Can anyone help?
October 15, 2012 at 10:20 am
Hi there did you get to the bottom of this as I have started receiving these errors myself. Seems very little about it anywhere, I am also using Mirroring.
October 15, 2012 at 10:58 am
Sorry, I never figured anything out with regards to this. I've since moved on to a different company and no longer have anything similar in my current environment.
October 16, 2012 at 3:52 am
OK in case anyone was interested I have found more out.
These errors were occurring for me when I had configured SCOM to monitor by using a WMI alert. The default action account for this in SCOM is SYSTEM, and I could see lots of errors in the SQL logs in regards to this to. I set SA on the SYSTEM account and the errors have stopped and the alert is functioning correctly.
Hope its of some help.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply