Hello

I have a master page with a user control. In one of my content pages, I update this usercontrol by forcing it to postback with a javascript function :

function postBackHiddenField(hiddenFieldID)
{
    var hiddenField = $get(hiddenFieldID);
    if (hiddenField)
    {
        __doPostBack(hiddenFieldID,'');
    }
}

It works with IE7 and Firefox, but with IE6 I get the following message :

The error description that appears when I double-click on the bottom left error image is the following :

 "The download of the specific resource has failed"

 I searched on google about the 12019 error code and people say that this can be fixed by disabling the Tracing, but I already did that and it didn't resolve it.

Anyone knows how I could make this thing work ?

EventValidation might also be the cause here, is your hiddenfield a server control?

Please refer to this: http://support.microsoft.com/kb/193625

Hi

 Thanks for your answers

@Paul : yes it's a server control, and I had to disable event validation and viewstate encryption because I had some error messages about the security :

@chetan : I already checked this page, it says that 12019 means that "The requested operation cannot be carried out because the handle supplied is not in the correct state." but that does not really explains why I get the error only on IE6, and how to fix it.

Have you got any solution ?

If got any point, post it.

it will help for others also

I'm working on it, I'll post a message if I find a solution.

But I definitely think that the problem comes from my usercontrol, not the postback

I have the same problem, but I'm not using any UserControls in my page. Last week I deployed a version of my App that was only tested with IE6 and was working fine.

Now I changed a lot of CSS code to get the page shown in IE6, IE7 and Firefox 2.x in the same way.

Right now my page works fine in IE7 and Firefox, but I get the 12019 error on every page/area, where I uses an ajax:UpdatePanel and click a server control inside the panel while browsing with IE6. There is no differece between Debug and Release Mode.

need some help please...

Thanks,
Dirk

 For what it's worth:

 I was getting the same error on my development machine, using the built-in server. Out of curiosity, I deployed it to a server2k3 box running full IIS, and I'm not getting the error.

-Jerod
 

Hi 

I'm already using IIS instead of the visual studio built-in server, under windows 2003 server.

But thanks anyway :)

Just using IIS the error was solved or did u set anything also ?

Just using IIS solved it for me...I didn't do anything "special". As to whether or not some other setting may have already existed on this server, I can't say for sure...it's hosting ~10 or so other sites.

The code's identical from my dev machine to the server...just using IIS fixed it. Can't say why...

-Jerod
 

Ok, I somehow got my problem fixed.

I was using IE6 for testing, but not the "real" IE6. I was using the version from multiple IE (since I have IE7 on my 2003 Server)

With the real IE6, I don't get this error anymore.

I had a similar error on my test machine using the MultipleIE IE6 which also disappeared when using the real IE6. Seems like a bug in the MultipleIE package.

I have this error with multiple IE6.

Debugging shows this:

msxml3.dll: The download of the specified resource has failed.

 So it appears IE6 is trying to use an older version of MSXML?  How do we fix this?

 Brilliant! 

 Same thing here, I was using IE6 from Multiple IE, and I was getting this exceptiong.  I knew that it had to be the browser, because it only happened in IE6, and using Fiddler I could see that the error actually popped up before a request to the server was even made - so it couldn't be something server side.

Guess I'll have to get a virtual machine or something setup for using real IE 6.

Thanks again guys, just answered this question for me after hours of messing around and searching google.
 

I experienced this same issue:

• IE6 from MultipleIEs gets a 12019 error
• "real" IE6 (on a different machine) works fine

Great!

I had same issue with using IETester v0.2.1 application on browser version IE 6.0.

Thanks

Akip