SCOM 2022 Operations manager products does populate with new values after upgrade from SCOM 2019 UR3

Question

Issue: Event ID 10801, Source Health Service Modules

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: 55f32a19-b0db-3a12-83d8-414183ff13b4
  HealthServiceId: 8b280675-0530-c007-a788-92eb2076fffb
  Microsoft.EnterpriseManagement.Common.DiscoveryDataInvalidClassPropertyValueException,The class property value specified in the discovery data item is not valid. The value needs to adhere to the class.
  Class property name: Microsoft.SystemCenter.Installed.OMProducts.InstallDate
  Class property value: 30.05.2022
  Rule ID: 55f32a19-b0db-3a12-83d8-414183ff13b4

Type definition for InstallDate in class Microsoft.SystemCenter.Installed.OMProducts (Microsoft.SystemCenter.OperationsManager.Internal) has been changed from string (SCOM 2019) to datetime (SCOM 2022).

The variable $InstallDate defined in SCOMInstalledProducts script (Microsoft.SystemCenter.OM.Products.Discovery) has not been changed to datetime.

Is there a quickfix available for this issue?

Regards,

Trond Jakobsen

Answer 1

Hi Trond (@Trond Jakobsen ),

I think the best approach would be to report this (ask) on the new SCOM feedback site, as it is being actively monitored by the SCOM PG. Such changes are defintely something they should be aware of. Here is the site:

System Center Operations Manager Feedback
https://feedback.azure.com/d365community/forum/2a49c9ee-4436-ec11-b6e6-00224824730c

Best Regards

----------

(If the reply was helpful please don't forget to upvote or accept as answer, thank you)
Regards,
Stoyan