?
Solved

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

Posted on 2007-04-05
3
Medium Priority
?
2,331 Views
Last Modified: 2008-01-09
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....
0
Comment
Question by:globalwm
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 16

Expert Comment

by:golfDoctor
ID: 18861675
If you haven't changed anything, try rebooting first.  
0
 
LVL 1

Author Comment

by:globalwm
ID: 18861725
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
 
LVL 16

Accepted Solution

by:
golfDoctor earned 2000 total points
ID: 18861742
Reboot solved your original question didn't it?

Leave Async as false.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Hello, all! I just recently started using Microsoft's IIS 7.5 within Windows 7, as I just downloaded and installed the 90 day trial of Windows 7. (Got to love Microsoft for allowing 90 days) The main reason for downloading and testing Windows 7 is t…
I was asked about the differences between classic ASP and ASP.NET, so let me put them down here, for reference: Let's make the introductions... Classic ASP was launched by Microsoft in 1998 and dynamically generate web pages upon user interact…
This is my first video review of Microsoft Bookings, I will be doing a part two with a bit more information, but wanted to get this out to you folks.
Add bar graphs to Access queries using Unicode block characters. Graphs appear on every record in the color you want. Give life to numbers. Hopes this gives you ideas on visualizing your data in new ways ~ Create a calculated field in a query: …

777 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question