AAAAAAHHHHHH This problem is killing me!!!

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I know that there is a simple solution to this but I CAN'T FIND IT!
Setup:
Win2K Terminal server used by about 10 users from another company.
In Active Directory they are all in one OU and within that OU is one Security Group.
When they logon to the server a program is automatically started.
The program .exe is located on a database server and they connect via UNC.
This is set under the environment tab for the user. Simple so far.
Problem:
The program they are using is a POS FoxPro program. It's not the most stable or reliable program and the users
also have NO patience with it. Sometimes, about once or twice a day, a user will get booted from the program for some reason. On the Terminal server the connection is gone but on the database server there still shows a session from the user that got booted off WITH OPEN FILES. When the user gets booted or loses connection they jump right back on and open up another session which accesses already open files from the previous session. Whithin a couple of minutes everyone that is logged onto the TS starts having all kinds of problems until I clear the hung session on the database server.
Question:
How do I end the session on the database server whenever the connection is lost on the Terminal server?
 
Hi,

first of all: Everyone knows that you're having a bad time, however, we do
not know your name, your headline is useless, shouting and full with
repeated characters... Therefore, many users will ignore your question,
which is the last line of your post:
How do I end the session on the database server whenever the connection is
Click to expand...
lost on the Terminal server?

Maybe you should terminate all disconnected sessions immediately eg. with
(sorry, translated from german) control panel/Administrative
stuff/TerminalServices Configuration/Connections/rightclick on
RDP-tcp/properties/Sessions tab/aktivate the second field "override user
setting" and activate the second option "end session"

regards

arno
 
Afish6969 opined thusly on Apr 22:
I know that there is a simple solution to this but I CAN'T FIND IT!
Setup:
Win2K Terminal server used by about 10 users from another company.
In Active Directory they are all in one OU and within that OU is one Security Group.
When they logon to the server a program is automatically started.
The program .exe is located on a database server and they connect via UNC.
This is set under the environment tab for the user. Simple so far.
Problem:
The program they are using is a POS FoxPro program. It's not the most stable or reliable program and the users
also have NO patience with it. Sometimes, about once or twice a day, a user will get booted from the program for some reason. On the Terminal server the connection is gone but on the database server there still shows a session from the user that got booted off WITH OPEN FILES. When the user gets booted or loses connection they jump right back on and open up another session which accesses already open files from the previous session. Whithin a couple of minutes everyone that is logged onto the TS starts having all kinds of problems until I clear the hung session on the database server.
Question:
How do I end the session on the database server whenever the connection is lost on the Terminal server?
Click to expand...

You can't. At least, not from the terminal services side. If their session
is genuinely vaporizing, there's obviously nothing you can do from the
session to resolve problems created when the session bounces.

I suspect that the advice given in the parallel response is precisely
wrong. If you find that the setting is already as Arno specifies, then
that's the very cause of your problem. A user is becoming disconnected from
the session (this can happen easily on a network), and your server is
terminating the session rather than letting it remain open on the server.
This is then plaguing your database server.

So if the settings are already as Arno suggests you set them, then be sure
to set them to let the session remain on the server -- don't let it
terminate! This way, your users will reconnect to that session in cases
where it drops out from under them, and continue on their merry way.

If the settings are not as Arno specifies, I'd still suggest not setting
them as he suggests. If the settings have not hitherto been that way, then
dropped users have been picking up where they've left off, without leaving
hung database sessions from automatically terminating disconnected
sessions. By forcing such dropped connections to terminate as Arno
suggests, you'd be creating more instances of the problem you're
experiencing. In this case, something unusual is killing your users'
sessions -- I mean, truly killing them. Not disconnections.

The problem is either simple or difficult on the terminal server side, but
in either case I'd suggest investigating how you can force your data server
to close the connections, because even if you get things set up right or
not failing on the terminal server, any time a future session crashes for
any other reasons, you're back to the same data connection problems.

Good luck.
 
----- arno wrote: ----

Hi

first of all: Everyone knows that you're having a bad time, however, we d
not know your name, your headline is useless, shouting and full wit
repeated characters... Therefore, many users will ignore your question
which is the last line of your post
How do I end the session on the database server whenever the connection i
Click to expand...
lost on the Terminal server

Maybe you should terminate all disconnected sessions immediately eg. wit
(sorry, translated from german) control panel/Administrativ
stuff/TerminalServices Configuration/Connections/rightclick o
RDP-tcp/properties/Sessions tab/aktivate the second field "override use
setting" and activate the second option "end session

regard

arn


Been there, done that, doesn't help. Any more bright ideas?
 
Back
Top