Odd Error

[miranda]

I use Custom 404 Errors to display any server errors to my users and then send via email the actual error to me. I received this one today and I don't have a clue what it is telling me other than the send method of an XML object isn't available.

msxml3.dll
, (0x800C000B)
-2146697205

System error: -2146697205. 
/evaluations/assessment/assessment.asp, line 799

line 799 is where I call the send method.

Set oXMLHTTP = Server.CreateObject("Microsoft.XMLHTTP")
oXMLHTTP.Open "POST", "theEmployersURL", false
oXMLHTTP.setRequestHeader "Content-Type", "application/x-www-form-urlencoded" 
oXMLHTTP.Send("AssessmentID = " & UserID & "&ApplicantID = " & ATSID)

BTW this is a line of code that is called at least 100 times or more every day for this particular employer over a number of years and this is the first time I have gotten this message.

[Old Pedant]

So is it repeatable? You don't say. If not, I'd guess it was just a transport failure. That is, the SEND didn't get the response it was expecting.

And is there a reason you use the older Microsoft.XMLHTTP instead of MSXML3.ServerXMLHTTP? I can't see how it could matter for this code, and I certainly wouldn't change the code if the error is not repeatable. But if it is repeatable, it might be worth trying the more modern object.

[miranda]

Up until yesterday I had not had a problem with using Microsoft.XMLHTTP

I am one that believes that if it works don't change it.

I received 6 of those erorr messages in a span of less than a minute. (all from the same user) Which in itself isn't that unusual considering how often many users will click the refresh button if they get an error message on the screen.

I am just trying to figure out what the message is trying to tell me. (other than it had a problem sending the data)

[Old Pedant]

Well, look here:
http://msdn.microsoft.com/en-us/libr...=vs.85%29.aspx

INET_E_CONNECTION_TIMEOUT (0x800C000B)
The Internet connection has timed out.

I know you aren't using the software this refers to, but 0x800C000B is just a wrapper around 0x000B which is the underlying error.

I'm sure you are aware that the last 4 hex digits in an error code designate the underlying fault (e.g., 0x0005 is a memory fault, unable to read and/or write to a given address). So it would make sense that if 0x000B indicates a timeout that indeed my guess that you have a connection error--likely a timeout--is the underlying cause.

I would bet that 0x000B is mentioned in some C++ ".h" header file in the MSDN Library, but I couldn't find it in what I happen to have on this machine. I've got a lot of the old Library CDs, but it would take a loooonnng while to rummage through all of them.

So the problem may not be on your end. It might be that the receiver of the POST data isn't capable of processing the data fast enough. But this is still just a (slightly) educated guess.