msxml3.dll error '80072ee2' - The operation timed out

This script has been running fine up until now (of course). I'm getting this error:

msxml3.dll error '80072ee2'

The operation timed out

/inv.asp, line 60


Function Mailbody
'on error resume next  
Set objXML = Server.CreateObject("MSXML2.ServerXMLHTTP")  
' Call the remote machine the request  
objXML.open "GET", SiteRoot & "inv.asp?whse=" & varWhse, False
objXML.SetRequestHeader "Content-Type", "text/html"
objXML.send()  

' return the response  
' clean up  
Mailbody = objXML.responsetext  
Set objXML = Nothing  
End Function  


Should I set varAsync = TRUE and do a loop:

objXML.open "GET", SiteRoot & "inv.asp?whse=" & varWhse, True
Do While objXml.readyState <> 4
DoEvents ???
Loop

as suggested at: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=362416&SiteID=1

Not sure how to make this work again....
LVL 1
globalwmAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

golfDoctorCommented:
If you haven't changed anything, try rebooting first.  
0
globalwmAuthor Commented:
I had installed MSXML 6.0 and tried using:

Set objXML = Server.CreateObject("MSXML2.ServerXMLHTTP.6.0")

- no change. Then I changed the line to:

Set objXML = Server.CreateObject("MSXML2.ServerXMLHTTP.4.0")

- no change.


I then rebooted the server - and it seems to have worked.


Can you tell me how to use Async = TRUE so it will wait for a response?

The open() method has varAsync parameter (third one) set to False which makes your send() call synchronous.  That means send() won't return until either entire response has been received or time out is detected.

You can set the parameter to True, call send() and enter into a loop to check for response.  You can add your own logic to decide what to do if you do not receive response within whatever amount of time you want to wait.

Since client code should not rely on the health of network connection (whether it's local network or Internet), you should not use synchronous send() method.  Always use asynchronous send() so that you can provide alternative experience to users in case something goes wrong.

0
golfDoctorCommented:
Reboot solved your original question didn't it?

Leave Async as false.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
ASP

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.