locked
WSUS synchronizing : Result: An error occurred in the upstream server. RRS feed

  • Question

  • Hello,

    When synchronizing WSUS following error occurs

    Server - Windows 2012 standard R2

    ------------------------------------------------------------------------------------------------------------------------------------------------

    Result: An error occurred in the upstream server.

    Details..

    SoapException: Fault occurred InvalidCookie
    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)

    ------------------------------------------------------------------------------------------------------------------------------------------------

    I updated sevaral times. But same error happens.

    Any idea ?

    Thank you.

    BR

    Anuradha


    technet


    Friday, August 31, 2018 2:27 AM

All replies

  • Hello Anuradha,

    Is there a upstream WSUS server in your environment?

    Is this issue happening on the downstream WSUS server?
     
    Could you find some error messages on the upstream WSUS server? IIS event viewer?
     
    Looking forward to your feedback.
     
    Best Regards,
    Ray Jia


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

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

    Friday, August 31, 2018 5:55 AM
  • Hello Ray Jia,

    Thank you for replying.

    Is there a upstream WSUS server in your environment?
    Is this issue happening on the downstream WSUS server?

    We have only one WSUS server.

    Could you find some error messages on the upstream WSUS server?

    "The server is failing to download some updates."

    IIS event viewer?

    No error message.

    BR

    Anuradha.


    technet

    Friday, August 31, 2018 7:02 AM
  • Hello,
     
    Since there is "invalidcookie", try to clean IE and other browser cookies and check if it works.
     
    Also check if there is a space issue in your WSUS server driver.
     
    And check softwaredistribution.log to see if there are some error information.
     
    Looking forward to your feedback.
     
    Best Regards,
    Ray Jia

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

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

    Friday, August 31, 2018 9:54 AM
  • FYI
    I am the same problem.

    :(

    Monday, September 10, 2018 8:40 AM
  • I'm having the same error.
    Tuesday, September 11, 2018 7:16 AM
  • On my W2012r2 I have installed from Microsodt Online Update both the preview updates

    KB4343891 and KB4346082

    deleted all IE temp items as someone suggested

    I dont know which one solved but now WSUS sync Succeeded.

    • Proposed as answer by Damiano.G Tuesday, September 11, 2018 9:33 AM
    Tuesday, September 11, 2018 9:23 AM
  • Well, I am not as lucky as you are. Syncing sometimes fails with only "Windows Defender" selected; meanwhile, it sometimes succeeds with a full line up of "Windows 7", "Windows 8.1", "Windows 10", "Windows Server 2008 R2" and "Windows Server 2012 R2" selected.

    The greatest moment of everyone's life is the moment of positive thinking.

    Monday, September 24, 2018 5:31 AM
  • I have also the same issue.

    At the moment it's "Windows Defender" that's trigger the error.
    Last week it was "Windows 10" and "Office 2016".

    I have test it on WSUS 3.x (Server 2008 R2), 6.3 (Server 2012 R2) and 10.x (Server 2016).
    On all WSUS the same issue.

    Any idea how to solve this?
    Is the reset of the WSUS a solution?

    https://blogs.technet.microsoft.com/sus/2016/10/18/recreating-the-susdb-and-wsus-content-folder-for-a-windows-server-2012-based-wsus-computer/

    Monday, September 24, 2018 6:18 AM
  • Well, I wouldn't do that.

    What I would do is to set up a Windows Server virtual machine, install a WSUS role, configure it, removal all auto-approval rules and synchronize.

    If that sync worked without an error, then yeah, try a reset.

    Monday, September 24, 2018 7:21 AM
  • i have the same problem , i have tried above but nothing work 
    Monday, September 24, 2018 8:51 AM
  • Well, I wouldn't do that.

    What I would do is to set up a Windows Server virtual machine, install a WSUS role, configure it, removal all auto-approval rules and synchronize.

    If that sync worked without an error, then yeah, try a reset.

    Ok, I have try it (Server 2016 with WSUS role).

    Doesn't seems to work. I think a reset of the catalog will not fix the issue.

    It's there a way to find out witch update generates the problem?
    Missing "Windows Defender Signatures" aren't good!

    Monday, September 24, 2018 12:51 PM
  • Hi,

    I solved de-selecting "Definition Updates" and forcing a manual Sync.

    After that, I selected again "Definition Updates" and everything seems to be working as expected.

    No Office 2016 in my env, Wsus on Win 2012 R2.

    Regards.

    Red.

    • Proposed as answer by Red Erik Monday, September 24, 2018 1:48 PM
    Monday, September 24, 2018 1:36 PM
  • Ok,

    since today 08:00 (UTC) all seems to work how excepted (3 synchronizations succeeded (All products and classifications)).
    Hope this will be the "normal" state for the next days.

    What I cannot understand is why MS don't communicate that, or have I not read on the right forum?

    Tuesday, September 25, 2018 10:02 AM
  • Me too! 😊 After a long time, I finally made a successful sync with the full complement of categories and classifications. It took an extraordinarily long time though.

    Of course, I did a WSUS server cleanup and a reindexed the WSUS database before the resync.


    The greatest moment of everyone's life is the moment of positive thinking.

    Tuesday, September 25, 2018 11:56 AM