Tuesday, 13 January, 2015 Normally I would be all over the search engines trying to figure out what is wrong with my WSUS server, but it's Patch Tuesday, Microsoft made some internal policy change regarding security updates since last time, I have made no configuration changes, and all of my WSUS on different networks are failing in the exact same way as of today. They'll get it figured out soon. Code: Synchronization Details Result: The upstream server experienced an unexpected error. Please try again at a later time. Details: 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) This is a "it's not you, it's Microsoft" notification for fellow WSUS admins out there.
Yep! But it's up now! Just now got mine to synchronize. I'd sure like to know what happened and how to prevent it!