Vault Maximum Path Length Get Errors

jamie.moseley — Fri, 14 Jun 2024 14:57:03 GMT

All versions of windows since Windows 10, version 1607 have allowed the maximum path length to be uncapped.

https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry

We've removed the path length on both our client and server machines, but when performing a Get on files with long paths, we still get "Object reference not set to an instance of an object." and "Could not find a part of the path C:\xyz\abc\_V\ijk.foo.v" errors.

I recognize this can be solved by shortening our file/directory names, but the folder structure is set in stone and the errors are causing a lot of complaints. Is there something which can be done to fix this?

Thank you!

topic Vault Maximum Path Length Get Errors in Vault Forum

Vault Maximum Path Length Get Errors