ASP HTTP XML WebService readystate question

I have an existing web service that is HTTP XML based (ASP not ASP.Net). It
runs fine in all environments and has been very stable and static. I have a
single test ASP page that I use to build the request, form the XML and submit
the request to any server I choose via radio button selection (dev, test,
prod, etc).

The underlaying data tables used by the web service to return result are
being updated with some new values and I needed to run regression tests to
verify process still works.

I'm getting issues with my test ASP page sending requests to the Dev web
service for any request. Requests to other servers from same test ASP page
run fine. I've verified web service code is the same on all servers. I am
using the exact same test ASP page to build/send requests.

I log data on server side and can see that the Dev server is getting
requests, processing them and sending response back.

On test ASP side I can see that I'm stuck with objXmlHttp.readystate=1. It
just never moves on to 4. Same request to other servers returns response
using the same test ASP page session.

I don't think this is an application issue. I think it must be a server
side setting of some sort on the Dev box that has changed.

v-wywang
Mon Feb 04 03:36:22 CST 2008

Hello Dmartin,

According to your description, your issue is that objXmlHttp.readystate
doesn't change when connection to the web service on your Dev box. This
issue only occurs when your ASP page connect to your Dev Box. When
connecting to other server, your ASP code works fine. If I misunderstood
anything, please don't hesitate to correct me.

Have tried to run your ASP page on other client machine? Therefore, we can
verify if this is a Server side issue or Client side issue.

After that, I'd like to suggest you trace the SOAP message both on your
problematic DEV box and Other Test/Prod boxes. Please compare them, and
check what the difference is between them. I think we may get some
information.
To trace SOAP message, you may use SOAP Toolkit.
http://www.microsoft.com/Downloads/details.aspx?familyid=C943C0DD-CEEC-4088-
9753-86F052EC8450&displaylang=en

Hope this helps. If there is anything unclear, please feel free to let me
know. We are glad to assist you.

Have a great day,
Best regards,

Wen Yuan
Microsoft Online Community Support
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

dmartin
Mon Feb 04 08:53:05 CST 2008

I've had 4 people try it. Oddly, 1 worked, the other 3 plus myself failed.
The one that worked is on a completely different subnet. His PC has InterDev
on it and I was hoping he could step thru it for me.

We aren't using SOAP, Just HTTP & XML.

doug

"WenYuan Wang [MSFT]" wrote:

> Hello Dmartin,
>
> According to your description, your issue is that objXmlHttp.readystate
> doesn't change when connection to the web service on your Dev box. This
> issue only occurs when your ASP page connect to your Dev Box. When
> connecting to other server, your ASP code works fine. If I misunderstood
> anything, please don't hesitate to correct me.
>
> Have tried to run your ASP page on other client machine? Therefore, we can
> verify if this is a Server side issue or Client side issue.
>
> After that, I'd like to suggest you trace the SOAP message both on your
> problematic DEV box and Other Test/Prod boxes. Please compare them, and
> check what the difference is between them. I think we may get some
> information.
> To trace SOAP message, you may use SOAP Toolkit.
> http://www.microsoft.com/Downloads/details.aspx?familyid=C943C0DD-CEEC-4088-
> 9753-86F052EC8450&displaylang=en
>
> Hope this helps. If there is anything unclear, please feel free to let me
> know. We are glad to assist you.
>
> Have a great day,
> Best regards,
>
> Wen Yuan
> Microsoft Online Community Support
> ==================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>

v-wywang
Tue Feb 05 01:38:38 CST 2008

Hello Doug,
Thanks for your reply.

As far as I know, SOAP is a standard protocol for accessing a Web Service.
I'm sorry, but I'm not sure which protocol you are using to consume
Webservice without SOAP now.

Is it possible for you to paste the XML message which you sent to
webservice in your ASP Page? Therefore, we can know more about the
technology you are using in this case. Without it, we cannot perform
further research so far.

If you have any more concern, please feel free to let me know. We are glad
to assist you.
Have a great day,
Best regards,

Wen Yuan
Microsoft Online Community Support
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

dmartin
Tue Feb 05 08:28:21 CST 2008

No I can't provide the request details. I do not have much in the way of
tools to trap the messages. This is an older web service. It doesn't use
Soap. It just uses HTTP POST passing an XML document as the data. It
behaves much the same as a Soap message without the Soap envelope or headers.

"WenYuan Wang [MSFT]" wrote:

> Hello Doug,
> Thanks for your reply.
>
> As far as I know, SOAP is a standard protocol for accessing a Web Service.
> I'm sorry, but I'm not sure which protocol you are using to consume
> Webservice without SOAP now.
>
> Is it possible for you to paste the XML message which you sent to
> webservice in your ASP Page? Therefore, we can know more about the
> technology you are using in this case. Without it, we cannot perform
> further research so far.
>
> If you have any more concern, please feel free to let me know. We are glad
> to assist you.
> Have a great day,
> Best regards,
>
> Wen Yuan
> Microsoft Online Community Support
> ==================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>

v-wywang
Wed Feb 06 02:03:13 CST 2008

Hello dmartin,
Thanks for your reply.

I understood you created a XML document object and pass it to web side by
HTTP post, correct? Thereby, you didn't use "SOAP". XML transfers to web
service by HTTP. If I misunderstood anything here, please don't hesitate to
correct me.

It sounds xml data has been sent to web server correctly. But xmlhttp
object cannot get response. Do you disable the firewall between your client
and web service? If you have already disabled them, we still suggest you
may trace the request and response on your
problematic DEV box and Other Test/Prod boxes. We can compare what the
difference between them. Thereby, we can get more information.

To trace HTTP request and response, we suggest to use Fiddler. It's free
software from Microsoft. You can get it from
http://www.fiddler2.com/Fiddler2/version.asp.

Hope this helps, let me know if there is anything unclear. We are glad to
assist you.

Have a great day,
Best regards,

Wen Yuan
Microsoft Online Community Support
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.