MSXML2.ServerXMLHTTP yielding unrecognized response

[deathtospam@gmail.com]

'm using a VBScript/ASP page to submit a request to a (JSP) page on a
remote server, using "MSXML2.ServerXMLHTTP". Here's the main code I'm
using:

================================
....

Set oXmlServerHttp = Server.CreateObject("MSXML2.ServerXMLHTTP.3.0")
Call oXmlServerHttp.SetTimeouts(10000, 10000, 10000, 10000)
Call oXmlServerHttp.Open("GET", sRequestURL, True, Null, Null)
Call oXmlServerHttp.Send()

bResponseReceived = False
If (oXmlServerHttp.ReadyState = 4) Then
bResponseReceived = True
Else
bResponseReceived = oXmlServerHttp.WaitForResponse(30)
End If

....
================================

When I try to submit the call, I get the following error: "The server
returned an invalid or unrecognized response". The script is failing
on the line "bResponseReceived = oXmlServerHttp.WaitForResponse(30)" --
does anybody have an idea on why it is failing, and a possible solution?

[Brian Staff]

With an ASYNC call, I think you need to look at priming a callback function.

Maybe try a NON-ASYNC call and loop waiting for a "4" ReadyState.

Brian

[deathtospam@gmail.com]

If you're doing a non-asynchronous call, it waits until
oXmlServerHttp.Send() finishes before it returns a result -- which
means you won't need a loop to poll the ReadyState value. And it still
returns the same error message.....


-= Tek Boy =-

[Brian Staff]

<VA.00000310.a974d0c5@bstaffw2k.jda.corp.local>
<1135107097.120031.164520@g43g2000cwa.googlegroups .com>
Newsgroups: microsoft.public.inetserver.asp.components
NNTP-Posting-Host: gw.jda.com 65.160.56.2
Path: number1.nntp.dca.giganews.com!border2.nntp.dca.gig anews.com!border1.nntp.dca.giganews.com!nntp.gigan ews.com!nx02.iad01.newshosting.com!newshosting.com !news.alt.net!msrtrans!TK2MSFTNGP08.phx.gbl!tk2msf tngp13.phx.gbl
Lines: 1
Xref: number1.nntp.dca.giganews.com microsoft.public.inetserver.asp.components:45797

> If you're doing a non-asynchronous call, it waits until
> oXmlServerHttp.Send() finishes before it returns a result -- which
> means you won't need a loop to poll the ReadyState value. And it still
> returns the same error message.....

you're right...my bad!