Script debugger (Microsoft Script Editor) won't open from Internet Explorer 6

This question has been in another section of EE for over six weeks without being resolved, so I am deleting the original question and reposting it here.

I want to use the Script Editor that comes with Office XP (2002) as a debugger for client-side Javascript that is running in Internet Explorer 6. My environment is Windows XP Professional, Office XP (2002) Professional, FrontPage 2002. I am an Administrator on my machine.

The 2 main symptoms are:

1. In Internet Explorer, if I use View, Script Debugger, Open - nothing happens.
2. If I open a web page that has a Javascript bug, I get the message "A Runtime Error has occurred. Do you wish to Debug?". I press Yes, but the debugger doesn't open, nor do I get a dialog to choose a debugger.

I can get the debugger to attach to iexplore by opening the Script Editor, using Debug, Processes, and selecting the appropriate instance of iexplore. However, this is quite time consuming since I have to do this every time there is an error. Also, it doesn't let me debug the first error on the page, since it only loads the page into the debugger when a second error occurs after the attach.

Here are some of the things I have tried to fix this problem:

1. Logged in as another user who has made very few customizations - to see if it was related to a user setting.
2. Used MSConfig to turn off all startup programs, to see if one of them was a source of conflict.
3. Uninstalled and re-installed the script editor and debugger. I did this from the Office XP setup, and from the FrontPage 2002 setup.
4. Repaired the FrontPage 2002 setup, in the hopes this would restore a missing registry setting. (I did not repair the Office setup - I figured that since the script editor is a common component that it wouldn't work any better.)
5. Ensured that both Disable Script Debugging options in the Advanced Internet Options are unchecked (also tried having just one or the other checked, and both checked).
6. Ensured that both Friendly URLs and HTTP Error Messages are unchecked.
7. Verified the permissions in DCOM Config for Just-In-Time Debugging Handler and CLR Remote Host, Machine Debug Manager, and Microsoft Script Editor. (The first 2 were OK, per the KB article on the MS site. I added Administrators and Debugger Users to Script Editor, just in case that was the problem). Also verified that the other DCOM parameters looked OK, although I have no reference as to what they should be.
8. Verified that the Machine Debug Manager service was running.
9. Ensured that Enable JIT debugging was turned on for Scripts using Tools, Options, Debugging, General, JIT Settings in Microsoft Script Editor.
10. I ran MDM. vs7jit, and MSE7 with the /regserver paramater.

I tried to check the registry settings for MDM (Machine Debug Manager) against what scant information I could find on the Internet. I suspect that this is where the problem lies. I think that Internet Explorer isn't showing me a list of possible debuggers to attach because the list doesn't exist where it belongs, and I assume that MDM is responsible for maintaining that list - although I can't figure out how. This is what I have in the values under the key
[HKLM\Software\Microsoft\.NETFramework]
DbgJITDebugLaunchSetting = 0 (I also tried 2)
DbgManagedDebugger = "C:\Program Files\Common Files\Microsoft Shared\VS7Debug\vs7jit.exe" PID %d APPDOM %d EXTEXT "%s" EVTHDL %d
(I also tried "C:\Program Files\Microsoft Office\Office10\MSE7.exe")
InstallRoot = C:\WINDOWS\Microsoft.NET\Framework\

Only the first value was there - I added the other values manually. I also added a key
[HKLM\Software\Microsoft\.NETFramework\DbgManagedDebugger] with a default value of "cordbg.exe !a 0x%x" (without the quotes), but when that didn't fix the problem I removed that key since I was doubtful it should be there, and it didn't use MSE7.exe anyway.

One thing I found suspicious. The documentation for the Script Editor says that initially there should be an option on the Debug menu to install the debugger - but I didn't have this option. I suspect that this is why the debugger wasn't installed properly. If I could fool Script Editor into thinking that it hasn't installed the debugger yet, that may enable me to easily fix the registry. Unistalling and re-installing the Script Editor did not reset this menu option.


dopyiii wrote ...

Maybe something here can help (if you haven't seen this already): http://support.microsoft.com/kb/281427


I responded ...

I had seen this article before and followed most of it. I hadn't followed the portions that seemed to be related to server side and asp debugging, especially since I was able to debug scripts from third party sites before I re-installed Windows on my computer - and I have no control over their permissions. But figured "what do I have to lose" by going all the way. So, in addition to the steps already taken, I

Per the article:
Enabled ASP server-side script debugging
Enabled ASP client-side script debugging
Plus:
Enables Script source access
(left the existing access permissions alone on the child nodes, though)

Per the article:
I verified that the permissions for Microsoft Script Editor (instead of Microsoft Script Debugger, since this article was written for the script debugger, not the script editor). Even though Administrators and Debugger Users already had access, I added Interactive to the lists for Access and Configuration permissions, since it was not on those lists before because I thought they weren't required.

I then looked at the .reg files in the article to switch between the Visual InterDev and Microsoft Script Debuggers, which has these two .reg files

For Visual InterDev: InterDev.reg

[HKEY_CLASSES_ROOT\CLSID\{834128A2-51F4-11D0-8F20-00805F2CD064}]
@="MDM Debug Session Provider Class"
"AppID"="{9209B1A6-964A-11D0-9372-00A0C9034910}"

[HKEY_CLASSES_ROOT\CLSID\{834128A2-51F4-11D0-8F20-00805F2CD064}\LocalServer32]
@="c:\\WINNT\\System32\\mdm.exe"

[HKEY_CLASSES_ROOT\CLSID\{834128A2-51F4-11D0-8F20-00805F2CD064}\ProgID]
@="MDM.SESSPROV.1"

[HKEY_CLASSES_ROOT\CLSID\{834128A2-51F4-11D0-8F20-00805F2CD064}\Programmable]

[HKEY_CLASSES_ROOT\CLSID\{834128A2-51F4-11D0-8F20-00805F2CD064}\VersionIndependentProgID]
@="MDM.SESSPROV"



For the Microsoft Script Debugger: MSCcrDbg.reg
[HKEY_CLASSES_ROOT\CLSID\{834128A2-51F4-11D0-8F20-00805F2CD064}]
@="ScriptDebugSvc Class"
"AppID"="{A87F84D0-7A74-11D0-B216-080000185165}"

[HKEY_CLASSES_ROOT\CLSID\{834128A2-51F4-11D0-8F20-00805F2CD064}\LocalServer32]
@="c:\\Program Files\\Microsoft Script Debugger\\msscrdbg.exe"

[HKEY_CLASSES_ROOT\CLSID\{834128A2-51F4-11D0-8F20-00805F2CD064}\ProgID]
@="ScriptDebugSvc.ScriptDebugSvc.1"

[HKEY_CLASSES_ROOT\CLSID\{834128A2-51F4-11D0-8F20-00805F2CD064}\VersionIndependentProgID]
@="ScriptDebugSvc.ScriptDebugSvc"



This is what I have
[HKEY_CLASSES_ROOT\CLSID\{834128a2-51f4-11d0-8f20-00805f2cd064}]
@="MDM Session Provider"
"AppID"="{9209B1A6-964A-11D0-9372-00A0C9034910}"

[HKEY_CLASSES_ROOT\CLSID\{834128a2-51f4-11d0-8f20-00805f2cd064}\LocalServer32]
@="C:\\Program Files\\Common Files\\Microsoft Shared\\VS7Debug\\mdm.exe"

[HKEY_CLASSES_ROOT\CLSID\{834128a2-51f4-11d0-8f20-00805f2cd064}\ProgID]
@="MachineDebugManagerSessionProvider.7"



It looks like the first key points to Machine Debug Session Provider. In my case it is
{9209B1A6-964A-11D0-9372-00A0C9034910}
which is the Machine Debug Manager mdm.exe.

Based on the pattern in the supplied registry files, I added the key
[HKEY_CLASSES_ROOT\CLSID\{834128A2-51F4-11D0-8F20-00805F2CD064}\VersionIndependentProgID]
@="MachineDebugManagerSessionProvider"


For the Application Protection, I changed the Application Protection from Medium to Low. I also gave full rights for IWAM_mymachine to the Machine Debug Manager for Launch, Access and Configuration. I also gave it full rights to C:\Program Files\Common Files\Microsoft Shared\VS7Debug\pdm.dll

Unfortunately, none of this has helped.

Could someone who is using Script Editor as their debugging tool please verify the registry entries for [HKEY_CLASSES_ROOT\CLSID\{834128a2-51f4-11d0-8f20-00805f2cd064}]?