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.
purplesoupAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rolf HasselbuschIT-ConsultantCommented:
What does the error message say?
0
David Johnson, CD, MVPOwnerCommented:
the application starts in the machine space and is not designed for multi-user access.  The application should be running in the users space and close when the user disconnects. That or NOT start when the user connects.  Is this an in-house application or a purchased application that the experts can work on?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
purplesoupAuthor Commented:
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.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.