Event ID 10801 and 33333 in Operations Manager log

This is something that I have been getting hit with a lot and now finally I found the time to deal with it.

The Operations Manager event log on the SCOM server was hitting me with the following event:

Discovery data couldn’t be inserted to the database. This could have happened because of one of the following reasons:

– Discovery data is stale. The discovery data is generated by an MP recently deleted.
– Database connectivity problems or database running out of space.
– Discovery data received is not valid.

The following details should help to further diagnose:

DiscoveryId: 7cf81cf1-b2f2-6242-571e-c4c988639eef
HealthServiceId: 64d0d5b5-ec8f-b5e2-bc0f-ac2cefc7ba1a
Microsoft.EnterpriseManagement.Common.DiscoveryDataInvalidRelationshipTargetException,The relationship target specified in the discovery data item is not valid.
Relationship target ID: 05ecb254-bca3-e788-85d0-c7aad007722d
Rule ID: 7cf81cf1-b2f2-6242-571e-c4c988639eef
<?xml version=”1.0″ encoding=”utf-16″?><RelationshipInstance TypeId=”{ccbc24c2-8403-0a4c-5f09-49d1a59a421f}” SourceTypeId=”{00000000-0000-0000-0000-000000000000}” TargetTypeId=”{00000000-0000-0000-0000-000000000000}”><Settings /><SourceRole><Settings><Setting><Name>5c324096-d928-76db-e9e7-e629dcc261b1</Name><Value>SQL01.itbl0b.com</Value></Setting><Setting><Name>af13c36e-9197-95f7-393c-84aa6638fec9</Name><Value>\\.\PHYSICALDRIVE11</Value></Setting></Settings></SourceRole><TargetRole><Settings><Setting><Name>5c324096-d928-76db-e9e7-e629dcc261b1</Name><Value>SQL01.itbl0b.com</Value></Setting><Setting><Name>af13c36e-9197-95f7-393c-84aa6638fec9</Name><Value>Disk #11, Partition #0</Value></Setting></Settings></TargetRole></RelationshipInstance>.

When I first noticed this event I searched the web for a result and got a lot of ideas how to solve it but none of them were effective.

The important thing to notice in that event is the following line:

The relationship target specified in the discovery data item is not valid.

You see, the exact same event id (with pretty much the same text) can appear for several different errors.

Searching the web, I found a thread on Technet forums that lead me to a solution. I used Graham’s SQL query to check who was generating this event on my server (Run this command against the OperationsManager DB):

select COALESCE(D.DiscoveryName, RU.RuleName, N'(system)') as [Rule Name],
COALESCE(DMP.MPName, DMP.MPName, N'(system)') as [MP Name],
DS.* from DiscoverySource DS
left outer join Discovery D on D.DiscoveryId = DS.DiscoveryRuleId
left outer join Rules RU on RU.RuleId = DS.DiscoveryRuleId
left outer join ManagementPack DMP on DMP.ManagementPackId =
left outer join ManagementPack RMP on RMP.ManagementpackId =
where D.DiscoveryId = '7cf81cf1-b2f2-6242-571e-c4c988639eef'

I had to change the following line with the ID that appeared in my event:

where D.DiscoveryId = '7cf81cf1-b2f2-6242-571e-c4c988639eef'

You can find the ID if you look at the ‘DiscoveryID’ in the event log.

The output is a list of objects that correspond to that Discovery Rule. In my case, the rule that was hitting me generated by ‘Microsoft.Windows.Server.6.2.PhysicalDiskContainsDiskPartition.Discovery’ which is part of the ‘Microsoft.Windows.Server.2012.Discovery’.


At this point I had two options – either the rule was mis-configured or there was something wrong with the agent on the monitored server. Out of pure speculation, I have decided that the latter was the source of my problem. To solve this, I have flushed the agent’s history and waited. Up until now – all is good!

By the way, You can see the name of the agent from the even log – in my case its ‘SQL01.itbl0b.com’

What do you think about this post?