locked
WSUS Will not Synchronize RRS feed

  • Question

  • We are running Server 2016 with WSUS version 10.0.14393.2636. Up until 2 days ago, all was working as it should. Starting yesterday, synchronization started to fail and the console would crash when I clicked on Synchronizations (at 44%). I used SQL management studio to connect to the Windows Internal Database and cleared out the synchronization history. Now i can I can open the synchronization pane but it will not synchronize. I have made all of the IIS tweaks recommended in other posts to include:

    Queue Length - 25000

    CPU Limit Interval - 15

    Service Unavailable response type - TCPLevel

    Failure Interval - 30

    Max Failures - 60

    Private memory limit - 4096000

    I am receiving Event ID 10022. The last catalog synchronization attempt was unsuccessful.

    In the WSUS console, I see the following error: The upstream server experienced an unexpected error. Try again later. the synchronization details are as follows:

    SoapException: Fault occurred
    at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
       at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
       at Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetUpdateData(Cookie cookie, UpdateIdentity[] updateIds)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.WebserviceGetUpdateData(UpdateIdentity[] updateIds, List`1 allMetadata, List`1 allFileUrls, List`1& updatesWithSecureFileData, Boolean isForConfig)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.GetUpdateDataInChunksAndImport(List`1 neededUpdates, List`1 allMetadata, List`1 allFileUrls, Boolean isConfigData)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.GetAndSaveUpdateMetadata(List`1 updates)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRe

    We do not use a Proxy server and we are not getting any drop at our firewall.

    I have run a server cleanup both through the GUI and PowerShell

    I don't really want to uninstall and reinstall but I will if that is the only option.

    Not sure where to go from here. Any help would be much appreciated.


    Russ




    • Edited by RussGM Wednesday, December 5, 2018 7:41 PM
    Wednesday, December 5, 2018 7:36 PM

Answers

All replies

  • Am 05.12.2018 schrieb RussGM:

    We are running Server 2016 with WSUS version 10.0.14393.2636. Up until 2 days ago, all was working as it should. Starting yesterday, synchronization started to fail and the console would crash when I clicked on Synchronizations (at

    You are not alone:
    http://social.Technet.microsoft.com/Forums/en-US/winserverwsus/thread/7c3e5c52-13b2-49db-a631-19e23ac7763c#7c3e5c52-13b2-49db-a631-19e23ac7763c

    Winfried


    WSUS Package Publisher:
    https://github.com/DCourtel/Wsus_Package_Publisher
    http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx
    http://www.wsuswiki.com/Home
    GP-PACK - PRIVACY AND TELEMETRIE: http://www.gp-pack.com/

    • Marked as answer by RussGM Monday, January 14, 2019 3:28 PM
    Wednesday, December 5, 2018 8:29 PM
  • Hi RussGM

    Go to this threat : https://social.technet.microsoft.com/Forums/windowsserver/en-US/7c3e5c52-13b2-49db-a631-19e23ac7763c/wsus-2012r2-not-sycing?forum=winserverwsus

    I have same problems like the others. Since December the 3rd, admins WSUS like me as the same problem.

    For me I have uncheck "Updates" & "Office 2013". Others, uncheck Windows Server 2019. Maybe others updates or products seems in fault and we receive this SOAP error.

    Thursday, December 6, 2018 9:04 AM
  • Thanks for the reply. Based on your reference, I can sync with Updates & Office 2016 unchecked. Can someone from MS chime in and verify they know this an issue and they are working on it


    Russ

    Thursday, December 6, 2018 3:07 PM
  • Hello,
     
    It is on the MS side and Microsoft has fixed it. The synchronization should work now. Feel free to feedback.
     
    Best Regards,
    Ray

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

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

    Friday, December 7, 2018 8:49 AM
  • Hello,
     
    I am review cases. Has your issue been solved? Does the synchronization work now with office and updates checked?
     
    Feel free to feedback.
     
    Best Regards,
    Ray

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

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

    Monday, December 10, 2018 8:01 AM
  • You can see this question on the old thread. 

    https://social.technet.microsoft.com/Forums/en-US/afb7e03b-62a0-465c-b1e9-8b95300bae37/wsus-server-not-synchronizing-anymore?forum=winserverwsus
    Monday, December 10, 2018 8:34 AM
  • Yes, i have rechecked all my options and everything is now synching again.

    Russ

    Tuesday, December 11, 2018 7:22 PM
  • Hello,
     
    Glad to hear it.
     
    Best Regards,
    Ray

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

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

    Wednesday, December 12, 2018 10:55 AM
  • Hi all,

    We've published an article documenting the ongoing WSUS sync issues:
    https://support.microsoft.com/en-us/help/4487379/windows-server-update-service-wsus-to-microsoft-update-sync-fails

    Thanks,
    Andrei


    We could change the world, if God would give us the source code.


    Friday, January 11, 2019 7:46 AM
  • Hi,

    Same issue again, since 2019-03-17 11:00:00 UTC...

    regards

    Juergen


    SoapException: Fault occurred InternalServerError
    at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
       at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
       at Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetUpdateData(Cookie cookie, UpdateIdentity[] updateIds)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.WebserviceGetUpdateData(UpdateIdentity[] updateIds, List`1 allMetadata, List`1 allFileUrls, List`1& updatesWithSecureFileData, Boolean isForConfig)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.GetUpdateDataInChunksAndImport(List`1 neededUpdates, List`1 allMetadata, List`1 allFileUrls, Boolean isConfigData)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)
    • Edited by J. Juergen Monday, March 18, 2019 7:54 AM
    Monday, March 18, 2019 7:12 AM
  • Did you get any solution. We have the same issue started from 17 March 19 onwards.

    Abhijit

    Monday, March 18, 2019 11:25 AM
  • Should be fixed again now:
    https://twitter.com/TheFrankUK/status/1107701881550311424

    Thanks,
    Andrei


    We could change the world, if God would give us the source code.


    Monday, March 18, 2019 8:39 PM
  • Yes, works again since 2019-03-18 6:44:00 pm UTC+1

    Thanks,

    Juergen

    Tuesday, March 19, 2019 7:13 AM