SCOM Event ID 10801 and 33333

Do you have systems logging the following events in your event log on the RMS or another management server?

Event Type:      Warning

Event Source:   DataAccessLayer

Event Category: None

Event ID:          33333

Date:                2/25/2009

Time:                12:36:50 AM

User:                N/A

Computer:         MANAGEMENTSERVER

Description:

Data Access Layer rejected retry on SqlError:

 Request: p_DiscoverySourceUpsert — (DiscoverySourceId=8bd389ab-7e6b-fa90-e8fb-a0849678f0a4), (DiscoverySourceType=0), (DiscoverySourceObjectId=7727e469-3a35-fddf-f255-f9404b3383df), (IsSnapshot=True), (TimeGenerated=2/25/2009 8:36:15 AM), (BoundManagedEntityId=3ca98a65-c8be-3f04-6394-ec5ecc85107d), (IsDiscoveryPackageStale=), (RETURN_VALUE=1)

 Class: 16

 Number: 777980004

 Message: Discovery data has been received from a rule targeted to a non-existent entity. The discovery data will be dropped.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:      Error

Event Source:   Health Service Modules

Event Category: None

Event ID:          10801

Date:                2/25/2009

Time:                12:36:50 AM

User:                N/A

Computer:         MANAGEMENTSERVER

Description:

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: 7727e469-3a35-fddf-f255-f9404b3383df

 HealthServiceId: 778a7339-3866-9639-eb1d-60e29a16962d

 Discovery data has been received from a rule targeted at a non-existent monitoring object id.

MonitoringObjectId: 3ca98a65-c8be-3f04-6394-ec5ecc85107d

RuleId: 7727e469-3a35-fddf-f255-f9404b3383df.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

If so, run the following query on your Operations Database for find what machines are causing events 10801 and 33333:

Select * from dbo.BaseManagedEntity where BaseManagedEntityID = ‘<GUID>’

So if your event 10801 contained the following:

DiscoveryId: 7727e469-3a35-fddf-f255-f9404b3383df

 HealthServiceId: 778a7339-3866-9639-eb1d-60e29a16962d

 Discovery data has been received from a rule targeted at a non-existent monitoring object id.

MonitoringObjectId: 3ca98a65-c8be-3f04-6394-ec5ecc85107d

RuleId: 7727e469-3a35-fddf-f255-f9404b3383df.

You would take the HealthServiceID and plug it into the query.

select * from dbo.BaseManagedEntity where BaseManagedEntityID = ‘778a7339-3866-9639-eb1d-60e29a16962d’

This would give you the following result:

778A7339-3866-9639-EB1D-60E29A16962D        58295   AB4C891F-3359-3FB6-0704-075FBFE36710            Microsoft.SystemCenter.HealthService:AGENTSYSTEM.DOMAIN.AD      AGENTSYSTEM.DOMAIN.AD    NULL            AGENTSYSTEM.DOMAIN.AD    4594FC6A-5F20-6BC3-764C-EF874846EB4F       1          0          2008-11-04 04:44:58.197     2008-11-04 04:34:02.147

(I am still researching how to resolve this and will update when done. Also, this information was kindly passed onto me by Frank at MS.)