In a Terminal Server environment, when the Runtime is physically on another machine and accessed via a mapped drive, the Runtime crashes for all users when either the first or last user to connect exits the application. Whether it’s triggered by the first or last user depends on the OS.
This is a known problem and Microsoft has already fixed it in Windows Server 2016. This Microsoft article describes the issue and workarounds:
The workarounds are:
The last one requires Visual Studio be available. If you have the right version of Visual Studio follow these steps:
(If you are running ACUCOBOL-GT version 10.0 or 10.1 you must use Visual Studio 2012.)