IE Crashes when loading page with javascript

[Guest]

In one of our customer sites, when our webpage with javascript for dynamic
content, IE 6 crashes.

The IE version customer has is - 6.0.2900.2180.xpsp_sp2_gdr.070227-2254C0
on Windows XP. Is there any known issues with this IE version ?

Another question is, From where can I get and download this version. I
searched couldn't find any.

Thanks
_Pete

 

[Jon Kennedy]

Need to know more information - what do you mean by "IE 6 crashes"? Any
error messages? Is there a URL for us to look at?

See these articles for possible help w/ error messages in scripting:

Error Message When You Browse the Web: An Error Has Occurred in the Script
on This Page
http://support.microsoft.com/kb/306831/en-us

How to Troubleshoot Script Errors in Internet Explorer
http://support.microsoft.com/kb/308260/

A lot of the time, script errors are solved by reinstalling/updating the
scripting engines
Windows Script 5.7 for Windows XP
http://www.microsoft.com/downloads/...25-D896-482E-A0D6-524E7E844D81&displaylang=en

As for your other question, the version of IE you're looking at is
6.00.2900.2180, which is Internet Explorer 6 for Windows XP SP2. The string
of numbers and letters at the end are indicative of where that version was
obtained, and are pretty meaningless in this context. FWIW, the "gdr.xxx"
stands for
"general distribution release", and may change with the installation of
updates to IE core files. Make sure that machine also has all the latest IE
updates/security roll-ups, etc. from Windows Update. Windows Update will
use the version numbers gdr.xxxx to see if any files need updating and which
ones to use. For an example of how this works, and more info see:

What is included in a Microsoft patch?
http://searchwindowssecurity.techtarget.com/originalContent/0,289142,sid45_gci1036250,00.html
How to determine which version of Internet Explorer is installed
http://support.microsoft.com/kb/164539

 

[Guest]

Thanks Jon, for the detailed reply.
Unfortunately I do not have any logs other than a watson.log (got from the
event viewer application log) and it is binary data and not sure how view or
paste it in viewable format.

IE just closes as soon as when we go to this particular web page. Since this
is an internal network monitoring site, I am not able to make it available
publicaly.

I asked the customer to follow these steps and it seems to fix the issues in
few machines

1. Refresh scripting engine:
http://www.microsoft.com/downloads/...43-7E4B-4622-86EB-95A22B832CAA&displaylang=en

2. And to clear corrupt file in the cache, Tools | Internet Options and
click Delete Files. And then

2a. Start | Run | Regsvr32 vbscript.dll

2b. Start | Run | Regsvr32 jscript.dll


But on few of them they are still seeing the issue. So is there any way I
can verify that these steps are done in a particular machine.

regards
_Pete

 

[Robert Aldwinckle]

Thanks Jon, for the detailed reply.
Unfortunately I do not have any logs other than a watson.log (got from the
event viewer application log) and it is binary data and not sure how view or
paste it in viewable format.

You can get the equivalent data in a more readable format by Run...
(e.g. press Win-R and enter): drwtsn32
and then View the appropriate entry from the bottom list of Application Errors.
Then to capture that report right-click, Select All, Copy (or doubleclick, Ctrl-a,
Ctrl-c -- I can't remember which one of those procedures or both works)
and paste into a new Notepad window. The paste will put you at the bottom
of the dump, so then do a Find (Ctrl-f) Up for FAULT -> (assuming an English
version of Windows) and then page ahead to the Stack Back Trace.
You may find some clues in there about the names of the modules involved
in your crash. Similar data may be easier to access if ProcMon captures
the crash event. E.g. doubleclick on that record to open it.

IE just closes as soon as when we go to this particular web page. Since this
is an internal network monitoring site, I am not able to make it available
publicaly.

Well then try eliminating things that it does (e.g. disable ActiveX, Scripting,
Images, etc.) Tip: the IE Developer Toolbar can help with that type of
diagnosis. You can also use a diagnostic technique I call maximal prompting
e.g. use the Security Settings to Prompt anything which is already Enabled.
That can give you a very rudimentary trace and allow you to refine your symptom
description. Of course tracing with a script debugger might be even more
illuminating if that is possible... ; )


Good luck

Robert Aldwinckle
---