Skip to main content

Bug Tracker

Side navigation

#6922 closed bug (invalid)

Opened August 20, 2010 12:35PM UTC

Closed August 20, 2010 11:55PM UTC

Last modified March 15, 2012 01:49PM UTC

Ajax Issue in IE7/8 - Error 12031

Reported by: sead.kolic Owned by:
Priority: Milestone: 1.4.2
Component: ajax Version: 1.4.2
Keywords: ajax, ie, 12031 Cc:
Blocked by: Blocking:


I have an issue with my script in IE8 when calling async ajax to my server side code. The server side code works fine and the script is fully working in Chrome and Firefox. The issue only occurs in Internet Explorer. This only happens sometimes, maybe each second/third time I call my function.

The error code I get is 12031: Internet Client Error: Connection Reset. What I understood from other sites, the ajax result returns, but the script throws an exception before completing the success handler.

Even if I set: dataType: 'json' and contentType: 'applications/json' the same error occurs.

Is is possible to provide a fix or a workaround for this issue? Thanks in advance.



The calling script:

var message = '';
ExecuteAction('myurl.php', 'fillgebruikersgroepen', message,
                function(data, textStatus, XMLHttpRequest) {
                function(xhr, ajaxOptions, thrownError) {

The method:

ExecuteAction: function(url, action, message, success, error) {
                type: "POST",
                cache: false,
                async: true,
                url: url + "?action=" + action,
                dataType: "html",
                data: message,
                success: success,
                error: error
Attachments (0)
Change History (1)

Changed August 20, 2010 11:55PM UTC by dmethvin comment:1

resolution: → invalid
status: newclosed

This isn't a bug report yet, so I would advise that you ask for help on a forum and provide a complete test page that can reproduce the problem.

As you mentioned, error 12031 is coming from the Winsock stack and means "connection reset". If you have any third-party toolbars or firewall software you should probably remove them. But again, the jQuery bug tracker is not an ideal place to troubleshoot a general problem like this.