Microsoft KB Archive/312880

= BUG: Visual InterDev 6.0 ASP Debugging Does Not Function Properly on a Windows XP-Based Computer =

Article ID: 312880

Article Last Modified on 8/15/2005

-

APPLIES TO


 * Microsoft Visual InterDev 6.0 Standard Edition
 * Microsoft Windows XP Professional

-



This article was previously published under Q312880



SYMPTOMS
After you install or upgrade to Windows XP, Visual InterDev 6.0 Active Server Pages (ASP) debugging may not function and you may encounter one of the following problems:  When you automatically attach the debugger (click the Run button), you may receive the following error message:

Unable to set server into correct debugging state automatically. You may not be able to debug ASP pages. Do you want to continue launching the debugger?

-Or- When you manually attach the debugger, you may receive the following error message:

Cannot attach to machine.

A Devenv.exe application error may be generated at this point which causes Visual InterDev to stop responding.



CAUSE
This problem occurs because the DCOM Authentication Level setting is set to Default in Machine Debug Manager and in the Catalog Class component. Generally, these need to use the default DCOM Authentication Level setting of Connect; however, in Windows XP, they are not set to Connect by default, which causes Visual InterDev 6.0 debugging to stop functioning.



RESOLUTION
NOTE: If you do not have Visual InterDev Server installed (it is located in Add/Remove Programs in Control Panel) follow the instructions in the &quot;Install/Confirm Debugging Components on the Web Server&quot; section in article Q192011 (the link to this article is located in the &quot;References&quot; section of this article). Install this before you proceed or you will not have the Catalog Class component that is referred to in the following steps.

To resolve this problem, change the DCOM Authentication Level setting for Machine Debug Manager and the Catalog Class component to Connect:
 * 1) In Control Panel, click Switch to Classic View.
 * 2) In Administrative Tools, double-click Component Services.
 * 3) Double-click Console Root, double-click Component Services, double-click Computers, double-click My Computer, annd then double-click DCOM Config.
 * 4) Right-click Catalog Class, and then click Properties.
 * 5) On the General tab, under General Properties of this DCOM application, click Connect in the Authentication Level box.
 * 6) Click OK to save your changes and to close the dialog box.
 * 7) Repeat steps 3 through 5 for Machine Debug Manager.

Restart the computer after you make the changes.

If debugging still does not work after you perform these changes, please make sure that you have configured the debugger properly based on the settings in article Q192011.



STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

