What causes an application to crash when another user logs off?
An application on the mapped share is launched by multiple users. One user logs off. This causes the other users of the application to experience an application crash or unresponsiveness. Depending on the OS version, this issue occurs when either the first or last user of the application logs off, as follows:
How to diagnose and prevent Windows server crashes?
Disckmon – this tool monitors, logs and displays all hard disk activity on a Windows system. By using this tool, you can better pinpoint errors which might be caused by pending hard disk failures. Procdump – this tool allows you to monitor applications for CPU spikes and generating crash dumps during a spike.
What happens when the last user logs off?
When the first user logs off, the FCB is orphaned. This causes the application to crash or become unresponsive on subsequent uses. In Windows Server 2008 R2, the FCB is owned by the last user who opened the file, and previous users experience the issue when the last user logs off. Technically the FCB is not owned by any specific user.
Why do I get an unexpected reboot error in my log?
An unexpected reboot error appears in the log when the system fails to shut down and restart gracefully. A likely cause of this error is the operating system stopped responding and crashed, or the server lost power. Look for events preceding the reboot to see a possible root cause. Here is an excerpt from an unexpected reboot event:
When does Windows Server 2012 R2 SP1 crash?
In Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008, this issue occurs when the first user who logged on logs off. In Windows Server 2008 R2 SP1, this issue occurs when the last user who logged on logs off.
What to do when a shared application crashes?
To work around this issue, use one of the following methods: Do not run shared applications from a mapped folder. Instead, install the shared application locally on the terminal server. Use WebDAV shares instead of mapped folders if remote binary sharing is required. If the application is a managed app, use the Shadow Copy feature.