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: ae39d630-f82d-77ee-d5d9-dd4c4a2e7bc2
HealthServiceId: ab069276-c6dc-13d7-3ef5-28e780c34953
Microsoft.EnterpriseManagement.Common.DiscoveryDataUnresolvedClassPropertyNameException,Unable to resolve the class property name specified in the discovery data item. Try using a fully qualified name.
Class property name: 12f3e541-ec4d-7310-be57-fa3bde0bed06
Rule ID: ae39d630-f82d-77ee-d5d9-dd4c4a2e7bc2
Instance:
<?xml version="1.0" encoding="utf-16"?><ClassInstance TypeId="{6ce7ab22-1880-0eb1-40ba-86d9a8c3d5f5}"><Settings><Setting><Name>0b3944af-12ff-1e1f-ac5c-55485fc10671</Name><Value>MANAGED REAL TIME APPLY</Value></Setting><Setting><Name>12f3e541-ec4d-7310-be57-fa3bde0bed06</Name><Value>rac2</Value></Setting><Setting><Name>18900065-cbab-1788-0c0e-2c97ef41d7d2</Name><Value>LGWR</Value></Setting><Setting><Name>1a42a2bc-9e87-029a-6db6-f512f8d00ca2</Name><Value></Value></Setting><Setting><Name>5c92d602-346f-9202-e2b4-7cfdc7226661</Name><Value>Common</Value></Setting><Setting><Name>5e763b8d-1979-d0e9-08bf-ea857c67fbaa</Name><Value></Value></Setting><Setting><Name>7dd3b6cb-8180-d58a-fae2-985730c3ffb8</Name><Value></Value></Setting><Setting><Name>7ecb288d-50c8-dd5b-419f-5d4712ef4b75</Name><Value>Database Physical</Value></Setting><Setting><Name>8c62b4e5-a737-b8d7-9017-4e8ea4c5a4ac</Name><Value></Value></Setting><Setting><Name>99cdac55-6b00-2485-cb26-bed62d37c926</Name><Value>Common</Value></Setting><Setting><Name>9ed7463c-fa1e-00ea-6743-5e54b928b7e8</Name><Value></Value></Setting><Setting><Name>a606d019-eff4-c6b9-eec9-32d43913fa58</Name><Value>DatabasePhysicalMP</Value></Setting><Setting><Name>aa9fbc8a-e274-91e8-7731-ba324682cab9</Name><Value>DatabasePhysical</Value></Setting><Setting><Name>afb4f9e6-bf48-1737-76ad-c9b3ec325b97</Name><Value>rac2</Value></Setting><Setting><Name>b60a9e0e-5baa-9b0a-8201-6ddd697d060d</Name><Value></Value></Setting><Setting><Name>bf194186-a061-ccf1-94de-971988a79003</Name><Value></Value></Setting><Setting><Name>c2ec02fc-fa4d-65c9-82da-fa76476433eb</Name><Value>rac2</Value></Setting><Setting><Name>d87b0cd0-2149-5736-ab85-42ebddab12a2</Name><Value></Value></Setting><Setting><Name>e1165cbd-8778-5bc1-de07-af341d420068</Name><Value>GRD</Value></Setting><Setting><Name>f56fc436-4a31-48dc-3127-745e5a6d2800</Name><Value></Value></Setting><Setting><Name>fda3d28f-3f34-e51c-e1ad-b1413a70c4ac</Name><Value>GUARD</Value></Setting></Settings></ClassInstance>.
- 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: ae39d630-f82d-77ee-d5d9-dd4c4a2e7bc2
HealthServiceId: ab069276-c6dc-13d7-3ef5-28e780c34953
Microsoft.EnterpriseManagement.Common.DiscoveryDataUnresolvedClassPropertyNameException,Unable to resolve the class property name specified in the discovery data item. Try using a fully qualified name.
Class property name: 12f3e541-ec4d-7310-be57-fa3bde0bed06
Rule ID: ae39d630-f82d-77ee-d5d9-dd4c4a2e7bc2
Instance:
<?xml version="1.0" encoding="utf-16"?><ClassInstance TypeId="{6ce7ab22-1880-0eb1-40ba-86d9a8c3d5f5}"><Settings><Setting><Name>0b3944af-12ff-1e1f-ac5c-55485fc10671</Name><Value>MANAGED REAL TIME APPLY</Value></Setting><Setting><Name>12f3e541-ec4d-7310-be57-fa3bde0bed06</Name><Value>rac2</Value></Setting><Setting><Name>18900065-cbab-1788-0c0e-2c97ef41d7d2</Name><Value>LGWR</Value></Setting><Setting><Name>1a42a2bc-9e87-029a-6db6-f512f8d00ca2</Name><Value></Value></Setting><Setting><Name>5c92d602-346f-9202-e2b4-7cfdc7226661</Name><Value>Common</Value></Setting><Setting><Name>5e763b8d-1979-d0e9-08bf-ea857c67fbaa</Name><Value></Value></Setting><Setting><Name>7dd3b6cb-8180-d58a-fae2-985730c3ffb8</Name><Value></Value></Setting><Setting><Name>7ecb288d-50c8-dd5b-419f-5d4712ef4b75</Name><Value>Database Physical</Value></Setting><Setting><Name>8c62b4e5-a737-b8d7-9017-4e8ea4c5a4ac</Name><Value></Value></Setting><Setting><Name>99cdac55-6b00-2485-cb26-bed62d37c926</Name><Value>Common</Value></Setting><Setting><Name>9ed7463c-fa1e-00ea-6743-5e54b928b7e8</Name><Value></Value></Setting><Setting><Name>a606d019-eff4-c6b9-eec9-32d43913fa58</Name><Value>DatabasePhysicalMP</Value></Setting><Setting><Name>aa9fbc8a-e274-91e8-7731-ba324682cab9</Name><Value>DatabasePhysical</Value></Setting><Setting><Name>afb4f9e6-bf48-1737-76ad-c9b3ec325b97</Name><Value>rac2</Value></Setting><Setting><Name>b60a9e0e-5baa-9b0a-8201-6ddd697d060d</Name><Value></Value></Setting><Setting><Name>bf194186-a061-ccf1-94de-971988a79003</Name><Value></Value></Setting><Setting><Name>c2ec02fc-fa4d-65c9-82da-fa76476433eb</Name><Value>rac2</Value></Setting><Setting><Name>d87b0cd0-2149-5736-ab85-42ebddab12a2</Name><Value></Value></Setting><Setting><Name>e1165cbd-8778-5bc1-de07-af341d420068</Name><Value>GRD</Value></Setting><Setting><Name>f56fc436-4a31-48dc-3127-745e5a6d2800</Name><Value></Value></Setting><Setting><Name>fda3d28f-3f34-e51c-e1ad-b1413a70c4ac</Name><Value>GUARD</Value></Setting></Settings></ClassInstance>.