Visual Studio Analyzer, which is one of the products that is included in Visual Studio Enterprise Edition version 6.0, cannot create the local user account that it needs to run because of changes to the security policies for users in Windows 2000.
Re-install Visual Studio 6.0 Enterprise Edition without Visual Studio Analyzer:
1.
Use the Custom setup, on the Visual Studio 6.0 Enterprise - Custom page, click Enterprise Tools, and then click Change Option.
2.
On the Visual Studio 6.0 Enterprise - Enterprise Tools page, under Options, make sure the Visual Studio Analyzer check box is not selected.
3.
Click to select all the other Visual Studio components that you want to install, and then click OK.
4.
Click Continue, and then follow the instructions that appear.
To install Visual Studio Analyzer:
1.
In Control Panel, double-click Add/Remove Programs, and then click Microsoft Visual Studio 6.0 Enterprise Edition.
2.
Click Change/Remove.
3.
In Visual Studio 6.0 Enterprise Setup, click Add/Remove.
4.
On the Visual Studio 6.0 Enterprise - Maintenance page, click Enterprise Tools, and then click Change Option.
5.
On the Visual Studio 6.0 Enterprise - Enterprise Tools page, under Options, click Visual Studio Analyzer, and then click OK.
6.
On the Visual Studio 6.0 Enterprise - Maintenance page, click Continue, and then follow the instructions that appear.
When you receive the error message that is described in the "Symptoms" section, continue with the Visual Studio Setup Wizard. Setup reports a failure.
To create a local account, which Visual Studio Analyzer will run as:
1.
On the computer that is running Visual Studio Enterprise Edition 6.0, create a local user. For information about how to create a local user, see Windows 2000 Help.
2.
Run Distributed COM Configuration (dcomcnfg.exe).
3.
On the Applications tab, click MSVSA Local Event Concentrator Class, and then click Properties.
4.
On the Identity tab, set This User to match the user and password you created in step 1 of this procedure.
When using Visual Studio Analyzer to create a new project on Windows NT, you receive an unexpected error, such as:
Visual Studio Analyzer is unable to connect to the machine. Ensure that it is powered, connected to the network and that the server-side components have been installed.
•
You cannot run Visual Studio Analyzer at all.
•
You receive many errors from VALEC.exe, usually Access is Denied errors or General Protection Faults.
Visual Studio Analyzer installation procedures create a new user account called VUSR_<machine>, for example, VUSR_DEVELOP001 if your computer is named DEVELOP001.
This user account is used in some of the system services that Visual Studio Analyzer runs to collect performance information from your applications when it analyzes them.
If this user account does not have the correct access permissions, Visual Studio Analyzer fails in various places. The correct permissions are that all of the files it needs to access are readable and executable by the Everyone user group.
Add the VUSR_<machine> user account to the Administrators group, or some other group that can provide execute permissions on files in the Visual Studio Analyzer directories and the %SYSTEM%\System32 directory.
•
Replace the permissions of the directory \Program Files\Microsoft Visual Studio so that the VUSR_<machine> account has permission to run programs and read/write log files. If you use the Windows NT Explorer, this procedure might change other permissions set in this directory (this is normal behavior).
This behavior is by design. This problem only arises if the default directory access permissions for Visual Studio or its associated products are changed on a computer where the components reside on an NTFS partition.
