Maintenance Connection Everywhere (MCe) · EAM/CMMS manuals
VFS - Virtual File System
Technically the requirement is ALSO there for our SaaSs, but we turn it on for you. This means MCe supports VFS Long paths on our SaaS
For support of long path in VFS there are 2 requirements on a Windows Server that you have IIS.
The first is that you must have at least Windows 2016, earlier versions of Windows didn't support it
Next you have ta have Long Path support turned on. It is supposed to be turned on by default in 2016 and later, but you may have turned it off or may have a server build process that sets it to off.
The following you would enter into Window's PowerShell
New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" -Name "LongPathsEnabled" -Value 1 -PropertyType DWORD -Force See also: https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry
If you are reading about VFS long path support on the web or using AI, note that yes, we have compiled in the correct support into MCe.
As above, applications have to have compiled in the support needed to work. The last we tested (with MC 2025) they do not have this and nothing in the MC 2026 preliminary notes indicating they are adding it, so the above instructions are for MCe, and while they will work for MC when they compile the feature in, as of MC 2025 and likely 2026 when it comes out, it is not supported. This may be due to the ASP 32bit architecture throughout most of MC and may require waiting until they do their full .NET rebuild which we understand, while a massive undertaking, is being worked on by Accruent.