Third-Party Patching for SCCM

Patch over 335+ third-party updates across 190 products in SCCM

Knowledge Base ArticlesDownload Trial

Windows Event Logging Details for Patch My PC Publishing Service

We recently had a customer request our Publishing Service save certain events of publishing operations to the Windows event log.

In the customer’s scenario, they wanted to automate specific actions based on certain events. Using the Windows event log with specific event ID’s would allow for an easier experience than parsing the PatchMyPC.log

Windows-Event-Log-Publishing-Service-PatchMyPC

Below are current event ID’s we use for the actions listed below.

List of Events

WhenTextSourceIDLevel
The service sync startsStart of synchronizationWorker1000Info
The service has successfully made changes on one or more updatesSuccessfully published, revised or expired updates:Worker2000Info
The service has failed to make changes on one or more updatesUnsuccessfully published, revised or expired updates:Worker3000Error
An error occurred in the RunOnce methodAn error occurred while synchronizing. See the log for more details. [+ Exception message]Worker3001Error
There is a problem with the licenseThe current license doesn't allow you to use the publication serviceWorker3002Error
The catalog didn't pass the security checkThe catalog is not signed by Patch My PCWorker3003Error
The service has failed to make changes on one or more applicationsUnsuccessfully published, updated or revised applications:Worker3004Error
The service can't find the SCCM Admin consoleUnable to find SCCM Admin consoleWorker3005Error
The service has successfully made changes on one or more applicationsSuccessfully published, updated or revised applications:Worker4000Info
The service sync completedEnd of synchronizationWorker9000Info|Error