Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Windows Server Update Service (WSUS) to Microsoft Update sync fails


View products that this article applies to.

Summary

When running standalone WSUS or System Center Configuration Manager integrated with WSUS, software update synchronizations may fail on an intermittent basis, while subsequent synchronizations may be successful. You may see one or more of the following errors.

Items of note from wsyncmgr.log (Configuration Manager site server log):

MM/dd/YYYY HH:mm:ss PM Synchronizing WSUS server contoso1.contoso.com ...

MM/dd/YYYY HH:mm:ss PM sync: Starting WSUS synchronization

MM/dd/YYYY HH:mm:ss PM sync: WSUS synchronizing categories

MM/dd/YYYY HH:mm:ss PM sync: WSUS synchronizing updates

MM/dd/YYYY HH:mm:ss PM Caught exception: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WsysSyncFailedException: ImportUpdateError: ~~ at Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS(SyncMode syncMode)~~ at Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.DoSync()

MM/dd/YYYY HH:mm:ss PM Sync done. Getting sync info...

MM/dd/YYYY HH:mm:ss PM Got sync info. NumSynced = 0

MM/dd/YYYY HH:mm:ss PM Sync failed: ImportUpdateError: . Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS

MM/dd/YYYY HH:mm:ss PM STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=CONTOSO1.CONTOSO.COM SITE=NEW PID=3196 TID=7588 GMTDATE=Day Mon dd HH:mm:ss.ssss YYYY ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS" ISTR1="ImportUpdateError: " ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0

MM/dd/YYYY HH:mm:ss PM Sync failed. Will retry in 60 minutes

 

Corresponding entries from SoftwareDistribution.log:

YYYY-MM-dd HH:mm:ss.sss UTC Error WsusService.42 CatalogSyncAgentCore.GetAndSaveUpdateMetadata 2 update(s) could not be imported into the local db even with retry

YYYY-MM-dd HH:mm:ss.sss UTC Error WsusService.42 CatalogSyncAgentCore.GetAndSaveUpdateMetadata Bad Update Revision #0: b55a761f-98c3-4e8f-be39-9dcfd35ceefc/201

YYYY-MM-dd HH:mm:ss.sss UTC Error WsusService.42 CatalogSyncAgentCore.GetAndSaveUpdateMetadata Bad Update Revision #1: e0dd10bf-612b-4524-b382-9655a5ee7d6e/200

YYYY-MM-dd HH:mm:ss.sss UTC Info WsusService.42 CatalogSyncAgentCore.UpdateSyncResultAndGenerateReportingEvent CatalogSyncThreadProcess: report subscription One or more updates failed to import to local database.

YYYY-MM-dd HH:mm:ss.sss UTC Info WsusService.42 EventLogEventReporter.ReportEvent EventId=386,Type=Error,Category=Synchronization,Message=Synchronization failed. Reason: System.Data.SqlClient.SqlException (0x80131904): Cannot insert the value NULL into column 'RevisionID', table '@AtLeastOneBundle'; column does not allow nulls. INSERT fails.

Error loading information from upd:BundledUpdates/upd:AtLeastOne/upd:UpdateIdentity for updateB55A761F-98C3-4E8F-BE39-9DCFD35CEEFC\201. Some update revisions in bundle information are not already present in the database.

A check of Synchronizations in the WSUS console will reveal results with status of Succeeded and Failed:

WSUS Sync fails1

Failed synchronization may be similar to the following (double click failed items in the screen to open a Synchronization Report):

WSUS sync fails2

↑ Back to the top


Cause

To be determined.

↑ Back to the top


Resolution

Synchronization/import of previously failed definition updates should be successful with subsequent software update synchronizations.

↑ Back to the top


More Information

If the Synchronizations history in the WSUS console fails to load, or is slow to enumerate, see the following article for information that can be used resolve this issue:


Clearing the Synchronization history in the WSUS console

↑ Back to the top


Keywords: Windows Server Update Services, wsus, System Center Configuration Manager 2012, System Center Configuration Manager 2012 R2, Configuration Manager 1802, Configuration Manager 1806, Configuration Manager 1810

↑ Back to the top

Article Info
Article ID : 4487379
Revision : 6
Created on : 1/11/2019
Published on : 1/11/2019
Exists online : False
Views : 410