Friday, April 24, 2015

Teaser: How To Solve Event ID‘s 11502, 33333 & 4502

Quiet recently I had to solve an issue where the SCOM 2012x Management Server logged these nagging and BAD Event ID’s:

  1. 11502
    The Microsoft Operations Manager Connector Framework Alert Forwarding module failed to mark an alert for forwarding because the connector the module is configured for no longer exists. Connector Id: [GUID]

  2. 33333
    Data Access Layer rejected retry on SqlError. The UPDATE statement conflicted with FOREIGN KEY constraint "FK_Alert_ConnectorId". The conflict occurred in database "OperationsManager", table "dbo.Connector", column "ConnectorId"

  3. 4502
    A module of type "Microsoft.EnterpriseManagement.Mom.Modules.McAlertWriteAction" reported an exception System.Data.SqlClient.SqlException (0x80131904): The UPDATE statement conflicted with the FOREIGN KEY constraint "FK_Alert_ConnectorId:. The conflict occured in database "OperationsManager", table "dbo.Connector", column 'ConnectorId'.

It took me a while to get to the bottom of it all, but finally I FIXED it! The last days I didn’t have the time to write an article about it. But soon I’ll write a posting for it. What caused it, and how to solve it. So stay tuned!

2 comments:

AB said...

Please share your solution on these errors.

Marnix Wolf said...

Hi AB.

The solution is to be found here, posted the same month: http://thoughtsonopsmgr.blogspot.nl/2015/04/troubleshooting-event-ids-33333-11502.html

Cheers,
Marnix