Wrox Programmer Forums
Go Back   Wrox Programmer Forums > Other Programming > VBScript
|
VBScript For questions and discussions related to VBScript.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the VBScript section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
  #1 (permalink)  
Old March 4th, 2008, 06:33 AM
Registered User
 
Join Date: Mar 2008
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default Script Debugging Problems

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 ?




Reply With Quote
  #2 (permalink)  
Old August 16th, 2008, 02:04 AM
Registered User
 
Join Date: Aug 2008
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hello calcott,

Did you manage to find a solution to this?

themuls

Reply With Quote





Similar Threads
Thread Thread Starter Forum Replies Last Post
.js outside script problems Apocolypse2005 Javascript 1 July 25th, 2006 07:33 PM
Problems with debugging ASp.net ocabrera70 ASP.NET 2.0 Basics 1 March 1st, 2006 03:49 PM
Debugging ASP using Windows Script Debugger Sameer Kulkarni Classic ASP Professional 0 February 23rd, 2006 12:28 AM
Client-side script debugging problem on WindowsXP Dmitriy ASP.NET 1.0 and 1.1 Professional 1 October 12th, 2005 09:24 AM
Problem debugging client-script on WindowsXP Dmitriy General .NET 0 October 11th, 2005 03:54 PM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.