Windows registry [NtfsDisable8dot3Namecreation] = "1" may prevent Enterprise Vault installer from updating Outlook Web Access (OWA) control files.
Article ID: 100029814
Updated On:
Description
Error Message
The Enterprise Vault Exchange 2003 OWA Extensions require changes to files in the Microsoft Controls Folder.
The files in the Microsoft Controls folder are not the original files and cannot be automatically edited.
The Enterprise Vault changes to the Microsoft OWA have not been made.
See the OWA instructions in 'Installing and Configuring'.
Do you want to continue the installation anyway?
Workarounds
1. Open Command Prompt.
2. Go to Vault Admin User's Documents and Settings folder. Usually it is "
C:\Documents and Settings\"3. Execute this command
- fsutil file setshortname "Local Settings" LOCALS~1 4. Execute this command
- dir /x /ah to confirm "Local Settings" now has a short file name.Option 2
1. Log in as the Vault Admin User.
2. Within the Environment Variables, User Variables, edit the TEMP and TMP variable to point to an alternate path such as
C:\temp.
Cause
Enterprise Vault installer spawned a small tool named Fciv.exe with the full path name in the installation task. Fciv.exe is copied under one of sub folders of C:\Documents and Settings\.
When the Vault Admin user was created with Windows registry [NtfsDisable8dot3NameCreation] being set to "1", the Vault Admin user's "Local Settings" folder (exists under "Documents and Settings" folder) will not have a short file name.
Enterprise Vault installer usually expects it has a short file name like "LOCALS~1" and create command line with that. But if "Local Settings" folder doesn't have a short file name, command line will be created with long file name "Local Settings"
Then the full path command name will be recognized as divided parts separated at the space among "Local Settings". This causes the command line interpretation to be failed and prevent Fciv.exe from running. Fciv.exe is called to calculate existing control file checksum, but no calculations are done so that Enterprise Vault installer misunderstands the checksums for these files are not correct and these control files are not the original files.
Resolution
Confirm if the "Local Setting" folder has the short file name by following the steps below:
1. Open Command Prompt.
2. Go to Vault Admin user's Documents and Settings folder. Usually it is "
C:\Documents and Settings\"3.
dir /x /ah 4. If the Vault Admin user's "Local Settings" has a short file name, that will be shown with a long file name like:
2007/01/05 13:53 LOCALS~1 Local Settings If not, the column will be blank:
2007/01/05 13:53 Local Settings Issue/Introduction
This occures when Windows registry [
NtfsDisable8dot3Namecreation] is set to "1".
