Discussion:
Event ID 33333 and 10801
(too old to reply)
Ken Manohar
2009-02-27 17:59:03 UTC
Permalink
Hi Good Day,

The following warning and error periodically shows up in the Operations
Manager section of the Event Viewer log in our SCOM server. We have a single
SCOM server which is both the RMS and Database server.

Any help in troubleshooting will be greatly appreciated. I've used
<domain>\<domain controller> to replace the acutal names of the domain and
domain controller:

Event Type: Warning
Event Source: DataAccessLayer
Event Category: None
Event ID: 33333
Date: 2/25/2009
Time: 9:05:45 AM
User: N/A
Computer: <SCOM Server>
Description:
Data Access Layer rejected retry on SqlError:
Request: p_ManagedEntityInsert --
(BaseManagedEntityId=e909e260-9d42-09b9-3ef3-e29a27781be0),
(TypedManagedEntityId=e909e260-9d42-09b9-3ef3-e29a27781be0),
(ManagedTypeId=02c5162c-b89f-1d61-349a-9b0667fbd60e),
(FullName=Microsoft.Windows.Server.AD.ConnectionObject:<domain>;<domain>\<domain
controller>), (Path=<domain>), (Name=<domain>\<domain controller>),
(TopLevelHostEntityId=2f9ac299-b907-f517-df91-cf335ebdeee7),
(DiscoverySourceId=f69e01ad-6d1e-e3da-45ff-31fbcf4bc0c1),
(HealthServiceEntityId=d4982d95-9f18-6298-0f19-cdbcd14ac203),
(PerformHealthServiceCheck=True), (TimeGenerated=2/25/2009 1:05:37 PM),
(RETURN_VALUE=1)
Class: 16
Number: 777980008
Message: Health service ( D4982D95-9F18-6298-0F19-CDBCD14AC203 ) should not
generate data about this managed object (
E909E260-9D42-09B9-3EF3-E29A27781BE0 ).
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: 9:05:45 AM
User: N/A
Computer: <SCOM Server>
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: e01fce66-71ba-81fc-4e7e-a501e26c1dc2
HealthServiceId: d4982d95-9f18-6298-0f19-cdbcd14ac203
Health service ( D4982D95-9F18-6298-0F19-CDBCD14AC203 ) should not generate
data about this managed object ( E909E260-9D42-09B9-3EF3-E29A27781BE0 )..
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Thanks,
Ken
Jeffrey Knapp
2009-02-27 20:00:01 UTC
Permalink
That was the exact query statement that Microsoft gave me. i copied and
pasted it.
i would have to double check with them again...

in the mean time, how many computer agents are you monitoring? how many are
domain controllers? i would check that box for each of them.
Thanks Jeffrey!
The Query executed successfully. However, I'm not getting any results. It
seems that the managed object from the error does not exist in the
BaseManagedEntity table.
I've search through the errors and tried about 3 different ID's. Same result.
Any thoughts?
Regards,
Ken
Ken Manohar
2009-02-27 20:37:02 UTC
Permalink
Hey Jeffery,

There are 50 managed servers and 24 of them are domain controllers.

The select statement is ok. It's just the ID's from the error messages are
not part of the table, so it's not finding it.

Regards,
Ken
Jeffrey Knapp
2009-03-13 17:43:03 UTC
Permalink
Ken,
Sorry it took me like WEEKS to respond to this.. i figured it out.
i finally had a chance to adjust the servers that needed the proxy check.

1) Use the following query in teh sql management studio on the
OPERATIONSMANAGER database to identilfy the agent throwing this error:

Select * from BaseManagedEntity Where BaseManagedEntityID
='33E45215-A4F8-811F-88AA-C1FA91B79E95'

(Note: The ID comes from the error message 33333 and its the 2nd to last id
for the HEALTH SERVICE ID... not the last id that comes after "should not
generate data about this managed object)


2) Set the agent that came back as "Allow this agent to act as a proxy...."
from "SCOM > Administration -> Agent Managed -> Properties -> Security".
Post by Ken Manohar
Hey Jeffery,
There are 50 managed servers and 24 of them are domain controllers.
The select statement is ok. It's just the ID's from the error messages are
not part of the table, so it's not finding it.
Regards,
Ken
Jeffrey Knapp
2009-02-27 19:22:03 UTC
Permalink
I actually had extensive phone conversations with Microsoft just last week.
These 2 error codes occure on computers that need to have the security proxy
box checked. by that i mean
Administration > Device Management > Agent Managed (or Management servers) >
right click on a computer > Select Properties > Security Tab > check the box
that says "Allow this agent to act as a proxy..."

the problem is that the error doesn't show the friendly computer name of the
computer this needs to be turned on for! it shows the id number in the
opsmanager database.

So to find the computer you have to open the SQL server management studio
and run the following query.

select * from BaseManagedEntity where BaseManagedEntityID ='xxxxxxxxxx'

where my "X"s are.. put in the full id number from the last line of the
error.. what ever is after "should not generate data about this managed
object"

Turning on the proxy is really no big deal at all. no damage will come of
this. I personally monitor over 350 servers and i need to turn this on for
most of my domain controllers and virtual server hosts that report for the
virtual machines.
Post by Ken Manohar
Hi Good Day,
The following warning and error periodically shows up in the Operations
Manager section of the Event Viewer log in our SCOM server. We have a single
SCOM server which is both the RMS and Database server.
Any help in troubleshooting will be greatly appreciated. I've used
<domain>\<domain controller> to replace the acutal names of the domain and
Event Type: Warning
Event Source: DataAccessLayer
Event Category: None
Event ID: 33333
Date: 2/25/2009
Time: 9:05:45 AM
User: N/A
Computer: <SCOM Server>
Request: p_ManagedEntityInsert --
(BaseManagedEntityId=e909e260-9d42-09b9-3ef3-e29a27781be0),
(TypedManagedEntityId=e909e260-9d42-09b9-3ef3-e29a27781be0),
(ManagedTypeId=02c5162c-b89f-1d61-349a-9b0667fbd60e),
(FullName=Microsoft.Windows.Server.AD.ConnectionObject:<domain>;<domain>\<domain
controller>), (Path=<domain>), (Name=<domain>\<domain controller>),
(TopLevelHostEntityId=2f9ac299-b907-f517-df91-cf335ebdeee7),
(DiscoverySourceId=f69e01ad-6d1e-e3da-45ff-31fbcf4bc0c1),
(HealthServiceEntityId=d4982d95-9f18-6298-0f19-cdbcd14ac203),
(PerformHealthServiceCheck=True), (TimeGenerated=2/25/2009 1:05:37 PM),
(RETURN_VALUE=1)
Class: 16
Number: 777980008
Message: Health service ( D4982D95-9F18-6298-0F19-CDBCD14AC203 ) should not
generate data about this managed object (
E909E260-9D42-09B9-3EF3-E29A27781BE0 ).
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: 9:05:45 AM
User: N/A
Computer: <SCOM Server>
Discovery data couldn't be inserted to the database. This could have
- 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.
DiscoveryId: e01fce66-71ba-81fc-4e7e-a501e26c1dc2
HealthServiceId: d4982d95-9f18-6298-0f19-cdbcd14ac203
Health service ( D4982D95-9F18-6298-0F19-CDBCD14AC203 ) should not generate
data about this managed object ( E909E260-9D42-09B9-3EF3-E29A27781BE0 )..
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Thanks,
Ken
Ken Manohar
2009-02-27 19:53:02 UTC
Permalink
Thanks Jeffrey!

The Query executed successfully. However, I'm not getting any results. It
seems that the managed object from the error does not exist in the
BaseManagedEntity table.

I've search through the errors and tried about 3 different ID's. Same result.

Any thoughts?

Regards,
Ken
Loading...