locked
Soap Exception trying to sync my WSUS server RRS feed

  • Question

  • Hello,

    Though it is after 1pm ET, I seem unable to sync the new MS15-001 thru MS15-008 security updates to my WSUS box just now. I keep getting the following error -- anyone else?

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

    Tuesday, January 13, 2015 6:31 PM

All replies

  • Same problem here...
    • Marked as answer by Dick Dee Tuesday, January 13, 2015 7:04 PM
    • Unmarked as answer by Dick Dee Tuesday, January 13, 2015 7:24 PM
    Tuesday, January 13, 2015 6:49 PM
  • Thank you.

    Tuesday, January 13, 2015 7:04 PM
  • Manually importing from Microsoft update catalog also fails with error code 8DDD0010

    Tuesday, January 13, 2015 7:14 PM
  • Same problem as well.  The server I'm having issue with is running WSUS on Windows 2012 while my other WSUS server is running Windows 2012 R2 and synced with no issue.
    • Marked as answer by Dick Dee Tuesday, January 13, 2015 7:24 PM
    • Unmarked as answer by Dick Dee Wednesday, January 14, 2015 1:17 PM
    Tuesday, January 13, 2015 7:21 PM
  • My (failing and only) server is Windows Server 2012 as well.
    Tuesday, January 13, 2015 7:24 PM
  • I was able to work around this problem by changing the URL that WSUS attempts to synchronize with as recommended in this thread. Search for select muurl from tbConfigurationB to find the instructions I used.

    Tuesday, January 13, 2015 8:00 PM
  • same issue here on a 2012r2 WSUS set to sync from M$ for 2012r2 and 2008r2 updates, and fails with Event ID 20022 and SOAP error below. A second wsus server that supports Win 7 clients is able to sync no problem.

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

    Hopefully M$ fixes this and all is good tmrw.

    Tuesday, January 13, 2015 8:23 PM
  • Hmm. I tried that, but something seems to be changing it back to

    https://fe2.update.microsoft.com/v6

    Each time after I change it (and verify the change with another select) to:

    https://update.microsoft.com/v6

    Tuesday, January 13, 2015 8:25 PM
  • Same problem.
    Tuesday, January 13, 2015 8:41 PM
  • Same problem occurring here as well.

    Failing on Server 2012R2. My updates were synchronizing last week as I have been pushing updates for some days now. (I just built this server last week).

    Update last succeeded at 1/13/2015 3:25AM (US EST)


    • Edited by MikeCramer0559 Tuesday, January 13, 2015 9:11 PM Added last succeeded.
    Tuesday, January 13, 2015 9:09 PM
  • Same problem in North Carolina.  I'm running Windows Server 2012 R2.  Synchornizations started failing between 12:16pm EST (last success) and 1:16pm EST (first failure).
    • Edited by jrauman Tuesday, January 13, 2015 9:12 PM
    Tuesday, January 13, 2015 9:09 PM
  • Same issue here.

    I've also tried changing the tbConfigurationB with the associated URL and manually ran updates on the WSUS server. No change. I really hope MS gets it fixed soon or tomorrow is going to be a long night. 

    Tuesday, January 13, 2015 9:14 PM
  • After stopping all other WSUS services running on other machines connecting to Microsoft from the same public IP address sync works:

    "%Systemroot%\system32\sc.exe" \\host.domain.tld stop wsusservice
    Afterwards:
    "%Systemroot%\system32\sc.exe" \\host.domain.tld start wsusservice

    • Proposed as answer by wasserja Tuesday, January 13, 2015 9:46 PM
    Tuesday, January 13, 2015 9:16 PM
  • We ran into this on one of our accounts a few months ago.  We spent several hours with MS to diagnose the problem.

    We found that the problem was that the settings for the WSUS application in pool for IIS were set too low. The application pool memory limit had been set 2 GB, we changed it to unlimited. The restart rate had been set to 5 we also changed that to unlimited. We are no longer seeing the SOAP errors.

    Tuesday, January 13, 2015 9:25 PM
  • I am also having the same issue 2008R2, anyone know if it might be port related?

    you think restarting the service might work? ManServ

    • Edited by goofyer Tuesday, January 13, 2015 9:30 PM update
    Tuesday, January 13, 2015 9:26 PM
  • No, as said: "After stopping all other WSUS services running on other machines connecting to Microsoft from the same public IP address sync works..."
    Tuesday, January 13, 2015 9:38 PM
  • This sort of worked for one of my WSUS servers. I ended up having to restart all the wsus services.

    net stop wsusservice
    REM net stop MSSQL$MICROSOFT##SSEE
    net stop MSSQL$MICROSOFT##WID
    net stop BITS
    iisreset
    net start BITS
    REM net start MSSQL$MICROSOFT##SSEE
    net start MSSQL$MICROSOFT##WID
    net start wsusservice

    However I used the same process on my other WSUS server, but I'm still getting the same SOAP error.

    Tuesday, January 13, 2015 9:52 PM
  • might be just a timing thing.
    Tuesday, January 13, 2015 9:55 PM
  • I tried setting mine to unlimited, too, for the "WsusPool" -- no soap (pun intended).

    I suspect it is something on the MS end since so many of us are having the problem all at once.

    Tuesday, January 13, 2015 10:21 PM
  • is working for me now, i didn't do anything just tried resynching it
    Tuesday, January 13, 2015 10:41 PM
  • Still not working for me.
    Tuesday, January 13, 2015 10:54 PM
  • check the wsyncmgr.log, after 3 attempts i finally got all the updates
    Tuesday, January 13, 2015 11:57 PM
  • Mine has finally successfully synched just now...

    Wednesday, January 14, 2015 1:33 AM
  • Mine just started working now too.
    Wednesday, January 14, 2015 2:02 AM
  • Mine started working last night, too -- I noticed around 9pm ET.
    Wednesday, January 14, 2015 12:42 PM
  • Problem appears to have resolved itself. 
    Wednesday, January 14, 2015 12:53 PM
  • same here, issue resolved thx m$ft!
    Wednesday, January 14, 2015 2:28 PM
  • Changing the memory setting resolved my issue. Thank you!
    Sunday, July 30, 2017 8:11 AM