Internet Explorer v6.0.3790.1830
Cipher Strength: 128-bit
Updated Versions:; SP1;
jscript.dll v5.6.0.8825
No other anti-spyware or toolbars in IE
AdAware, hijackthis, etc. all clean (like I said this is a brand new,
fresh load)
Also tried installing latest Java runtime, Directx, and JScript 5.6 -
none helped.
IE instantly closes and the following shows up in the event log...
Faulting application iexplore.exe, version 6.0.3790.1830, faulting
module jscript.dll, version 5.6.0.8825, fault address 0x0000368b.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 69 65 78 ure iex
0018: 70 6c 6f 72 65 2e 65 78 plore.ex
0020: 65 20 36 2e 30 2e 33 37 e 6.0.37
0028: 39 30 2e 31 38 33 30 20 90.1830
0030: 69 6e 20 6a 73 63 72 69 in jscri
0038: 70 74 2e 64 6c 6c 20 35 pt.dll 5
0040: 2e 36 2e 30 2e 38 38 32 .6.0.882
0048: 35 20 61 74 20 6f 66 66 5 at off
0050: 73 65 74 20 30 30 30 30 set 0000
0058: 33 36 38 62 368b
The crash does not happen on Windows 2003 or Windows XP when the
Microsoft Navision Attain client v3.60 is NOT installed. After
installing Navision Attain, google local crashes IE as shown above.
The workaround is to NOT install the client, but rather just copy the
working directory from another computer where it is installed.
Normally "C:\Program Files\Navision Attain\Client\"
We have tested and are using the Navision Attain Ceres client
successfully without having installed it, and now google local/maps
continues to work too. :-)
Obviously something in the Navision installer is copying old DLLs (or
something, on Windows 2003 servers and Windows XP) I already tried
reinstalling VB6 runtimes SP6 and MDAC 8.2 which the Navision client
appears to forcibly install, and that doesn't help, who knows what
else they are overwriting with an old version. :-(
Installation do not just put files into specific locations. They also make
a ton of registry entries. Perhaps the problem is in the registry. Your
work around avoids that portion of the installation.
Besides, it's not Microsoft's job to ensure that 3rd party software packages
run well, it's the author's responsibility.