MSXML3.dll 80072efd and 800c0005 errors executing ServerXMLHTTP.send in classic ASP on Windows 7

Question

I have a classic ASP page that I'm trying to debug in IIS on Windows 7. This page works fine on another computer running Windows Server 2003 on a different network. Also, on a Windows 7 machine, I can successfully open this URL in a browser.

Page error while executing ServerXMLHTTP.send () with error:

msxml3.dll error '80072efd' A connection with the server could not be established 

This code looks like this (last line does not work):

 set xmlHTTP = server.CreateObject("MSXML2.ServerXMLHTTP") xmlHTTP.open "get", "http://stackoverflow.com", False xmlHTTP.send 

I searched around and the most useful search was to use NetSh to set proxies for winHTTP. The problem machine is located on a network that uses a proxy server. However, even after installing the proxy server and rebooting, I still get the same error.

The change

 set xmlHTTP = server.CreateObject("MSXML2.ServerXMLHTTP") 

to

 set xmlHTTP = server.CreateObject("MSXML2.XMLHTTP") 

gives a slightly different error:

 msxml3.dll error '800c0005' The system cannot locate the resource specified. 

I also tried installing MSXML4 SP3 and explicitly creating a v4 object using:

 set xmlHTTP = server.CreateObject("MSXML2.ServerXMLHTTP.4.0") 

I am still getting the same errors except the msxml4.dll message in the message.

Finally, I tried disabling the Forefront TMG proxy client by telling my browser not to use a proxy server and using netsh to reset the proxy for winHTTP. Nevertheless, the same errors, although the browser can still access the Internet.

From what I found, I believe that this should be a problem with connecting to this particular machine on the specific network in which it is located. However, I do not know what the problem is. Any suggestions gratefully received.

Answer 1

Solved this for my case, there are many other reasons why you might get this error. The short answer for me was: Verify that the custom .Net AppPool works as well and make sure your network allows them to access the Internet.

I downloaded Microsoft Network Monitor and looked at the traffic during the crash. The only traffic that could be connected was all that happened to our proxy server and consisted of a failed authentication attempt.

Then I checked the application pools in IIS and am pretty sure that the classic .Net AppPool was configured to use a local machine account that was not recognized by the proxy. Changing the account to use in the domain account fixed the error.

Answer 2

The only reasonable answer I found on google was this one. Hope this helps.

How can I read the contents of a remote webpage? [link removed]

General error you may get:

 > msxml3.dll error '80072efd' > A connection with the server could not be established 

Make sure the url is actually reachable. Perhaps you are writing the wrong domain name, or the site may actually not work. Testing using a browser from this machine or just running trace / ping. Please note that ping does not always return results, because many sites block all such traffic (mainly to eliminate DOS attacks). However, ping should, to a lesser extent, inform you of the IP address, which means that the domain name has been correctly resolved through DNS. Otherwise, your DNS server may be preventing the connection.

Answer 3

@Dan: Have you tried using the IP address for stackoverflow.com?

 set xmlHTTP = server.CreateObject("MSXML2.ServerXMLHTTP") xmlHTTP.open "get", "http://64.34.119.12/", False xmlHTTP.send response.write xmlHTTP.responseText 

Answer 4

This error can also occur when using HTTPS if the SSL session cannot be negotiated due to incompatible ciphers.

SSL Labs SSL Test can help determine which ones are compatible.

I know that the original question was not about an SSL connection, but I put it there since this is the first hit on Google when looking for an error message.

Answer 5

I found out that when I receive error 800C005 in my script, connecting to the soap server with which I was connecting matters.

It was necessary to specify several entries in my Windows HOSTS table in order to run the script without errors.

Insert mysoapserverurl.com, which gave the error, adding www.mysoapserverurll.com, which works, leaving only the URL from www. The script will throw an error again. (always msxml3.dll error).

Answer 6

This can happen if your URL is longer than 255 characters. Some like XML does not allow sending more than 255 characters