Logging into a remote desktop session causes an access violation on an application running on the remote computer
This problem only appears on Windows Server 2012.
We are hosting a desktop application running on our server, which people access and run through remote desktop.
We leave the desktop application permanently running and users connect and disconnect their sessions to use it.
We are finding that when a user connects, the desktop application closes with an access violation - looking in the event log it is clear the error happens when the remote user connects.
Can anyone shed any light on this? Unfortunately googling this problem tends to come up with problems for users trying to connect with remote desktop and getting an error. Just to be very clear - the users are not having a problem connecting to the server with remote desktop, our problem is that a desktop application running on the server is crashing when a remote user connects to the server.
We are hosting a desktop application running on our server, which people access and run through remote desktop.
We leave the desktop application permanently running and users connect and disconnect their sessions to use it.
We are finding that when a user connects, the desktop application closes with an access violation - looking in the event log it is clear the error happens when the remote user connects.
Can anyone shed any light on this? Unfortunately googling this problem tends to come up with problems for users trying to connect with remote desktop and getting an error. Just to be very clear - the users are not having a problem connecting to the server with remote desktop, our problem is that a desktop application running on the server is crashing when a remote user connects to the server.
What does the error message say?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005.
The is a purchased application but it has always worked in this manner for years - it is only with Windows 2012 that it has started exhibiting this behaviour. It runs fine when the users are connected, it is only when they re-connect the error happens.
Exception Info: exception code c0000005.
The is a purchased application but it has always worked in this manner for years - it is only with Windows 2012 that it has started exhibiting this behaviour. It runs fine when the users are connected, it is only when they re-connect the error happens.