File not found error when replacing a file in a clustered Projectwise enviroment.

Error reproduction:

In a clustered environment, a ProjectWise user opens properties of a document and imports a new file from his computer to replace already existing file that is currently linked to said document.

In some cases user will receive a file not found error and the document will be left locked in "coming in" state.

Solution:

Three DWORD values need to be created in the registry on all cluster nodes/servers:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Lanmanworkstation\Parameters

CacheLifetime

FileInfoCacheLifetime

FileNotFoundCacheLifetime

All values should be set to 0.

A PowerShell command Get-SmbClientConfiguration can be run to check if settings were applied. 

Further notes:
https://blogs.msdn.microsoft.com/winsdk/2009/07/10/file-exists-_access-getfileattributes-findfirstfilefindnextfile-_stat-behavior-over-smb-2-0/
https://docs.microsoft.com/en-us/powershell/module/smbshare/get-smbclientconfiguration?view=win10-ps