BUG: Processes dialog box causes Visual Studio 6.0 IDE to stop responding when Visual Studio .NET is also installed (327038)


The information in this article applies to:

  • Microsoft Visual Studio .NET (2002), Academic Edition
  • Microsoft Visual Studio .NET (2002), Professional Edition
  • Microsoft Visual Studio .NET (2002), Enterprise Developer Edition
  • Microsoft Visual Studio .NET (2002), Enterprise Architect Edition
  • Microsoft Visual J++ 6.0
  • Microsoft Visual InterDev 6.0
This article was previously published under Q327038

SYMPTOMS

When you are logged on to a computer running Windows XP or Windows 2000, and you try to open the Processes dialog box (on the Debug menu, click Processes), the Visual J++ 6.0 and Visual Interdev 6.0 development environments close unexpectedly (crash) if all of the following conditions are true:
  • You are logged on under a user account that does not have Administrator rights.
  • The user account is not a member of the Debugger Users Group.
  • Any version of Visual Studio .NET is installed on the computer.
You receive the following error message:
Development Environment has encountered a problem and needs to close. We are sorry for the inconvenience
When you click Details, you see that the error occurred in AppName: devenv.exe and ModName: msenv.dll.

CAUSE

The IDEs for Visual Interdev 6.0 and Visual J++ 6.0 use a component named the Machine Debug Manager (MDM) for cross-process debugging. Visual Studio .NET also uses this component. When you install Visual Studio .NET on a computer that has Visual J++ 6.0 or Visual Interdev 6.0 installed, the Visual Studio .NET installation upgrades MDM to a newer version.

To tighten computer security, MDM and Visual Studio .NET now require that the user has Administrator rights on the computer or is a member of the Debugger Users Group. The Debugger Users Group is a new account that is created by the Visual Studio .NET installation program specifically for configuring debugging rights.

When Visual J++ 6.0 or Visual Interdev 6.0 is run under a user account that is not a member of one of these two groups, the error that is described in the "Symptoms" section occurs.

RESOLUTION

To resolve this problem, give the user account the correct rights. You can add the user to the Debug Users Group (recommended), or add the user to the Administrators group.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

Steps to Reproduce the Behavior

Note These steps will cause Visual J++ 6.0 or Visual Interdev 6.0 to close unexpectedly.
  1. On a computer running Windows XP or Windows 2000, that has either Visual J++ 6.0 or Visual Interdev 6.0 installed, and that also has any version of Visual Studio .NET installed, log on to the computer under an account that is not a member of the Administrators group or the new Debugger Users Group account.
  2. Do one of the following (any of these scenarios reproduces the problem):
    • Open Visual J++ 6.0. With or without a project open, on the Debug menu, click Processes. In the Processes dialog box, click Refresh.
    • Open Visual J++ 6.0. With or without a project open, on the Debug menu, click Processes. In the Processes dialog box, click Properties.
    • Open Visual J++ 6.0. With or without a project open, on the Debug menu, click Processes. In the Processes dialog box, in the Machine drop-down list box, type the name of a computer that is not on the network, and then press ENTER. You receive the following error message:
      Unable to connect to the machine. The machine cannot be found on the network.
      Click OK.
    • Open Visual J++ 6.0. Create a new Console Application project. Press F11 to step into the code in the debugger. You receive the following error message:
      Application 'c:\winnt\system32\JView.exe' failed to launch. Access is denied. Check the DCOM configuration settings for the Machine Debug Manager
      Close the error message, and then, on the Debug menu, click Processes.

REFERENCES

For more information about problems related to rights settings and the Debugger Users Group, click the following article numbers to view the articles in the Microsoft Knowledge Base:

306164 PRB: "Access Is Denied. Check the DCOM Configuration Settings for the Machine Debug Manager" Error Message When You Debug ASP.NET Applications

317290 PRB: Unable to Debug Remote ASP.NET Applications

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

306172 INFO: Common Errors When You Debug ASP.NET Applications in Visual Studio .NET

319842 BUG: Permissions Error When You Try to Debug an ASP.NET Web Application

Modification Type:MinorLast Reviewed:8/25/2005
Keywords:kbvs2002sp1sweep kbbug kberrmsg kbpending KB327038 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.