Error. Received 0x80072ee7 from WinHttpSendRequest - Intermittent

Question

_{Monday, May 19, 2014 4:26 PM}

We are running SCCM 2012 R2 on Windows Server 2012 with 6 MP/DP site system role servers servicing 6 of our locations. All MP/DP roles are https only.

At one of our locations, we are having difficulty imaging and frequently receiving

"Error. Received 0x80072ee7 from WinHttpSendRequest"

when attempting to image using bootable media. Our troubleshooting so far includes:

-same media can be used to image successfully at other sites
-new media created specifically referencing the location MP also fails the same way
-can ping both the fqdn and netbios name of MP from command prompt after failure occurs
-confirmed firewall off on MP/DP server
-confirmed portfast enabled on switch port
-if network ip helper set to location MP/DP address and pxe enabled, computer hangs at pxe portion of boot with blinking cursor

To make matters even more nebulous, the boot media "sometimes" will make it to the list of Task Sequences. However, in every case where that has happened, the image has not come down correctly.

I'm trying to make a determination of whether this is a network issue or could possibly be an issue with the DP/MP itself. It would appear that all the devices check in normally with the site, receive  Endpoint definitions, etc, but I can't say for sure the root cause of the issue.

Any suggestions for further troubleshooting/isolation?

All replies (4)

_{Tuesday, May 27, 2014 1:07 PM ✅Answered | 1 vote}

It looks like we may have some timing issues at this site. If we wait for approximately 3-5 seconds after the screen appears where we click next, then the issue does not occur.

To answer the specific question, if we hit F8, the moment that screen appears, we can confirm no ip address at that time.

So there may or may not be some network latency at this site, but if we just calm down a moment before proceeding, that seems to address the issue.

Thanks for your assistance.

_{Monday, May 19, 2014 8:24 PM}

0x80072ee7 = "The server name or address could not be resolved"

This is a name resolution issue.

IPHelpers have nothing to do with MP/DPs so not sure why'd you try that.

Where exactly is the above error occurring and what exactly is is happening when it occurs? Does it always fail in the same spot?

Jason | http://blog.configmgrftw.com

_{Monday, May 19, 2014 8:41 PM}

I tried PXE booting via IP helper addresses to determine if there was any difference between boot media and pxe booting with respect to my issue. I observed the included data that my workstations hung on pxe boot when attempting this which they do not do at our other locations. I included the information because it thought it might be relevant in determining whether or not I have a network issue or an issue with my MP/DP.

The issue occurs when using boot media, after the first splash screen when given the option to provide custom network/proxy settings. On selecting Next, the failure occurs almost immediately. The logs clearly indicate communication issues, but as soon as you F8 into a command prompt, you have full network connectivity.

Error. Received 0x80072ee7 from WinHttpSendRequest.    TSMBootstrap    5/15/2014 10:49:24 AM   536 (0x0218)
unknown host (gethostbyname failed) TSMBootstrap    5/15/2014 10:49:24 AM   536 (0x0218)
hr, HRESULT=80072ee7 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,8919)  TSMBootstrap    5/15/2014 10:49:24 AM   536 (0x0218)
sending with winhttp failed; 80072ee7   TSMBootstrap    5/15/2014 10:49:24 AM   536 (0x0218)
m_pHttpTransport->Send (0, 0, pServerReply, nReplySize), HRESULT=80072ee7 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,5159)  TSMBootstrap    5/15/2014 10:49:24 AM   536 (0x0218)
MPKeyInformation.RequestMPKeyInformationForMedia(szTrustedRootKey), HRESULT=80072ee7 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,9410)  TSMBootstrap    5/15/2014 10:49:24 AM   536 (0x0218)
Failed to get information for MP: https://server.my.org. 80072ee7.  TSMBootstrap    5/15/2014 10:49:24 AM   536 (0x0218)

It does always fail in the same spot.

_{Monday, May 19, 2014 8:56 PM}

What happens if you drop to a command-prompt before hitting next?

Can you ping the MP by FQDN *and* shortname?

Jason | http://blog.configmgrftw.com