Microsoft KB Archive/281427

Knowledge Base

PRB: Microsoft Script Debugger Does Not Break at Error

Article ID: 281427

Article Last Modified on 5/29/2003

---

APPLIES TO

• Microsoft Active Server Pages 4.0

---

This article was previously published under Q281427

SYMPTOMS

When the Microsoft Script Debugger is installed, it may not open automatically when you view a page in Microsoft Internet Explorer if there is an error or stop statement in the code.

CAUSE

There are several causes for this problem:

• Automatic debugging flags are not checked in Internet Information Server (IIS).
• Distributed Component Object Model (DCOM) permissions are not configured correctly.
• The Microsoft Script Debugger is not set as the default debugger.
• If the directory's application protection is set to Medium or High on Internet Information Server (IIS) 5.0, or if the application is set to run in separate memory space on IIS 4.0, the appropriate DCOM and NTFS permissions for the IWAM account are not set for the Machine Debug Manager.

RESOLUTION

The following resolutions correspond to the preceding causes:

Steps to Enable Debugging for the Web Site

1. Open the Internet Server Manager as follows:
   

On Windows NT, on the Start menu, point to Programs, point to Windows NT 4.0 Option Pack, point to Microsoft Internet Information Server, and then click Internet Server Manager.

On Windows 2000, open Control Panel, click Administrative Tools, and then click Internet Services Manager.

1. Locate the application that contains the page that you are trying to debug. Right-click the application (or if the page is in the root of your default Web site, right-click the default Web site), and then click Properties.
2. If the application is under the default Web site (or other virtual server), click the Directory (or Virtual Directory) tab. If the application is the default Web site or other virtual server, click the Home Directory tab.
3. Click Configuration.
4. In the Application Configuration dialog box, click the App Debugging tab.
5. In the Debugging Flags list, select the Enable ASP Server-Side Script Debugging check box.

Steps to Configure the Appropriate DCOM Permissions

1. On the Start menu, click Run, and then type dcomcnfg.
2. In the Distributed COM Configuration Properties dialog box on the Applications tab, click Microsoft Script Debugger, and then click Properties.
3. In the Microsoft Script Debugger Properties dialog box, click the Security tab.
   
   If this tab does not appear, close the Distributed COM Configuration Properties dialog box, and complete these steps:
   
   
   1. Confirm that the Msscrdbg.exe file exists on your computer. By default, it is located in the C:\Program Files\Microsoft Script Debugger folder.
   2. On the Start menu, click Run, and type C:\Program Files\Microsoft Script Debugger\msscrdbg.exe /regserver.
   The Security tab should now appear in the Distributed COM Configuration Properties for the Microsoft Script Debugger.
4. On the Security tab, click Use custom access permissions, and then click Edit.
5. In the Registry Value Permissions dialog box, confirm that the following groups and users are listed:

   <ComputerName>\Administrators
   SYSTEM
   INTERACTIVE

   Note The <ComputerName>\Administrators group assumes that you are logged on as a user in the local Administrators group.
   
   

   If any of these items are missing, you must click Add to add them. If you change anything in this Property window, you must restart your computer before you can debug. Click OK to exit the Registry Value Permissions dialog box.
6. On the Security tab, click Use custom launch permissions, and then click Edit. Repeat step 5.
7. On the Security tab, click Use custom configuration permissions, and then click Edit. Repeat step 5.

Set Microsoft Script Debugger as Default Debugger

To set the Microsoft Script Debugger as your default debugger, complete the steps in the following article:

284973 HOWTO: Switch Between the Visual InterDev Debugger and the Microsoft Script Debugger as Default JIT Debugger

Steps to Check Application Protection Settings

1. Open the Internet Services Manager.
2. Locate the application that contains the page that you are trying to debug. Right-click the application (or if the page is in the root of your default Web site, right-click the default Web site), and then click Properties.
3. If the application is under the default Web site (or other virtual server), click the Directory (or Virtual Directory) tab. If the application is the default Web site or other virtual server, click the Home Directory tab. Take note of the Application Protection setting under Application Settings.

If the Application Protection is set to Medium or High, follow these steps:

1. On the Start menu, click Run, and then type dcomcnfg.
2. In the Distributed COM Configuration Properties dialog box, on the Applications tab, click Machine Debug Manager, and then click Properties.
3. On the Security tab, click Use custom access permissions, and then click Edit.
4. In the Registry Value Permissions dialog box, add the local computer's IWAM account.
5. On the Security tab, click Use custom launch permissions, and then click Edit. Repeat step 4.
6. In Windows Explorer, right-click C:\Winnt\System\PDM.dll, and then click Properties.
7. On the Security tab, give full control to the IWAM account.
8. Restart your computer.

Note After you test the Script Debugger and confirm that it works, you can remove the NTFS permissions for the IWAM account that is set on the PDM.dll file.

Additional query words: debugging script debugger break

Keywords: kbbug kbvisiddebugger kbdebug kbprb KB281427

---

Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.