The specified path, file name, or both are too long

Symptoms 

When workin with FileDirector you see a message similar to the following:

Cause

FileDirector uses a 'local' cache folder when you create, modify or just view a file through the WinClient. By default the cache path will be in the folder:

%userprofile%\Documents\FileDirector\<server name>\<domain_username>\<cabinet ID>.CAB\<document GUID>.FDD\00000xxx.REV\File\<Original document filename>

By default, Windows uses a path length limitation (MAX_PATH) of 260 characters for Win32 applications.

Often, especially when roaming profiles or Microsoft OneDrive are used in Windows the overall path length can exceed 265 characters. For instance this fictional path below is 269 characters:

C:\Users\JeremyBurgess\OneDrive - Workflow Doctor Ltd\Documents\FileDirector\cloud.filedirector.co.uk\workflowdoctor_admin\3DE5CB14.CAB\20221015-0736-3313-1019-65e3d5879ac1.FDD\00000001.REV\File\(Signed) Mutual non-disclosure document with (client) on (1 Jan 2024).pdf

Solution

There are two possible solutions:

1. Enable long file names - https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry#enable-long-paths-in-windows-10-version-1607-and-later
2. Use the FileDirector app configuration file to move the default LocalCachePath.

Use the FileDirector app configuration file to change LocalCachePath

This solution is particularly beneficial when server-based roaming profiles are in use. When opening a file in FileDirector the following will happen, the reverse happens when saving a changed file:

1. File is retrieved from the server.
2. File is written to the local cache.
3. File is loaded for view/edit from the local cache.

When the local cache is, in fact, a network location this means that every operation to open a file will result transmitting the file across the network three times. When using local path, on c: for instance, there would only be one network file transfer.

FileDirector's local cache is only for temporary data so there is no value in storing it on a roaming profile location. There are further 'risks' to using a network location for laptop users - if you search and retrieve a file when connected to the network then subsequently disconnect you are reliant on the system administrator properly setting up offline file access.

We recommend against using a network file path for the FileDirector WinClient local cache.

Locate the file "C:\Program Files (x86)\Spielberg Solutions GmbH\FileDirector WinClient\app.xml" change the value of the LocalCachePath attribute.

We normally use C:\FileDirector.cache and to keep in mind Domain Users will need to have modify/delete permissions.

The same fictional 269 character example path would therefore become a more manageable 214 characters:

C:\FileDirector.Cache\cloud.filedirector.co.uk\workflowdoctor_admin\3DE5CB14.CAB\20221015-0736-3313-1019-65e3d5879ac1.FDD\00000001.REV\File\(Signed) Mutual non-disclosure document with (client) on (1 Jan 2024).pdf