IE8 + Prototype AJAX = HTTP Status 12019

[web_dev_ajax]

I have a B2B web application that is developed on Struts JSP using
Prototype JS library (version 1.4.0) for AJAX. I have a client running
my application on IE8. She is intermittently getting the http status
code of 12019 (this is an IE specific status code for
ERROR_INTERNET_INCORRECT_HANDLE_STATE). She is the only person in the
client shop that gets the error and she cannot consistently reproduce
the error. However, after she gets the error, she can close her
browser and logs in again to go to the same page as before and not get
the error.

Initially the client shop was on IE6 SP2 and all the users got the
error 12019 intermittently also. After researching on the internet, we
recommended that they upgrade to IE8 to see if the error is resolved
because error 12019 is widely associated with IE6. Now that everyone
in the client shop has upgraded to IE8, and after about 2 months after
the upgrade, one user is beginning to get the error 12019 again. We
have been unable to reproduce the error under various scenarios in
Development.

One more thing to add, in one instance, the user that was getting the
12019 error code also got an exception message coming back from the
AJAX call. The exception message is: System error: -2146697208.

Googling this exception message indicates that it is tied to the error
"The download of the specific resource has failed." The same message
has been seen before by the same client when they were on IE6, but on
IE6, they saw the explicit message rather than the exception code.

Does anyone have this similar problem or know of a fix or know of a
way for me to reproduce this in order to find a solution?

Any help is appreciated. Thank you.

[Phil Petree]

I would try using a later version of proto on just that page.

--
You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group.
To post to this group, send email to prototype-s...@googlegroups.com.
To unsubscribe from this group, send email to prototype-scripta...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en.

[web_dev_ajax]

Thanks for the suggestion. That's an option that we plan to do with
the next Production release. Unfortunately, we have release cycles
that we have to adhere to and in the mean time, the client is unhappy
with getting these 12XXX status code errors. I have also done a diff
between version 1.4.0 and 1.7.0 and I don't see any differences that I
believe may help with these 12XXX status errors, but we won't know
until we do a release and see if the errors are still occurring.

I do have an update - it seems that ALL the users at the client shop
are now getting the 12XXX status code errors on IE8 (12019 and 12152
so far). The client shop claims that it's happening about once an
hour.

Thanks to some leads from Khan (http://groups.google.com/group/google-
web-toolkit/browse_thread/thread/f8059139eab52ccf), I'm now trying to
monitor the requests and responses to see if there's a pattern to
these seemingly intermittent errors, specifically request header
content-length that doesn't match the request body length.

Still, if anyone has any ideas or suggestions, I'd appreciate hearing
from you. Thanks.

On Dec 15, 1:55 pm, Phil Petree <phil.pet...@gmail.com> wrote:
> I would try using a later version of proto on just that page.

[Phil Petree]

Unless you're getting paid by the hour, you loose nothing by temporarily trying a later version of prototype.  Try eliminating the easy stuff before working on the hard and you'll avoid that headslap moment that comes when you realize you wasted two weeks for nothing.

[Eric]

Hi,

Is your application running on some kind of intranet network?

This seems close to an issue we got with IE9 and I wouldn't be
surprised if the issue was already present on IE8.
Basically, (and for some reason only known from MS), when on a
"Trusted Site" IE9 revert to compatibility mode, which from what we've
seen is mostly "IE6 mode".
If your issue is an "IE6 bug", that would explain why it is back on
IE8.
Sadly, there is no way to force IE9 to use its native (more) W3C
compliant from the server (if somebody knows a way, please post
it :o) ) but it is possible using menu options to change this.

Have a look here: http://blogs.msdn.com/b/ie/archive/2009/06/17/compatibility-view-and-smart-defaults.aspx

Eric

On Dec 16, 11:47 am, Phil Petree <phil.pet...@gmail.com> wrote:
> Unless you're getting paid by the hour, you loose nothing by temporarily
> trying a later version of prototype.  Try eliminating the easy stuff before
> working on the hard and you'll avoid that headslap moment that comes when
> you realize you wasted two weeks for nothing.