How to reset 2X client connection on server?

Hi sometimes a published application hangs or quits with a Dr. Watson, however the application/connection is not properly terminated on the 2x ApplicationServer.

This mean that the user (with hang/Dr. Watson) can not start the published application again.
Other users have no problem and can start the same application.
My solution has been to restart the TS/2X ApplicationServer,
this is very inconvenient for the other users on the TS.

My question is there a command(line) or another easy way to reset a particular user/connection so I don't need to restart the server?

TIA, Jem.

 

Hi,
If you need to log off a particular user, or end a particular application of a user, you can do this:
In the 2X terminal server,

To log off:
task manager->user-> select the user-> log off

To end a particular app:
task manager-> process->list the processes by user names-> select the process(app)->end the process

Tom

 

Thanks Tom , but I found even an easier way. On the client go to 2X Application (usually in the tray), let the USER go to the program that won't work. With the right-mouse button on the application, the user can select logoff user or disconnect from application.

 

Jemboy,
That's funny.
Did you try?
What are the effects if you were an end user?

Your method will log off the user's complete session.
Make sure you send him/her a message before you do this.


Tom

 

Yes, that's exactly what I want. However I am not doing this!
The publisched applications sometimes hangs. If a user then tells me he cannot start the published application I had to restart the server (or use your solution). For both solutions I had to connect to the TS to allow for a gracefull termination, sending the users messages "Please quit program bla bla".
Now I can just tell to user to logoff his own session... it's faster, cleaner and it saves me work :wink:

BTW my description to logoff above (earlier message) is for 2X Application 3.7 , for version 6.x the user can logoff with a rightmouse click at the right farm and select log off...

 

I usually publish an extra "kill process" shortcut for apps that crashes occasionally. By specifying "%systemroot%\system32\tskill.exe" as target and "processname" as parameter, your users are able to easily kill the hanging process by themselves. No need to log-off the full session.