locked
WSUS Synchronization failed RRS feed

  • Question

  • Hello,

    Since 3/26/2019 11:26 AM PST I cannot synchronized the classification "Updates" anymore. For the past two days as I was updating SCUP for Firefox and Google I did a lot of successful Synchronizations...

    I have one database SUSDB and one Repository shared by three SUPs.

    Wakeup by inbox drop	SMS_WSUS_SYNC_MANAGER	3/26/2019 11:44:01 AM	12656 (0x3170)
    Found local sync request file	SMS_WSUS_SYNC_MANAGER	3/26/2019 11:44:06 AM	12656 (0x3170)
    Starting Sync	SMS_WSUS_SYNC_MANAGER	3/26/2019 11:44:06 AM	12656 (0x3170)
    Performing sync on local request	SMS_WSUS_SYNC_MANAGER	3/26/2019 11:44:06 AM	12656 (0x3170)
    Full sync required due to changes in category subscriptions.	SMS_WSUS_SYNC_MANAGER	3/26/2019 11:44:06 AM	12656 (0x3170)
    Read SUPs from SCF for VRPSCCMPR01.ad	SMS_WSUS_SYNC_MANAGER	3/26/2019 11:44:06 AM	12656 (0x3170)
    Found 3 SUPs	SMS_WSUS_SYNC_MANAGER	3/26/2019 11:44:06 AM	12656 (0x3170)
    Found active SUP DGIT-SU-SCCM-P1.ad from SCF File.	SMS_WSUS_SYNC_MANAGER	3/26/2019 11:44:06 AM	12656 (0x3170)
    Found active SUP VRPSCCMIBCM01.ad from SCF File.	SMS_WSUS_SYNC_MANAGER	3/26/2019 11:44:06 AM	12656 (0x3170)
    Found active SUP VRPSCCMSU01.ad from SCF File.	SMS_WSUS_SYNC_MANAGER	3/26/2019 11:44:06 AM	12656 (0x3170)
    STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=VRPSCCMPR01.AD SITE=UCP PID=11236 TID=12656 GMTDATE=Tue Mar 26 18:44:06.373 2019 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	3/26/2019 11:44:06 AM	12656 (0x3170)
    Sync Surface Drivers option is not set	SMS_WSUS_SYNC_MANAGER	3/26/2019 11:44:57 AM	12656 (0x3170)
    Synchronizing WSUS server VRPSCCMSU01.ad	SMS_WSUS_SYNC_MANAGER	3/26/2019 11:44:57 AM	12656 (0x3170)
    STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=VRPSCCMPR01.AD SITE=UCP PID=11236 TID=12656 GMTDATE=Tue Mar 26 18:44:57.441 2019 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	3/26/2019 11:44:57 AM	12656 (0x3170)
    https://VRPSCCMSU01.ad:8531	SMS_WSUS_SYNC_MANAGER	3/26/2019 11:44:57 AM	15496 (0x3C88)
    Synchronizing WSUS server vrpsccmsu01.ad ...	SMS_WSUS_SYNC_MANAGER	3/26/2019 11:44:57 AM	15496 (0x3C88)
    sync: Starting WSUS synchronization	SMS_WSUS_SYNC_MANAGER	3/26/2019 11:44:57 AM	15496 (0x3C88)
    sync: WSUS synchronizing categories	SMS_WSUS_SYNC_MANAGER	3/26/2019 11:44:59 AM	15496 (0x3C88)
    Sync failed: UssInternalError: SoapException: Fault occurred~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall). Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS	SMS_WSUS_SYNC_MANAGER	3/26/2019 11:45:02 AM	12656 (0x3170)
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=VRPSCCMPR01.AD SITE=UCP PID=11236 TID=12656 GMTDATE=Tue Mar 26 18:45:02.449 2019 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS" ISTR1="UssInternalError: SoapException: Fault occurred~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	3/26/2019 11:45:02 AM	12656 (0x3170)
    Sync failed. Will retry in 60 minutes	SMS_WSUS_SYNC_MANAGER	3/26/2019 11:45:02 AM	12656 (0x3170)
    Setting sync alert to active state on site UCP	SMS_WSUS_SYNC_MANAGER	3/26/2019 11:45:02 AM	12656 (0x3170)
    Sync time: 0d00h00m56s	SMS_WSUS_SYNC_MANAGER	3/26/2019 11:45:02 AM	12656 (0x3170)
    Skipping Delete Expired Update relations since this is not a scheduled sync.	SMS_WSUS_SYNC_MANAGER	3/26/2019 11:45:02 AM	12656 (0x3170)
    Inbox source is local on VRPSCCMPR01.ad	SMS_WSUS_SYNC_MANAGER	3/26/2019 11:45:03 AM	12656 (0x3170)

    I unchecked Upgrades as seen in https://blog.ctglobalservices.com/configuration-manager-sccm/kea/getting-wsus-sync-errors-in-configmgr-1702/ and several threads...

    https://social.technet.microsoft.com/Forums/en-US/25643b79-779c-4c23-82b5-ec7eb206bf73/wsus-sync-failed-right-after-patch-tuesday-1142017?forum=ConfigMgrCompliance

    Or Microsoft issue?

    https://social.technet.microsoft.com/Forums/en-US/61ae15ff-b244-4135-b90d-09fcd28094a9/sup-sync-failing?forum=configmanagersecurity


    but still the same error:

    SCCM 1810

    I removed all classifications and start to synchronized successfully ...

    added classification one by one...

    it start failing when I checked "Updates"

    All other synchronizations went fine... including Upgrades

    I tried also:

    - Unselect all classifications in SUP

    - run SUP Synchronization in SCCM Console

    - run wsusutil.exe reset in one SUP

    - select all classifications in SUP

    - run SUP Synchronization in SCCM Console

    Still the same error...

    Any idea?

    Thanks,
    Dom


    Security / System Center Configuration Manager Current Branch / SQL









    • Edited by Felyjos Wednesday, March 27, 2019 2:34 AM
    Tuesday, March 26, 2019 6:51 PM

Answers

  • The sync error we experienced since 26-3 was the categorie: Update and narrowd down to the product: Windows 10 LTSB
    • Marked as answer by Felyjos Friday, March 29, 2019 2:39 PM
    Thursday, March 28, 2019 9:44 AM
  • Hello,

    I tried again after a full night of rest... for the machine :)

    - Unselect all classifications in SUP

    - run SUP Synchronization in SCCM Console

    - run wsusutil.exe reset in one SUP

    - select all classifications in SUP

    - run SUP Synchronization in SCCM Console

    This time it works fine... all patches from Microsoft and Third-Parties synchronized successfully and I was able to download and deploy them...

    it is really random

    Thanks,
    Dom


    Security / System Center Configuration Manager Current Branch / SQL

    • Marked as answer by Felyjos Wednesday, March 27, 2019 3:04 PM
    Wednesday, March 27, 2019 3:04 PM

All replies

  • Did you see what is the update which is failing ?

    you could manually insert that table and see whether all other updates are sync successfully.


    Kamala kannan.c| Please remember to click “Mark as Answer” or Vote as Helpful if its helpful for you. |Disclaimer: This posting is provided with no warranties and confers no rights

    Wednesday, March 27, 2019 3:26 AM
  • Hi,

    Error which is mentioned in the snippet indicates that issue is with WSUS synchronization. When WSUS tries to sync with Microsoft server, it fals at that time. 

    ===========================================

    sync: Starting WSUS synchronization SMS_WSUS_SYNC_MANAGER 3/26/2019 11:44:57 AM 15496 (0x3C88)
    sync: WSUS synchronizing categories SMS_WSUS_SYNC_MANAGER 3/26/2019 11:44:59 AM 15496 (0x3C88)
    Sync failed: UssInternalError: SoapException: Fault occurred~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall). Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS SMS_WSUS_SYNC_MANAGER 3/26/2019 11:45:02 AM 12656 (0x3170)
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=VRPSCCMPR01.AD SITE=UCP PID=11236 TID=12656 GMTDATE=Tue Mar 26 18:45:02.449 2019 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS" ISTR1="UssInternalError: SoapException: Fault occurred~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 3/26/2019 11:45:02 AM 12656 (0x3170)
    Sync failed. Will retry in 60 minutes 

    ===========================================

    As you have mentioned that, Please try below steps to find out the exact issue.

    1. On Primary sup, run the health check of WSUS with the below command:

    wsusutil.exe checkhealth

    Results will appear in the Application Event log. Please share the error, if there is any. 

    2. Run wsusutil.exe reset on Primary SUP.

    check and please share Software distribution.log.

    • Proposed as answer by veera0918 Sunday, November 3, 2019 9:02 AM
    Wednesday, March 27, 2019 6:24 AM
  • Hi,

    As my research, there could be an issue with the Windows Update service caused this issue, Premier Support have also confirmed that it’s a bug on their end. No ETA yet on a resolution. It could be fixed itself after a period of time.

    For reference:
    https://thesysadminchannel.com/sccm-wsus-sup-failing-to-sync-with-windows-updates/
    Also the post you have read:
    https://social.technet.microsoft.com/Forums/en-US/61ae15ff-b244-4135-b90d-09fcd28094a9/sup-sync-failing?forum=configmanagersecurity

    Regards,
    Allen

    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, March 27, 2019 6:31 AM
  • Hi, Allen Lio could be right and have already seen the phenomenon more often.
    Anyway, a WSUS cleanup can never hurt:

    Cleanup:

    powershell -executionpolicy bypass -file "https://github.com/bender-the-greatest/WSUS-Maintenance/blob/master/WSUS-Decline-Superseded-Updates.ps1" -UpdateServer <SCCMSITESERVER> -Port 8530


    #Important: If this is the first cleanup attempt, try only the first 2 parameters and then the complete parameters

    powershell Invoke-WsusServerCleanup -CleanupObsoleteComputers -CleanupObsoleteUpdates -CleanupUnneededContentFiles -CompressUpdates -DeclineExpiredUpdates -DeclineSupersededUpdates

    It is also possible to run this as scheduled Task

    Program: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
    Arguments: -Command “& ‘C:\scripts\WSUS-Maintenance\Decline-SupersededUpdatesWithExclusionPeriod.ps1’ -UpdateServer <SCCMSITESERVER> -Port 8530 -ExclusionPeriod 90”
    
    Program: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
    Arguments: -command Invoke-WsusServerCleanup -CleanupObsoleteComputers -CleanupObsoleteUpdates -CleanupUnneededContentFiles -CompressUpdates -DeclineExpiredUpdates -DeclineSupersededUpdates


    Optimize:
    https://gallery.technet.microsoft.com/scriptcenter/Optimize-and-cleanup-of-eb9d8640

    The Reindex Script https://gallery.technet.microsoft.com/scriptcenter/6f8cde49-5c52-4abd-9820-f1d270ddea61 can also run as a T-SQL job.

    BR, G.

    Edit

    and the complete Guide: https://support.microsoft.com/de-at/help/4490644/complete-guide-to-microsoft-wsus-and-configuration-manager-sup-maint

    Wednesday, March 27, 2019 9:33 AM
  • hi there, is it working now or are you still facing the same issue?

    https://twitter.com/SuneThomsenDK/status/1110799437310369792 

    • Proposed as answer by Kritika Patwal Wednesday, March 27, 2019 9:40 AM
    Wednesday, March 27, 2019 9:37 AM
  • Hello,

    I tried again after a full night of rest... for the machine :)

    - Unselect all classifications in SUP

    - run SUP Synchronization in SCCM Console

    - run wsusutil.exe reset in one SUP

    - select all classifications in SUP

    - run SUP Synchronization in SCCM Console

    This time it works fine... all patches from Microsoft and Third-Parties synchronized successfully and I was able to download and deploy them...

    it is really random

    Thanks,
    Dom


    Security / System Center Configuration Manager Current Branch / SQL

    • Marked as answer by Felyjos Wednesday, March 27, 2019 3:04 PM
    Wednesday, March 27, 2019 3:04 PM
  • The sync error we experienced since 26-3 was the categorie: Update and narrowd down to the product: Windows 10 LTSB
    • Marked as answer by Felyjos Friday, March 29, 2019 2:39 PM
    Thursday, March 28, 2019 9:44 AM