Hi, Guys hope you can help me here.
.
I’m having problems invoking the MS Script Debugger with ASP pages.
Requirements of KB articles mentioned in Ch 6 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.
.
A test ASP script is located in c:\inetpub\wwwroot and invoked by http://localhost/asptestscript.asp.
.
The problem is:-
.
On encountering a ‘Stop’ statement or a run-time error the Just-in-Time Debugger issues the message:
“An exception ‘Runtime Error’ has occurred in Script.
Possible debuggers – MS Script Debugger or MS Script Editor
Do you want to debug using the selected debugger ?.”

On selecting ‘Debug with MS Script Debugger’, two things happen:
.
If a break-point is set (i.e VB Script Stop statement):
MS Script Debugger activates and correctly shows the name of the running ASP but does not show the script code containing the break point and does not take control of script execution, which continues to normal completion.
.
If a run-time error is set (i.e divide by zero or undeclared variable)
MS Script Debugger activates and correctly shows the name of the running ASP but does not show the script code containing the error and does not take control of script execution, issues an “ASP Script Error: Division by Zero or Variable is undefined”, the IIS then returns a HTTP 500.100 error message correctly identifying the VBScript error.
.
.
System = XP Pro SP2, IIS5.1, IE7.0
Script = VBScript
.
As the error handler appears to be detecting break-points and run-time errors correctly, why is MS Script Debugger not taking control of code execution?
Are there other permissions to be set?
Can anybody help to solve this or point me in the right direction to find a solution?
.
Many thanks
Calcott

PS – I’ve noticed that in MMC Computer Management, in Local Groups there is a Debugger Users group,
where does this come into play ?

Hello calcott,

Did you manage to find a solution to this?

themuls