(left the existing access permissions alone on the child nodes, though) So, in addition to the steps already taken, I
But figured "what do I have to lose" by going all the way.
#Microsoft script debugger windows
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. I had seen this article before and followed most of it.
Maybe something here can help (if you haven't seen this already): Unistalling and re-installing the Script Editor did not reset this menu option. 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. I suspect that this is why the debugger wasn't installed properly.
#Microsoft script debugger install
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. 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. Only the first value was there - I added the other values manually. InstallRoot = C:\WINDOWS\Microsoft.NET\F ramework\ (I also tried "C:\Program Files\Microsoft Office\Office10\MSE7.exe") This is what I have in the values under the keyĭbgJITDebugLaunchSetting = 0 (I also tried 2)ĭbgManagedDebugger = "C:\Program Files\Common Files\Microsoft Shared\VS7Debug\vs7jit.exe " PID %d APPDOM %d EXTEXT "%s" EVTHDL %d 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. I suspect that this is where the problem lies. I tried to check the registry settings for MDM (Machine Debug Manager) against what scant information I could find on the Internet. vs7jit, and MSE7 with the /regserver paramater. Ensured that Enable JIT debugging was turned on for Scripts using Tools, Options, Debugging, General, JIT Settings in Microsoft Script Editor.ġ0. Verified that the Machine Debug Manager service was running.ĩ. Also verified that the other DCOM parameters looked OK, although I have no reference as to what they should be.Ĩ. I added Administrators and Debugger Users to Script Editor, just in case that was the problem). (The first 2 were OK, per the KB article on the MS site. Verified the permissions in DCOM Config for Just-In-Time Debugging Handler and CLR Remote Host, Machine Debug Manager, and Microsoft Script Editor. Ensured that both Friendly URLs and HTTP Error Messages are unchecked.ħ. 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).Ħ. (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.)ĥ. Repaired the Front2 setup, in the hopes this would restore a missing registry setting. I did this from the Office XP setup, and from the Front2 setup.Ĥ. Uninstalled and re-installed the script editor and debugger. Used MSConfig to turn off all startup programs, to see if one of them was a source of conflict.ģ. Logged in as another user who has made very few customizations - to see if it was related to a user setting.Ģ. Here are some of the things I have tried to fix this problem:ġ. 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. However, this is quite time consuming since I have to do this every time there is an error. I can get the debugger to attach to iexplore by opening the Script Editor, using Debug, Processes, and selecting the appropriate instance of iexplore. I press Yes, but the debugger doesn't open, nor do I get a dialog to choose a debugger. If I open a web page that has a Javascript bug, I get the message "A Runtime Error has occurred. In Internet Explorer, if I use View, Script Debugger, Open - nothing happens.Ģ. My environment is Windows XP Professional, Office XP (2002) Professional, Front2. 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. 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.
0 kommentar(er)
