MSXML3 error '80072efd' in ASP 3

[Charlie Company]

I wonder if anyone might be able to help me on this one. I am using
MSXML3 in ASP to do a POST to a JSP page that's on the same server as my
ASP page. The error I get is:

msxml3.dll error '80072efd'
A connection with the server could not be established
/xmlhttp.asp, line 19

Line 19 reads, "xmlhttp.send PostString" and PostString is a valid POST
string.

I have confirmed that the JSP page is working properly by creating a
separate HTML page that does the same POST to the JSP, all is fine with
that. Additionally, I can POST to the JSP using EXACTLY the same code
which fails with the above error, provided I do it from a remote server.

So the problem seems to be something to do with the MSXML3.dll on the
server. Having googled for this issue I have not been able to find
anything of consequence except for one forum post where someone said they
have run across the same error, which would only occur when trying to do
a POST via MSXML *to the same server*.

Can anyone suggest a possible resolution to this issue?

Thanks in advance!
FB

[Ray Costanzo [MVP]]

It seems to me that your server may not be able to resolve the host name
you're using. Try using the IP address of the server in the URL and see if
that makes any difference.

Ray at work

"Charlie Company" <ch*****@viet.nam> wrote in message
news:Xn****************************@216.196.97.131 ...

I wonder if anyone might be able to help me on this one. I am using
MSXML3 in ASP to do a POST to a JSP page that's on the same server as my
ASP page. The error I get is:

msxml3.dll error '80072efd'
A connection with the server could not be established
/xmlhttp.asp, line 19

Line 19 reads, "xmlhttp.send PostString" and PostString is a valid POST
string.

I have confirmed that the JSP page is working properly by creating a
separate HTML page that does the same POST to the JSP, all is fine with
that. Additionally, I can POST to the JSP using EXACTLY the same code
which fails with the above error, provided I do it from a remote server.

So the problem seems to be something to do with the MSXML3.dll on the
server. Having googled for this issue I have not been able to find
anything of consequence except for one forum post where someone said they
have run across the same error, which would only occur when trying to do
a POST via MSXML *to the same server*.

Can anyone suggest a possible resolution to this issue?

Thanks in advance!
FB

[Charlie Company]

"Ray Costanzo [MVP]" <my first name at lane 34 dot commercial> wrote in
news:ep**************@TK2MSFTNGP14.phx.gbl:

It seems to me that your server may not be able to resolve the host
name you're using. Try using the IP address of the server in the URL
and see if that makes any difference.

It's the same physical server. I'm using Request.ServerVariables
("SERVER_NAME") to get the server name. Unfortunately using the IP address
doesn't work because of multi-homing being activated on the box. Or am I
missing something?

Thanks for the attempt though, Ray.

[Ray Costanzo [MVP]]

Using Request.ServerVariables("SERVER_NAME") doesn't guarantee name
resoltion. That variable will return what's in the URL, such as
www.yourdomain.kom. If your machine doesn't have a good DNS server set, it
won't be able to resolve that name, even though it's itself.

Ray at work

"Charlie Company" <ch*****@viet.nam> wrote in message
news:Xn****************************@216.196.97.131 ...

"Ray Costanzo [MVP]" <my first name at lane 34 dot commercial> wrote in
news:ep**************@TK2MSFTNGP14.phx.gbl:

It seems to me that your server may not be able to resolve the host
name you're using. Try using the IP address of the server in the URL
and see if that makes any difference.

It's the same physical server. I'm using Request.ServerVariables
("SERVER_NAME") to get the server name. Unfortunately using the IP address
doesn't work because of multi-homing being activated on the box. Or am I
missing something?

Thanks for the attempt though, Ray.

[Charlie Company]

"Ray Costanzo [MVP]" <my first name at lane 34 dot commercial> wrote in
news:OD**************@TK2MSFTNGP10.phx.gbl:

Using Request.ServerVariables("SERVER_NAME") doesn't guarantee name
resoltion. That variable will return what's in the URL, such as
www.yourdomain.kom. If your machine doesn't have a good DNS server
set, it won't be able to resolve that name, even though it's itself.

Well well welly well. Seems that name resolution was indeed the problem. I
aliased the site's IP to its name and used the IP, and Bob's my auntie's
live-in lover. Thanks so much for helping me to resolve this issue.