Product Documentation
Abstract
Content Manager OnDemand requires the Windows 8.3 file name support to be enabled if it is installed on the default location or to a path with embedded spaces such as C:\Program Files\IBM\ondemand\V9.5.
Content
Content Manager OnDemand for Windows must be installed on a drive or volume with 8.3 file names enabled when the install path contains spaces, such as the default path C:\Program Files\IBM\ondemand\V9.5. If it is not possible to enable the 8.3 file name support on the drive or volume, you can install Content Manager OnDemand to a directory with no spaces, such as C:\IBM\ondemand\V9.5.
If Content Manager OnDemand is installed to a path with embedded spaces and the 8.3 file names are not enabled on that drive or volume, running the ARSLOAD program may result in the following error:
C:\Program Files\IBM\OnDemand\V9.5\bin>ARSLOAD -X A -f -V -c C:\TEMP -h host -g ag_name -a appl_name -u userid-p password C:\TEMP\filename.exe
...
yyyy-mm-dd hh:mm:ss.fffff: ARS4302I Indexing started, --UNKNOWN-- bytes to process
: 'C:\Program' is not recognized as an internal or external command,
: operable program or batch file.
To check the current 8.3 file name settings for a drive, start a command window elevated with administrator privileges and enter:
fsutil.exe behavior query disable8dot3
Possible values are:
- 0: Create 8.3 short file names (default)
- 1: Do not create 8.3 file names
- 2: Set 8.3 file names on a per volume basis
- 3: Disable 8.3 file names on all volumes, except the system volume
To enable 8.3 file name support on a global basis, enter:
fsutil.exe behavior set disable8dot3 0
The above command sets the registry value of NtfsDisable8dot3NameCreation under the following registry key to 0.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
When NtfsDisable8dot3NameCreation is set to 0, the 8.3 file name creation is enabled on all volumes. This change takes effect immediately. No restart is required.
When 8.3 file name support is enabled, Windows generates a short 8.3 name equivalent for any file or directory names that does not confirm to the 8.3 format or contains spaces. For example, Windows may create a short 8.3 name of PROGRA~1 for Program Files. When 8.3 file name support is disabled, the 8.3 short names are not created.
If Content Manager OnDemand is installed to a path with spaces on a drive without 8.3 file name support, it must be uninstalled and reinstalled to the same drive after the 8.3 file name support is enabled or to a different drive with the 8,.3 file name support already enabled. The reason for the reinstall is that Windows 8.3 short names are created during the directory creation. Installing to an existing directory may not cause the 8.3 short name to be created. Either install Content Manager OnDemand to a new directory or if the directory is empty, delete the directory and allow the 8.3 name to be recreated during the install.
If you wish to disable 8.3 name creation on all NTFS partitions using regedit, follow these steps:
- Start regedit.exe and locate the following registry key:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
- Select the NtfsDisable8dot3NameCreation entry. By default, the value for this entry is set to 0.
- On the Edit menu, click DWORD. Type a value of 1 in the Data field.
- Click OK and then exit regedit.
- Exit Windows, and then restart your computer.
For more information about fsutil 8dot3name, see the following TechNet article:
http://technet.microsoft.com/en-us/library/ff621566.aspx
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg27048788