Hi G
Thanks for the reply, sorry I’m late getting back.
In the absence of any help, I’ve had to work this problem back from first
principles,
however this solution works for me.
..
Enable Server-side script debugging in IIS
For Machine Debug Manager, MS Script Debugger and JIT Debugging Handler,
give Dcom permissions for the Access, Launch and Configuration properties to
Administrator, Interactive and System.
Set MS Script Debugger as default by adding Registry Key as per KB284973.
In IIS – Default Web Site – Home Directory, set Application Protection to
“Low (IIS Process)”
Re-boot and both Debugger and Script Editor should now work, (well it does
on my machines)
..
The so called “experts” on this site seem to be quite useless don’t they?
..
If you have any problems let me know.
..
Best Regards
..
Ian C
--
Ian C
"Gorgsenegger" wrote:
> Hi Ian,
>
> I'm afraid I can't help you as I have the same problem. I installed
> the Microsoft Script Debugger from the MS website and the Microsoft
> Script Editor (better in my opinion) from the Office installation
> files. However, when I open a HTML file with Javascript that launches
> the debugger via "debugger", in the best case I get the error message
> you described. Sometimes I don't even get an error message, it just
> seems that nothing at all happens, which is also the case when I try
> to open the debugger via the menu.
>
> IE settings have been checked and script debugging is NOT disabled
> (neither of the two), and running the MS Script Editor (MSE7.exe)
> directly also works fine. I set the registry value as described in the
> KB article as well, but nothing seems to work...
>
> G.
>
> On Feb 10, 4:27 pm, Ian C <I... DeleteThis @discussions.microsoft.com> wrote:
> > Hi, Guys hope you can help me here.
> > .
> > I'm having problems invoking the MS Script Debugger.
> > Requirements of article KB281427 have been complied with, ie:
> > IIS Server Script debugging enabled
> > DCOM Permissions set
> > MS Debugger set as JIT default by installing registry file MSScrDbg.exe.
> > (KB284973)
> > IWAM permissions set for Machine Debugger
> > .
> > The JITDebug (launch on 'Stop') key in registry has been enabled as per
> > article KB252895.
> > .
> > On encountering a 'Stop' statement or a run-time error the Just-in-Time
> > Debugger (csrss.exe) issues the message:
> > "An exception 'Runtime Error' has occurred in Script.
> > However, no debuggers are registered that can debug this exception. Unable
> > to JIT debug."
> > .
> > The IIS then returns a HTTP 500.100 error message correctly identifying the
> > VBScript error.
> > .
> > Why is MS Debugger not registered with JIT Debugger ?
> > Is a patch or update needed ?
> > How do I fix it ?
> > .
> > System = XP Pro SP2, IIS5.1, IE7.0
> > Script = VBScript
> > .
> > PS - I've noticed that in MMC Computer Management, in Local Groups there is
> > a Debugger Users group,
> > where does this come into play ?
> >
> > --
> > Ian C
>
> >> Stay informed about: Debugger Problems 
FAQ
Search
Profile
Private Messages
Log in/Register/Password
