locked
WSUS Sync Error: SoapException: Fault occurred InternalServerError RRS feed

  • Question

  • Hi,

    From today, start getting title error when trying to sync WSUS with Microsoft Updates. I tried to remove multiple products like Office2016 from syncing but no luck. Also rebooted the server but no result. There are no changes made on <g class="gr_ gr_697 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar only-ins replaceWithoutSep" data-gr-id="697" id="697">WSUS</g> server and it was working fine until yesterday. Here is the full description of error;

    <g class="gr_ gr_977 gr-alert gr_gramm gr_inline_cards gr_run_anim Punctuation only-del replaceWithoutSep" data-gr-id="977" id="977">""</g>The upstream server experienced an unexpected error. Please try again at a later time.

    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.GetAndSaveUpdateMetadata(List`1 updates)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRe""

    Are others also experiencing a similar issue? 

    Any Suggestions, please......

    Thank you.

    Monday, March 18, 2019 4:02 PM

Answers

  • successful sync.  No changes after several failures earlier

    • Edited by cjmx Monday, March 18, 2019 5:13 PM .
    • Marked as answer by ssaleh365 Tuesday, July 9, 2019 8:58 PM
    Monday, March 18, 2019 5:13 PM

All replies

  • same issue here.  Removing office products from syncing did not work either.
    Monday, March 18, 2019 4:19 PM
  • I have the same error on both of my WSUS systems
    Monday, March 18, 2019 4:42 PM
  • Same here. Tried removing update classification and re-sync with no luck so far. 

    Any other thoughts on troubleshooting this?

    Monday, March 18, 2019 4:52 PM
  • I'm having the same issue. Looks like it has started this morning. All sync was okay yesterday.  Version: 6.2.9200.22167. Another WSUS running Version: 10.0.14393.2007 still ok, however products and categories are not the same.

    • Edited by DA-Sky Monday, March 18, 2019 5:06 PM
    Monday, March 18, 2019 4:57 PM
  • successful sync.  No changes after several failures earlier

    • Edited by cjmx Monday, March 18, 2019 5:13 PM .
    • Marked as answer by ssaleh365 Tuesday, July 9, 2019 8:58 PM
    Monday, March 18, 2019 5:13 PM
  • same issue here.  Removing office products from syncing did not work either.

    tried again and POW working...

    Monday, March 18, 2019 5:15 PM
  • Same here. Working now. 

    DA-Sky

    Monday, March 18, 2019 5:20 PM
  • Just sync'd. issue apparently resolved itself
    Monday, March 18, 2019 5:54 PM
  • Hi,

    problem is in old Microsoft update server https://fe2.update.microsoft.com/v6. New Microsoft update server is: https://sws.update.microsoft.com and you must change it in wsus configuration over the powershell.

    You can see it in the log: %ProgramFiles%\Update Services\LogFiles\SoftwareDistribution.log

    I have w2016 with wsus and now it is working fine.

    Here is the solution: Microsoft article 4482416 (I cannot put the link - new user).

    For WSUS on Windows Server 2012 and later versions:
    $server = Get-WsusServer
    $config = $server.GetConfiguration()
    # Check current settings before you change them 
    $config.MUUrl
    $config.RedirectorChangeNumber
    # Update the settings if MUUrl is https://fe2.update.microsoft.com/v6
    $config.MUUrl = "https://sws.update.microsoft.com"
    $config.RedirectorChangeNumber = 4002
    $config.Save()
    iisreset
    Restart-Service *Wsus* -v

    I hope this help.

    M.

    PS: I apologize for my English ;)


    Tuesday, April 9, 2019 7:32 AM
  • <Start Quote of original Message>

    Hi,

    problem is in old Microsoft update server https://fe2.update.microsoft.com/v6. New Microsoft update server is: https://sws.update.microsoft.com and you must change it in wsus configuration over the powershell.

    You can see it in the log: %ProgramFiles%\Update Services\LogFiles\SoftwareDistribution.log

    I have w2016 with wsus and now it is working fine.

    Here is the solution: Microsoft article 4482416 (I cannot put the link - new user).

    For WSUS on Windows Server 2012 and later versions:
    $server = Get-WsusServer
    $config = $server.GetConfiguration()
    # Check current settings before you change them 
    $config.MUUrl
    $config.RedirectorChangeNumber
    # Update the settings if MUUrl is https://fe2.update.microsoft.com/v6
    $config.MUUrl = "https://sws.update.microsoft.com"
    $config.RedirectorChangeNumber = 4002
    $config.Save()
    iisreset
    Restart-Service *Wsus* -v

    I hope this help.

    M.

    PS: I apologize for my English ;)

    <End Quote of original Message>

    My Windows 2016 WSUS Server would not Sync.

    My Windows 2012 R2 WSUS Server would.  Based upon this info I checked the Upstream WSUS Server.  The 2016 server was using the old Microsoft Server while the 2012 R2 server was using the new Microsoft Upstream server.  I made the changes as listed below and now my Windows 2016 WSUS Server is now syncing.

    Thanks for your Help!   :)



    Tuesday, April 9, 2019 7:28 PM