Share via


Received 0x80072ee2 from WinHttpSendRequest.

Question

Thursday, November 14, 2019 8:53 AM

I recently have been getting socket and winhttp failures in our task sequences. I'm able to ping the FQDN of the MP and also nslookup to resolve dns so that seems to be ok. Certs also looks fine.

I attached log file, but I replaced domain names with xxxxx.xxxx.com

https://drive.google.com/open?id=1To0tqpBr4y4ZLlUWLHIh40jbiMkOjJPG

I will be very happy with any help.

All replies (3)

Thursday, November 14, 2019 10:03 AM | 1 vote

Error - 0x80072ee2 which = "The operation timed out"

Since you already tested ping and nslookup, check if any firewall is blocking the communication. 


Thursday, November 14, 2019 12:11 PM

It stopped work suddenly, I double checked firewall and it looks that nothing is blocking the communication.


Thursday, November 14, 2019 4:38 PM | 1 vote

Timeout issues are almost always the result of something in the network layer prevent the traffic from reaching the target or from making it back from the target. 

Ping proves connectivity of small amounts of traffic but not necessarily that larger conversations of actual data transferring connections will be successful. You should probably involve your network team to monitor the link to the DP and the server folks to examine the DP itself to check for faulty hardware just to validate. Ultimately, whatever is going on is outside the scope of visibility or control of ConfigMgr though.

Jason | https://home.configmgrftw.com | @jasonsandys