none
After running Cleanup Wizard and reclaiming space, WSUS server now won't synchronize RRS feed

  • Question

  • Had severe space problem with WSUS server almost totally full. Finally managed to get the Cleanup Wizard in WSUS to run, first to decline expired and superseded updates, and then to delete "Unneeded update files". (Still have to run Wizard again (it did a *lot* of timing out), to delete "Unused updates and update revisions", but I have room on my server now and wanted to get it working again.) When I try to synchronize it manually, sync fails with the SOAP exception below. Looked in support article numbered 4482416, and when I ran the Power Shell commands that were given, I saw that my synchronization endpoint in WSUS configuration was already what they said (https://sws.update.microsoft.com) and that my redirector change number was already what they said (4002). I restarted services as they asked  and still get the SOAP exception on a manual sync attempt. Ideas? Thanks in advance! 

    ===

    "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)

    ===

    Monday, March 18, 2019 4:30 PM

Answers

  • Don't know why, but 5th try worked with same settings that I had. Seems OK now, will look at results of when sync's run automatically over next month or so. Thanks for reading! 
    • Marked as answer by SteveCRO2 Monday, March 18, 2019 6:36 PM
    Monday, March 18, 2019 6:36 PM

All replies

  • Don't know why, but 5th try worked with same settings that I had. Seems OK now, will look at results of when sync's run automatically over next month or so. Thanks for reading! 
    • Marked as answer by SteveCRO2 Monday, March 18, 2019 6:36 PM
    Monday, March 18, 2019 6:36 PM
  • No worries. It was not your fault, we all had the same issue

    https://www.reddit.com/r/sysadmin/comments/b2gmwz/wsus_sync_errors/

    https://social.technet.microsoft.com/Forums/en-US/6d282c86-56ad-451d-8d3c-69454a12106c/wsus-sync-error-soapexception-fault-occurred-internalservererror?forum=winserverwsus

    It seems Microsoft has fixed it. 

    Anyway to cleanup the WSUS Database here is a good guide: https://support.microsoft.com/en-us/help/4490644/complete-guide-to-microsoft-wsus-and-configuration-manager-sup-maint

    Monday, March 18, 2019 7:17 PM