Forum Discussion
Simon Bond
Sep 29, 2020Copper Contributor
Sync errors following 3rd Part Update Publishing
Hi Having sync'd the updates (Lenovo/HP in my case) and 'published' the updates I wanted, I then got the following errors in the wsycmgr.log: Generic exception : ImportUpdateFromCatalogSite fail...
Lewis-H
Sep 30, 2020Iron Contributor
Before any third-party updates can sync into SCCM, they need to be published to WSUS. The publishing operating can be performed using the following methods:
Patch My PC’s Publisher
SCCM’s Third-Party Software Update Catalogs Feature
System Center Updates Publisher (SCUP)
NOTE: When using our publishing service or the third-party software update catalog feature in SCCM, the publishing of third-party updates to WSUS is performed by a background service. If an update fails to publish to WSUS, you will need to review the SMS_ISVUPDATES_SYNCAGENT.log if using the third-party software update catalog feature in SCCM. If using the Patch My PC Publisher, you can review the PatchMyPC.log in the installation directory.
If there are no errors in the logs, the next step is to review if third-party updates exist in WSUS. Since the WSUS doesn’t directly expose third-party software updates in the WSUS console, you will need to use our publisher.
In the Advanced tab of our publishing service, you can run the Modify Published Updates wizard to view what updates are published to WSUS.
Review Third-Party Updates Published to WSUS
If the third-party updates that aren’t appearing in the SCCM console do exist in WSUS, proceed to the next troubleshooting steps.
Patch My PC’s Publisher
SCCM’s Third-Party Software Update Catalogs Feature
System Center Updates Publisher (SCUP)
NOTE: When using our publishing service or the third-party software update catalog feature in SCCM, the publishing of third-party updates to WSUS is performed by a background service. If an update fails to publish to WSUS, you will need to review the SMS_ISVUPDATES_SYNCAGENT.log if using the third-party software update catalog feature in SCCM. If using the Patch My PC Publisher, you can review the PatchMyPC.log in the installation directory.
If there are no errors in the logs, the next step is to review if third-party updates exist in WSUS. Since the WSUS doesn’t directly expose third-party software updates in the WSUS console, you will need to use our publisher.
In the Advanced tab of our publishing service, you can run the Modify Published Updates wizard to view what updates are published to WSUS.
Review Third-Party Updates Published to WSUS
If the third-party updates that aren’t appearing in the SCCM console do exist in WSUS, proceed to the next troubleshooting steps.