Status of XMLHTTPRequest object is 12031 on call of its Send method

Try using the XHR objects as follows:

var xmlhttp = getXmlHttp(); // Get the proper XHR object for all browsers

function getXmlHttp() {
    var x = [
        function() { return new XMLHttpRequest(); },
        function() { return new ActiveXObject("Msxml2.XMLHTTP"); },
        function() { return new ActiveXObject("Microsoft.XMLHTTP"); }
    ];
    for (var i = 0; i < x.length; i += 1) {
        try { var f = x[i], r = f(); if (r !== null) { return r; } }
        catch(e) { continue; }
    }
    return null;
}

Select allOpen in new window

Badotz

Thanks for inputs but unfortunately these did not help! :-(

Actually we are migrating one ASP application to ASP.Net and this is JS portion on one common JS file. In it URL parameter now is .ASPX not .ASP. With .ASP URLs this function never returns any such exception.

Found this:

/*

IE status Property Value    Corresponding statusText Value

12002                       ERROR_INTERNET_TIMEOUT
12007                       ERROR_INTERNET_NAME_NOT_RESOLVED
12029                       ERROR_INTERNET_CANNOT_CONNECT
12030                       ERROR_INTERNET_CONNECTION_ABORTED
12031                       ERROR_INTERNET_CONNECTION_RESET
12152                       ERROR_HTTP_INVALID_SERVER_RESPONSE

*/

Select allOpen in new window

I am using IE6 only. Interestingly ASP application with same browser never gives any such exception in same JS code but migrated ASP.Net application gives this exception seldom with same JS code.

I already found status text against this status code 12031 but not root cause or fix unfortunately. :-(

The only clue here is "ERROR_INTERNET_CONNECTION_RESET" - perhaps your server is flaking?

Do you use a wi-fi connexion ?
Open command line and run a ping to your server (update server_adress with your server address) :

ping server_adress -n 1000000

Select allOpen in new window

leakim971
Its not Wi-fi connection.

gurvinder372:
Thanks for sharing these links. Actually the scenario is link a page is there that populates the list of pending of notifications of user and refreshes itself periodically by sending an asynchronous request to an ASPX page. The ASPX page in turn would call COM+ services to fetch latest list of notifications from the server and post it back to client. I am suspecting that irregular behavior by COM+ services might also cause connection reset to client but don't have enough evidence to prove it. As suggested in your first link, I don't think size of response is an issue here because 8 out of 10 times the notification page refreshes perfectly. It causes issues for hardly 2 of the 10 times.

I would keep you guys posted with my findings but please provide any other pointer if you think like I might be missing in my analysis.

>Its not Wi-fi connection.
OK, run the ping and browse the site, it may help you to know if you've a connexion problem with the server.

Which is what I suggested in http:#a4523087...

Thanks

No worries - glad to help.