PRB: Visual InterDev 6.0 ASP Debugging Fails After You Install Office XP Microsoft Script Editor (300243)


The information in this article applies to:

  • Microsoft Visual InterDev 6.0
  • Microsoft Office XP Professional
  • Microsoft Office XP Small Business
  • Microsoft Office XP Standard
  • Microsoft Office XP Students and Teachers
  • Microsoft Office XP Developer
  • Microsoft Access 2002
  • Microsoft Excel 2002
  • Microsoft FrontPage 2002
  • Microsoft Outlook 2002
  • Microsoft PowerPoint 2002
  • Microsoft Word 2002
This article was previously published under Q300243

SYMPTOMS

After you install the Web Debugging components within the Microsoft Script Editor that comes with Office XP, the Visual InterDev 6.0 debugger does not stop on breakpoints.

CAUSE

When you install the Web Debugging components from the Office XP Microsoft Script Editor (Mse7.exe), a new version of the Machine Debug Manager (Mdm.exe version 7.0.9064.9150 or later) is installed, which runs as a service. The new Machine Debug Manager requires that you configure Distributed Component Object Model (DCOM) permissions for both the Machine Debug Manager and Just-In-Time Debugging Handler and CLR Remote Host entries.

NOTE: The Web Debugging components are not installed by default when you install Office XP. You must first install the Microsoft Script Editor, then the Install Web Debugging option appears in the Debug menu in the Microsoft Script Editor.

RESOLUTION

First, ensure that your debugger is properly configured according to the following Microsoft Knowledge Base article:

192011 HOWTO: Configure Your Web Server for Visual InterDev 6.0 ASP Debugging

To facilitate the configuration of DCOM permissions for the new Machine Debug Manager, a new Windows NT Group named Debugger Users is automatically added to the computer when you install the Office XP Microsoft Script Editor. The Debugger Users group is given DCOM permissions on the Machine Debug Manager and Just-In-Time Debugger Handler and CLR Remote Host entries.

To configure the Web Server for debugging, use the User Manager for Domains tool on Microsoft Windows NT or the Computer Management tool in Administrative Tools on Windows 2000 to add the user who will be debugging to the Debugger Users group on the Web Server. If you use this method, you do not have to reboot the Web server.

You can also follow these steps to add the local Administrators group or the individual users who will be debugging to the DCOM permissions on the Web server:
  1. From the Start menu, click Run, type dcomcnfg.exe, and then click OK.
  2. On the Applications tab, scroll down to the Machine Debug Manager, and double-click it to view Properties.
  3. On the Security tab, click Use custom access permissions, and then click Edit.
  4. Click Add to add the users who will be debugging to this list, and grant them Allow Access rights, or simply add the Administrators group to this list.
  5. In the Properties dialog box, click Use custom launch permissions, and then click Edit.
  6. Click Add to add the users who will be debugging to this list, and grant them Allow Launch rights, or simply add the Administrators group to this list.
  7. Click Apply and then click OK.
  8. Double-click Just-In-Time Debugger Handler and CLR Remote Host on the Application tab to display the Properties, and repeat steps 3 through 7 for the Just-In-Time Debugger Handler and CLR Remote Host.
  9. Close the Distributed COM Configuration Properties dialog box, and restart your computer.

REFERENCES

For a list of related debugging articles, see the following Microsoft Knowledge Base article:

244272 INFO: Visual InterDev 6.0 Debugging Resources

Modification Type:MinorLast Reviewed:2/21/2006
Keywords:kbBug kbDebug kbprb KB300243
©2004 Microsoft Corporation. All rights reserved.