"DisableNtfs8dot3" Does Not Correct the Error "The weblayout directory is on a filesystem with 8dot3 semantics"
Last updated on FEBRUARY 02, 2018
Applies to:Oracle WebCenter Content - Version 22.214.171.124.0 and later
In every page of UCM 11g, the following message is displayed at the top:
You are accessing the shared/remote filesystem using CIFS/Samba from a Unix/Linux server where Content Server is running, rather than using NFS or being directly attached to a SAN.
After running the UCM command "Installer DisableNtfs8dot3" and restarting Windows, the error persists.
After manually setting Windows registry to disable 8.3 naming support and restarting Windows, the error persists.
(HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\NtfsDisable8dot3NameCreation = 0x00000001)
When verifying if 8.3 naming support is actually disabled (see test below), the results show that the Windows registry change disables 8.3 naming support for the local disk C:\, but has no effect on the remote NAS/CIFS filesystem where the UCM weblayout directory exists.
The test (using no UCM code):
...against the local C drive:
C:\> type 123456~1.TMP
C:\> The system cannot find the file specified.
Test result: 8.3 naming support is disabled for Windows and the C:\ drive.
...against the NAS/CIFS fileshare:
Z:\> echo "This is a test file" > 123456789.tmp
Z:\> type 123456~1.TMP
Z:\> This is a test file
Test result: 8.3 naming is enabled on the NAS/CIFS remote file system.
You are accessing a remote/shared filesystem from where the Content Server is running.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms