seit dem 10.04. schlägt auf unserem Empirum 17.0.2 der PM Katalog-Sync fehl.
So sieht das Ganze im Debugview aus:
Code: Select all
[1464] ThreadId=2132 [PM] Downloading metadata to C:\Users\svc_wp_prd_EmpSvc\AppData\Local\Temp\PatchManagementWorkData
[1464] ThreadId=2132 [PMRt] Patch Manager: Get partner manifest file
[1464] ThreadId=2132 [PMRt] https://content.ivanti.com/data/partner/sdk/93/manifest/partner.manifest.xml successfully downloaded to C:\Users\svc_wp_prd_EmpSvc\AppData\Local\Temp\PatchManagementWorkData\partner.manifest.xml
[1464] ThreadId=2132 [PMRt] Start Catalog download
[1464] ThreadId=2132 [PMRt] https://content.ivanti.com/data/WindowsPatchData.zip successfully downloaded to C:\Users\svc_wp_prd_EmpSvc\AppData\Local\Temp\PatchManagementWorkData\WindowsPatchData.zip
[1464] ThreadId=2132 [PMRt] No action has been assigned to the alarm with event name <CATALOG_SYNC_ERROR>
[1464] Error during job execution: Input string was not in a correct format.
[1464] ThreadId=2132 [MXCORE] Error during job execution: Input string was not in a correct format.
[1464] ThreadId=2132 [MXCORE] call backend log msg id 12
[1464] ThreadId=2132 [MXCORE] => CREATE ENTRY:104800.3262006 STATE:Running MSG:'12' OID:CatalogSync OT:Computer IOI:PM
[1464] ThreadId=2132 [MXCORE] => UPDATE ENTRY:3262006 STATE:Failure MSG:'Input string was not in a correct format.' EXCEPTION:Input string was not in a correct format.
Viele Grüße,
Michael Weyershäuser
Edit:
Nach einer Reinstallation der Dienste auf dem Empirum-Server läuft der Sync wieder...