MSXML connection to server cannot be established

[MandoThrasher]

We're using the xmlhttp component to grab shipping data from UPS. It was working fine on our development server. When we moved the app to a server running ISA firewall the component cant get out to make a connection. We get the error "connection to server cannot be established". We've opened up everything in ISA that we know of, port 443, 80, all IP traffic, etc. What are we forgetting?

 

[codestorm]

What errorcode (status property) does the xmlhttp object return?

codestorm
Fire bad. Tree pretty. - Buffy
Kludges are like lies.
You're not a complete programmer unless you know how to guess.
I hope I never consider myself an 'expert'.
<insert witticism here>

 

[MandoThrasher]

Error Type:
msxml3.dll (0x80072EFD)
A connection with the server could not be established
/telecenter/order.asp, line 397

 

[mparter]

Read these:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winhttp/http/proxycfg.asp

http://msdn.microsoft.com/library/d...dk/htm/xml_obj_iserverxmlhttprequest_93i1.asp

 

[MandoThrasher]

All the examples are in C++, and I'm having a hard time translating to ASP.

Here's the object
Set objWinHttp = Server.CreateObject(&quot;WinHttp.WinHttpRequest.5.1&quot

 

[MandoThrasher]

proxycfg -u fixed it. thanks!

 

[bbolte]

i'm getting the same error but i don't have access to the server (shared hosting environment), so i can't run proxycfg. is there any other way to get around this error?

here is the code:

Set httpReq = Server.CreateObject("MSXML2.ServerXMLHTTP")
Set myXmlDoc = Server.CreateObject("MSXML2.DOMDocument")
httpReq.Open "post", webServiceUrl, False
httpReq.setRequestHeader "Content-Type", "text/xml"
httpReq.setRequestHeader "SOAPAction", "soapserver/soap:CreatePreview#CreateGraphics"
[b]httpReq.Send soapEnv[/b]   'error line
returnSoapEnv = httpReq.responseText

 

[MandoThrasher]

It turned out that proxycfg did not fix it. I had to make adjustments to the firewall.

FYI - the WinHttp object does not use the standard ports(80, 8080, 443, 8443). In our case, it was using port 2317.

I'm not sure about ServerXMLhttp, but my guess is that it works the same way.

proxycfg only works with WinHttp version 5, and not 5.1