PRB: Error: Valec.exe - Invalid Current Directory
Article ID: 192661
Article Last Modified on 10/20/2003
APPLIES TO
- Microsoft Visual Studio 6.0 Enterprise Edition
This article was previously published under Q192661
SYMPTOMS
When you start various programs after you have installed Visual Studio
Enterprise Edition 6.0, the following error appears:
valec.exe - Invalid Current Directory
The process cannot switch to the startup current directory <Windows NT
default drive and directory>\System32\. Select OK to set current
directory to <Windows NT default drive and directory> or
select CANCEL to exit.
CAUSE
This problem is caused by directory permission restrictions on a Windows NT
File System (NTFS) formatted drive. The Visual Studio Analyzer Local Event
Concentrator, ValEC.exe, does not have read access to the system32
directory.
RESOLUTION
Try one of the following to solve this problem:
- Add permissions for the VUSR_machine name to the local Users group in
the Windows NT 4.0 User Manager and ensure that that group has at least
"Read" permissions to the Windows\System32 directory. Or, you can
enable permissions for "Everyone" to give at least Read permission for
the System32 directory. See your Windows NT documentation for
instructions on setting up directory security on the Windows NT File
System.
- Run DCOMCNFG, select MSVSA Local Event Concentrator Class, and click
Properties. Click the Identity tab, change "This user" to a userid that
has access to <Windows NT default drive and directory>\System32, set the
corresponding password, and restart your computer.
- Remove Visual Studio Analyzer from the system.
STATUS
This behavior is by design.
MORE INFORMATION
If you use the default security settings of the System32 directory under
Windows NT, this problem does not occur. You should only see this problem
if the user or administrator modified the security settings. The Zero
Administration Kit can also reset the permissions for this directory and
cause this problem.
Keywords: kbsetup kbprb KB192661