none
WSUS Synchronization Failed 404 , 2012 Server help!

    Question

  • Since about a week ago WSUS Synchronizations have failed . Tried uninstalling any previous windows updates. 

    WebException: The request failed with HTTP status 404: Not Found.
    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.GetAuthConfig()
       at Microsoft.UpdateServices.ServerSync.ServerSyncLib.InternetGetServerAuthConfig(ServerSyncProxy proxy, WebServiceCommunicationHelper webServiceHelper)
       at Microsoft.UpdateServices.ServerSync.ServerSyncLib.Authenticate(AuthorizationManager authorizationManager, Boolean checkExpiration, ServerSyncProxy proxy, Cookie cookie, WebServiceCommunicationHelper webServiceHelper)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.SyncConfigUpdatesFromUSS()
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)

    Tried resetting WSUS with the command line tool.

    Standalone install not SCCM. 

    These sites are allowed through the proxy and I can browse to them on the server.

    • http://windowsupdate.microsoft.com
    • http://*.windowsupdate.microsoft.com
    • https://*.windowsupdate.microsoft.com
    • http://*.update.microsoft.com
    • https://*.update.microsoft.com
    • http://*.windowsupdate.com
    • http://download.windowsupdate.com
    • http://download.microsoft.com
    • http://*.download.windowsupdate.com
    • http://test.stats.update.microsoft.com
    • http://ntservicepack.microsoft.com

    I've Also Verified "Network Service" has read write access to the content directory. 

    Only thing I can see that is changed is that download.windowsupdate.com redirects to another site (which is also unblocked.

    If you reply with a link to this technet article http://technet.microsoft.com/en-us/library/cc708514(v=ws.10).aspx

     I will find you.. 

    Thursday, July 24, 2014 9:01 PM

Answers

  • Since about a week ago WSUS Synchronizations have failed . Tried uninstalling any previous windows updates. 

    WebException: The request failed with HTTP status 404: Not Found.

    One of two things causes an HTTP 404 trying to find a website, and neither of them have anything to do with WSUS. :-)

    Either your DNS resolver is returning bad IP Address information and Microsoft Update isn't on the other end of the connection,

    or a perimeter device is interfering and not returning the proper error code. (An interfering device should be returning a '403', not a '404'.)

    Tried resetting WSUS with the command line tool.

    Well, that didn't help. It's the wrong tool, and now you'll need to wait until this process fully completes within the database before you can do anything else. In some environments, this task has taken DAYS to complete. Post back when the sqlservr.exe process is no longer using all available CPU cycles.


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    • Marked as answer by PJChampion Friday, July 25, 2014 2:04 AM
    Friday, July 25, 2014 1:37 AM
  • It actually was a 403 where WSUS was reporting a 404. Great job WSUS on your reporting! So in this case the 404 did have to do with WSUS and its error reporting.

    Wireshark showed this to me.  Needed to add "go.microsoft.com" to allowed sites. Why? I dont know..

    Went ahead an added *.microsoft.com 

    Thank you Microsoft for keeping your list of sites up to date!

    And for those who are going to say.. "oh he just typed one of the .microsoft sites wrong and that's why the wildcard fixed it. Here's the list of allowed sites through the proxy

    .download.windowsupdate.com, .update.microsoft.com, update.microsoft.com, .windowsupdate.com, .windowsupdate.microsoft.com, download.microsoft.com, download.windowsupdate.com, ntservicepack.microsoft.com, windowsupdate.microsoft.com, wustat.windows.com, www.microsoft.com, s-microsoft.com, test.stats.update.microsoft.com, 

    • Marked as answer by PJChampion Friday, July 25, 2014 2:04 AM
    Friday, July 25, 2014 2:04 AM

All replies

  • Since about a week ago WSUS Synchronizations have failed . Tried uninstalling any previous windows updates. 

    WebException: The request failed with HTTP status 404: Not Found.

    One of two things causes an HTTP 404 trying to find a website, and neither of them have anything to do with WSUS. :-)

    Either your DNS resolver is returning bad IP Address information and Microsoft Update isn't on the other end of the connection,

    or a perimeter device is interfering and not returning the proper error code. (An interfering device should be returning a '403', not a '404'.)

    Tried resetting WSUS with the command line tool.

    Well, that didn't help. It's the wrong tool, and now you'll need to wait until this process fully completes within the database before you can do anything else. In some environments, this task has taken DAYS to complete. Post back when the sqlservr.exe process is no longer using all available CPU cycles.


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    • Marked as answer by PJChampion Friday, July 25, 2014 2:04 AM
    Friday, July 25, 2014 1:37 AM
  • It actually was a 403 where WSUS was reporting a 404. Great job WSUS on your reporting! So in this case the 404 did have to do with WSUS and its error reporting.

    Wireshark showed this to me.  Needed to add "go.microsoft.com" to allowed sites. Why? I dont know..

    Went ahead an added *.microsoft.com 

    Thank you Microsoft for keeping your list of sites up to date!

    And for those who are going to say.. "oh he just typed one of the .microsoft sites wrong and that's why the wildcard fixed it. Here's the list of allowed sites through the proxy

    .download.windowsupdate.com, .update.microsoft.com, update.microsoft.com, .windowsupdate.com, .windowsupdate.microsoft.com, download.microsoft.com, download.windowsupdate.com, ntservicepack.microsoft.com, windowsupdate.microsoft.com, wustat.windows.com, www.microsoft.com, s-microsoft.com, test.stats.update.microsoft.com, 

    • Marked as answer by PJChampion Friday, July 25, 2014 2:04 AM
    Friday, July 25, 2014 2:04 AM