Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.
One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.
Logging off users on a RDP server, if application crashes
We have an Access application running on a remote server. This server is locked down and opens our application at login. When they exit the application - it runs the Logoff function and takes them back to their local desktop.
I have put several functions into the Access application that will allow users to logoff - should an issue occur. However, I do see a possibility of something going wrong and the user not being able to log out. The Taskbar/Desktop/TaskManage
I was thinking of writing a small c# process, that is triggered by the Access application once it has loaded. It would pass the process ID the the c# app, which would then monitor the process ID, to see if it's still running. If not (i.e a crash has taken place), it would log the user off.
Is this a good idea, and as I'm pretty new to c#, does anyone have any pointers (or better suggestions)?
I have put several functions into the Access application that will allow users to logoff - should an issue occur. However, I do see a possibility of something going wrong and the user not being able to log out. The Taskbar/Desktop/TaskManage
I was thinking of writing a small c# process, that is triggered by the Access application once it has loaded. It would pass the process ID the the c# app, which would then monitor the process ID, to see if it's still running. If not (i.e a crash has taken place), it would log the user off.
Is this a good idea, and as I'm pretty new to c#, does anyone have any pointers (or better suggestions)?
Asked:
3-
2
1 Solution
Thanks Gustav - good to hear from you - hope all is well.
OK - that's a good point. Do you think it's a sound idea, or would you do it differently?
OK - that's a good point. Do you think it's a sound idea, or would you do it differently?
We've used the runtime environment for decades with zero issues. Should an error occur, a message is popped, and the only choice for the user is to close the application.
If you need to do something afterwards, you could launch the application from a shortcut that opens a batch/command/powershell file which launched Access, then waits for this to finish before moving on calling your termination command(s).
/gustav
If you need to do something afterwards, you could launch the application from a shortcut that opens a batch/command/powershell file which launched Access, then waits for this to finish before moving on calling your termination command(s).
/gustav
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.
Join & Write a Comment Already a member? Login.
Featured Post
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
/gustav