PRB: Installing Script Debugger May Disable Scripting (163500)
The information in this article applies to:
- Microsoft Visual Basic, Scripting Edition 1.1
- Microsoft Visual Basic, Scripting Edition 2.0
- Microsoft Internet Explorer (Programming) 3.0
- Microsoft Internet Explorer (Programming) 3.01
- Microsoft JScript 1.0
This article was previously published under Q163500 SYMPTOMS
After installing the Microsoft Script Debugger, all
scripting on documents loaded by Internet Explorer 3.0/3.01 may become
deactivated. Also, the script debugger may fail to do any syntax coloring
on the sections of VBScript or JScript in viewed pages.
CAUSE
A VBScript or JScript DLL with an older version may have been added to the
system.
RESOLUTION
Verify that the registry key at the following points to a VBScript DLL with a version stamp of 3.0.0.1217 or higher:
[HKEY_CLASSES_ROOT\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}
InprocServer32]
After installation of the Microsoft Script Debugger, this value typically
points to the following:
<Internet Explorer Directory>\system\VBscript.dll
Similarly, verify that the registry key at the following location points to a JScript DLL with the same version stamp: 3.0.0.1217:
[HKEY_CLASSES_ROOT\CLSID\{F414C260-6AC0-11CF-B6D1-00AA00BBBB58}
InprocServer32]
When fixing a mismatch, it is more appropriate to change the registry entry
to point to a VBScript or JScript DLL with the correct version than to
overwrite any other VBScript or JScript DLLs on the system.
STATUS
This behavior is by design.
MORE INFORMATION
VBScript/JScript DLLs marked with major version 1.0 or 1.1 shipped with
Internet Explorer 3.0/3.01.
VBScript/JScript DLLs marked with major version 2.0 shipped with the Active
Server Pages component of Internet Information Server 3.0.
VBScript/JScript DLLs marked with major version 3.0 are currently only
shipping with the BETA release of the Microsoft Script Debugger.
| Modification Type: | Minor | Last Reviewed: | 3/3/2005 |
|---|
| Keywords: | kbenv kbprb KB163500 |
|---|
|