Share via


Windows update failed - WS error: There was an error communicating with the endpoint at 'https://fe3.delivery.mp.microsoft.com/ClientWebService/client.asmx'.

Question

Monday, May 15, 2017 11:23 AM

Get this error (started on 25-apr-2017)

 [0]3540.39F4::05/14/2017-11:47:35.901 [endpointproviders]Got service 8B24B027-1DEE-BABB-9A95-3517DFB9C552 plugin Client/Server auth token of type 0x00000001
2017/05/14 11:47:35.9085851 13632 14836 ProtocolTalker  [0]3540.39F4::05/14/2017-11:47:35.908 [agent]ServiceId = {8B24B027-1DEE-BABB-9A95-3517DFB9C552}, Server URL = https://fe3.delivery.mp.microsoft.com/ClientWebService/client.asmx
2017/05/14 11:47:35.9090145 13632 14836 ProtocolTalker  [0]3540.39F4::05/14/2017-11:47:35.909 [agent]PT: Calling GetConfig on server
2017/05/14 11:47:35.9090190 13632 14836 IdleTimer       [0]3540.39F4::05/14/2017-11:47:35.909 [agent]WU operation (CAgentProtocolTalker::GetConfig_WithRecovery) started; operation # 11; does<NULL> use network; is<NULL> at background priority<NULL>
2017/05/14 11:47:35.9090385 13632 14836 WebServices     [0]3540.39F4::05/14/2017-11:47:35.909 [webserviceinfra]Auto proxy settings for this web service call.
2017/05/14 11:47:36.1305887 13632 14836 WebServices     [0]3540.39F4::05/14/2017-11:47:36.130 [client]Certificate used for SSL failed chain policy check: 0x80096004
2017/05/14 11:47:36.1308639 13632 14836 WebServices     [0]3540.39F4::05/14/2017-11:47:36.130 [webserviceinfra]WS error: There was an error communicating with the endpoint at 'https://fe3.delivery.mp.microsoft.com/ClientWebService/client.asmx'.
2017/05/14 11:47:36.1308645 13632 14836 WebServices     [0]3540.39F4::05/14/2017-11:47:36.130 [webserviceinfra]Web service call failed with hr = 80096004.

Is there a possibility to ingore the certification error?

All replies (3)

Thursday, May 25, 2017 11:09 AM

Hi DAtStone,

According to your report, it provides that Certificate used for SSL failed chain policy check: 0x80096004.

WSUS has always required a Microsoft SSL certificate, because the synchronization task is performed via SSL.

The WSUS Server runs a server synchronization via an SSL connection to Microsoft. In order to validate that SSL connection, your machine must have the correct SSL certificate installed. Without the certificate, it cannot authenticate that it is talking to the correct server.

You could check your internal root CA for revoked certificates and generate a new cert, assigned it.

If the issue still insists, I suggest that you could uninstall WSUS and reinstalled it.

Hope it will be helpful to you

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].


Tuesday, May 30, 2017 6:24 AM

Hi Carl,

Thanks for your answer.

Before the windows updates getting a cab file, now this is not the case? So before I could download the cab file in Internet explorer and the updates works. This not more the case now.

The problem is our firewall. If I try it directly connected then it works fine.

So your answer is correct, but not a solution for my problem.

I am talking with the guys of the firewall to solve the problem. 


Tuesday, May 30, 2017 8:55 AM

Hi DAtStone,

Thank you for the update on the issue.

If it needs change the firewall settings, as you said, you could only talk with your IT to change the firewall policy.

Best regards,

Carl

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].