nurturer69
asked on
Downstream WSUS server in a single domain has not been synchronizing.
Downstream WSUS server in a single domain has not been synchronizing. Tried reboot, then manual synchronization and get a failure with the following detail information within 30 seconds. Was working fine a month ago.
An HTTP error occurred:
WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: The handshake failed due to an unexpected packet format.
at System.Web.Services.Protoc ols.WebCli entProtoco l.GetWebRe sponse(Web Request request)
at System.Web.Services.Protoc ols.HttpWe bClientPro tocol.GetW ebResponse (WebReques t request)
at Microsoft.UpdateServices.S erverSync. ServerSync Compressio nProxy.Get WebRespons e(WebReque st webRequest)
at System.Web.Services.Protoc ols.SoapHt tpClientPr otocol.Inv oke(String methodName, Object[] parameters)
at Microsoft.UpdateServices.S erverSyncW ebServices .ServerSyn c.ServerSy ncProxy.Ge tAuthConfi g()
at Microsoft.UpdateServices.S erverSync. ServerSync Lib.Intern etGetServe rAuthConfi g(ServerSy ncProxy proxy, WebServiceCommunicationHel per webServiceHelper)
at Microsoft.UpdateServices.S erverSync. ServerSync Lib.Authen ticate(Aut horization Manager authorizationManager, Boolean checkExpiration, ServerSyncProxy proxy, Cookie cookie, WebServiceCommunicationHel per webServiceHelper)
at Microsoft.UpdateServices.S erverSync. CatalogSyn cAgentCore .SyncConfi gUpdatesFr omUSS()
at Microsoft.UpdateServices.S erve
An HTTP error occurred:
WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: The handshake failed due to an unexpected packet format.
at System.Web.Services.Protoc
at System.Web.Services.Protoc
at Microsoft.UpdateServices.S
at System.Web.Services.Protoc
at Microsoft.UpdateServices.S
at Microsoft.UpdateServices.S
at Microsoft.UpdateServices.S
at Microsoft.UpdateServices.S
at Microsoft.UpdateServices.S
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.