none
WSUS 3.0.6000.374 - catalog synchronization attempt was unsuccessful.

    Question

  • I have noticed that our WSUS synchronizations have been failing since last Friday evening with the following event: -

    Event Source: Windows Server Update Services
    Event ID: 10022
    Description:The last catalog synchronization attempt was unsuccessful.

    The only adjustment made to the WSUS configuration on Friday was to include Windows Server 2008 and Windows 7 updates in our products.

    I have reviewed the SoftwareDistribution.log file and identified the following errors: -


    2011-01-25 09:34:08.754 UTC Error WsusService.25 CatalogSyncAgentCore.ExecuteSyncProtocol 1 update(s) could not be imported into the local db even with retry
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.CatalogSyncThreadProcess()
       at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
       at System.Threading.ExecutionContext.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    2011-01-25 09:34:08.754 UTC Error WsusService.25 CatalogSyncAgentCore.ExecuteSyncProtocol Bad Update Revision #0: 29695606-6562-40c0-a569-600771e42eb9/100
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.CatalogSyncThreadProcess()
       at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
       at System.Threading.ExecutionContext.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()


    2011-01-25 09:34:08.801 UTC Info WsusService.25 CatalogSyncAgentCore.UpdateSyncResultAndGenerateReportingEvent CatalogSyncThreadProcess: report subscription One or more updates failed to import to local database.
    2011-01-25 09:34:08.801 UTC Info WsusService.25 EventLogEventReporter.ReportEvent EventId=386,Type=Error,Category=Synchronization,Message=Synchronization failed. Reason: System.Data.SqlClient.SqlException: Cannot insert the value NULL into column 'RevisionID', table '@BundleAll'; column does not allow nulls. INSERT fails.
    Error loading information from upd:BundledUpdates/upd:UpdateIdentity for update 29695606-6562-40C0-A569-600771E42EB9\100. Some update revisions in bundle information are not already present in the database.
    The statement has been terminated.
       at Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsoleteConnections(SqlException e)
       at Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteCommandNoResult()
       at Microsoft.UpdateServices.Internal.DatabaseAccess.CommonDataAccess.ExecuteSPImportUpdate(Int32 upstreamServerLocalId, String xmlUpdateBlob, Byte[] xmlUpdateBlobCompressed, Int32& localRevisionId)
       at Microsoft.UpdateServices.Internal.DatabaseAccess.CommonDataAccess.ImportUpdate(Int32 ussRevLocalId, String xmlUpdateBlob, Byte[] xmlUpdateBlobCompressed, String xmlSdpBlob, Int32& localRevisionId)
       at Mic.
    2011-01-25 09:34:08.879 UTC Info WsusService.3 CatalogSyncAgent.UpdateServerHealthStatusBasedOnError ServerHealth: Updating Server Health for Component: CatalogSyncAgent, Marking as Not Running

    The problem appears to be related to the statement "update revisions in bundle information are not already present in the database".

    I then performed a full WSUS Server Cleanup thinking this may resolve the issue but unfortunately this was not the case and performing a manual update fails with the same error messages.

    I'd appreciate any suggestions on how to resolve this issue. If this turns out to become a painful excersie, I'm considering enabling the WSUS Server Role on a new Windows 2008 server recently implemented.

    More information on request...

    Thanks in advance.

    Tuesday, January 25, 2011 10:58 AM

Answers

All replies