Event 10830 errors generated by the AD managent pack.

Hi,

I have recently installed SCOM 2012 R2 in preparation to migrate over from 2007R2.

I have only one agent installed ( a Domain cotroller) and have found the 'One or more Domain controllers may not be replicating' rule is causing Event 10830 error every 15 minutes:

An alert couldn't be inserted to the database. This could have happened because  of one of the following reasons:

- Alert is stale. The alert is generated by an MP recently deleted.

- Database connectivity problems or database running out of space.

- Alert received is not valid.

The following details should help to further diagnose:

Details: RuleId:a811dcbc-4c5b-d9de-592b-f01e17fc0e9a. HealthServiceId:60951ca0-edc4-5a4d-be13-734dba2e4c53. The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Alert_BaseManagedEntity". The conflict occurred in database "OperationsManager", table "dbo.BaseManagedEntity", column 'BaseManagedEntityId'.

The statement has been terminated.RuleId:a811dcbc-4c5b-d9de-592b-f01e17fc0e9a. HealthServiceId:60951ca0-edc4-5a4d-be13-734dba2e4c53. The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Alert_BaseManagedEntity". The conflict occurred in database "OperationsManager", table "dbo.BaseManagedEntity", column 'BaseManagedEntityId'.

The statement has been terminated.RuleId:a811dcbc-4c5b-d9de-592b-f01e17fc0e9a. HealthServiceId:60951ca0-edc4-5a4d-be13-734dba2e4c53. The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Alert_BaseManagedEntity". The conflict occurred in database "OperationsManager", table "dbo.BaseManagedEntity", column 'BaseManagedEntityId'.

The statement has been terminated.RuleId:a811dcbc-4c5b-d9de-592b-f01e17fc0e9a. HealthServiceId:60951ca0-edc4-5a4d-be13-734dba2e4c53. The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Alert_BaseManagedEntity". The conflict occurred in database "OperationsManager", table "dbo.BaseManagedEntity", column 'BaseManagedEntityId'.

The statement has been terminated.RuleId:a811dcbc-4c5b-d9de-592b-f01e17fc0e9a. HealthServiceId:60951ca0-edc4-5a4d-be13-734dba2e4c53. The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Alert_BaseManagedEntity". The conflict occurred in database "OperationsManager", table "dbo.BaseManagedEntity", column 'BaseManagedEntityId'.

The statement has been terminated.RuleId:a811dcbc-4c5b-d9de-592b-f01e17fc0e9a. HealthServiceId:60951ca0-edc4-5a4d-be13-734dba2e4c53. The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Alert_BaseManagedEntity". The conflict occurred in database "OperationsManager", table "dbo.BaseManagedEntity", column 'BaseManagedEntityId'.

The statement has been terminated.RuleId:a811dcbc-4c5b-d9de-592b-f01e17fc0e9a. HealthServiceId:60951ca0-edc4-5a4d-be13-734dba2e4c53. The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Alert_BaseManagedEntity". The conflict occurred in database "OperationsManager", table "dbo.BaseManagedEntity", column 'BaseManagedEntityId'.

The statement has been terminated.RuleId:a811dcbc-4c5b-d9de-592b-f01e17fc0e9a. HealthServiceId:60951ca0-edc4-5a4d-be13-734dba2e4c53. The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Alert_BaseManagedEntity". The conflict occurred in database "OperationsManager", table "dbo.BaseManagedEntity", column 'BaseManagedEntityId'.

The statement has been terminated.RuleId:a811dcbc-4c5b-d9de-592b-f01e17fc0e9a. HealthServiceId:60951ca0-edc4-5a4d-be13-734dba2e4c53. The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Alert_BaseManagedEntity". The conflict occurred in database "OperationsManager", table "dbo.BaseManagedEntity", column 'BaseManagedEntityId'.

The statement has been terminated.RuleId:a811dcbc-4c5b-d9de-592b-f01e17fc0e9a. HealthServiceId:60951ca0-edc4-5a4d-be13-734dba2e4c53. The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Alert_BaseManagedEntity". The conflict occurred in database "OperationsManager", table "dbo.BaseManagedEntity", column 'BaseManagedEntityId'.

The statement has been terminated.RuleId:a811dcbc-4c5b-d9de-592b-f01e17fc0e9a. HealthServiceId:60951ca0-edc4-5a4d-be13-734dba2e4c53. The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Alert_BaseManagedEntity". The conflict occurred in database "OperationsManager", table "dbo.BaseManagedEntity", column 'BaseManagedEntityId'.

The statement has been terminated..

How can this be fixed?

February 26th, 2015 11:21am

For error 10830, you can refer below link

http://donald-scom.blogspot.com/2011/11/my-experience-handling-event-id-10830.html

Free Windows Admin Tool Kit Click here and download it now
February 26th, 2015 1:02pm
This is a known issue with AD MP
February 26th, 2015 2:55pm

Hi,

Yes, this is a known issue.

And which version of AD MP did you use?ou may try the below version.

Active Directory Domain Services Management Pack for System Center

http://www.microsoft.com/en-hk/download/details.aspx?id=21357

Free Windows Admin Tool Kit Click here and download it now
February 28th, 2015 5:31am

Hi Yan,

I'm using the most up to date version of the MP (6.0.8293.0) and SCOM 2012R2 with UR4

March 3rd, 2015 10:57am

Hi,

To work arround this issue, I would like to suggest you disable the Rule "One or more domain controllers may not be replicating" for Active directory Domain controller role to stop event ID 10830 from occurring on the server.

Regards,

Yan Li

Free Windows Admin Tool Kit Click here and download it now
March 18th, 2015 1:37am
thank you very much, I solved my problem
March 25th, 2015 8:57am

Hi,

Will you please share out the resolution here? It may also help others encoutering the similar issue.

Regards,

Yan Li

Free Windows Admin Tool Kit Click here and download it now
March 25th, 2015 9:23pm

Hi,

We have the same issue in our environment, using AD MP 6.0.8293.0. I see that the only "solution" is to disable the rule for all objects, or does anyone have other ways to fix this? Foreign Key constraint in the database would allow the record to be inserted, but i don't like to do this.


  • Edited by ehrnst 20 hours 49 minutes ago
May 12th, 2015 6:22am

Hi,

We have the same issue in our environment, using AD MP 6.0.8293.0. I see that the only "solution" is to disable the rule for all objects, or does anyone have other ways to fix this? Foreign Key constraint in the database would allow the record to be inserted, but i don't like to do this.


  • Edited by ehrnst Tuesday, May 12, 2015 10:22 AM
Free Windows Admin Tool Kit Click here and download it now
May 12th, 2015 10:19am

Hi,

We have the same issue in our environment, using AD MP 6.0.8293.0. I see that the only "solution" is to disable the rule for all objects, or does anyone have other ways to fix this? Foreign Key constraint in the database would allow the record to be inserted, but i don't like to do this.


  • Edited by ehrnst Tuesday, May 12, 2015 10:22 AM
May 12th, 2015 10:19am

Hi,

We have the same issue in our environment, using AD MP 6.0.8293.0. I see that the only "solution" is to disable the rule for all objects, or does anyone have other ways to fix this? Foreign Key constraint in the database would allow the record to be inserted, but i don't like to do this.


  • Edited by ehrnst Tuesday, May 12, 2015 10:22 AM
Free Windows Admin Tool Kit Click here and download it now
May 12th, 2015 10:19am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics