Terminal Services issue

[Database Administrator]

Greetings all.

One of my clients that uses Terminal Services, with 15 or more users logged
in at a time, is having a serious problem. After working normally for days
or weeks, no new users can open the application. They say that the users
aren't being dropped from TS, and that they don't cancel the TS sessions.


The workaround is to get everyone out, and run the Clear Lock Files utility.
But, I need to fix the problem instead.

I'm at a loss to explain how the lock/net files are getting corrupted (or
filled?), so that they have to be purged before they can be used again.
Can the application be causing this issue, or is it solely a Runtime (or
connection) issue? Does anyone have any insight, or even a good guess?

Pdox 9 Runtime sp3.

Thanks,
Jim Moseley

[Database Administrator]

Jim Moseley wrote:
> Greetings all.
>
> One of my clients that uses Terminal Services, with 15 or more users logged
> in at a time, is having a serious problem. After working normally for days
> or weeks, no new users can open the application. They say that the users
> aren't being dropped from TS, and that they don't cancel the TS sessions.
>
>
> The workaround is to get everyone out, and run the Clear Lock Files utility.
> But, I need to fix the problem instead.
>
> I'm at a loss to explain how the lock/net files are getting corrupted (or
> filled?), so that they have to be purged before they can be used again.
> Can the application be causing this issue, or is it solely a Runtime (or
> connection) issue? Does anyone have any insight, or even a good guess?
>
> Pdox 9 Runtime sp3.
>
> Thanks,
> Jim Moseley


Are they closing TS, and not closing the application/Paradox first?


--
---------------
Tony McGuire

[Database Administrator]

Jim Moseley wrote:
> Greetings all.
>
> One of my clients that uses Terminal Services, with 15 or more users logged
> in at a time, is having a serious problem. After working normally for days
> or weeks, no new users can open the application. They say that the users
> aren't being dropped from TS, and that they don't cancel the TS sessions.
>
>
> The workaround is to get everyone out, and run the Clear Lock Files utility.
> But, I need to fix the problem instead.
>
> I'm at a loss to explain how the lock/net files are getting corrupted (or
> filled?), so that they have to be purged before they can be used again.
> Can the application be causing this issue, or is it solely a Runtime (or
> connection) issue? Does anyone have any insight, or even a good guess?
>
> Pdox 9 Runtime sp3.
>
> Thanks,
> Jim Moseley


At some point, ALL users AND Paradox must be exited AT THE SAME TIME in
order for the lck file to be cleared.

Is that ever happening?


--
---------------
Tony McGuire

[Database Administrator]

> At some point, ALL users AND Paradox must be exited AT THE SAME TIME in
> order for the lck file to be cleared.

if users abort w/o exiting properly, the lock files can get corrupt and
they'll never properly clear..

--
Steven Green - Myrtle Beach, South Carolina USA

Diamond Software Group
http://www.diamondsg.com/main.htm
Paradox Support & Sales

Diamond Sports Gems
http://www.diamondsg.com/gemsmain.htm
Sports Memorabilia and Trading Cards

"Tony McGuire" wrote in message
news:48f4c6f0@pnews.thedbcommunity.com...
> Jim Moseley wrote:
>> Greetings all.
>>
>> One of my clients that uses Terminal Services, with 15 or more users
>> logged
>> in at a time, is having a serious problem. After working normally for
>> days
>> or weeks, no new users can open the application. They say that the users
>> aren't being dropped from TS, and that they don't cancel the TS sessions.
>> The workaround is to get everyone out, and run the Clear Lock Files
>> utility.
>> But, I need to fix the problem instead.
>>
>> I'm at a loss to explain how the lock/net files are getting corrupted (or
>> filled?), so that they have to be purged before they can be used again.
>> Can the application be causing this issue, or is it solely a Runtime (or
>> connection) issue? Does anyone have any insight, or even a good guess?
>>
>>
>> Pdox 9 Runtime sp3.
>>
>> Thanks,
>> Jim Moseley
>
>
> At some point, ALL users AND Paradox must be exited AT THE SAME TIME in
> order for the lck file to be cleared.
>
> Is that ever happening?
>
>
> --
> ---------------
> Tony McGuire

[Database Administrator]

Steven Green wrote:
>> At some point, ALL users AND Paradox must be exited AT THE SAME TIME in
>> order for the lck file to be cleared.
>
> if users abort w/o exiting properly, the lock files can get corrupt and
> they'll never properly clear..


Which was my first question.


Tony

[Database Administrator]

Tony & Steven (and all),

The next time it happens, I'll try to login & use the LockWise tool Al Brevelerei
wrote to see how many users the BDE thinks are active. Hopefully this points
to 'dropped users' causing 'corrupt lock files'.

Their manager tells me that he doesn't think the users are getting dropped,
but it might happen so often that they've just gotten used to it & stopped
complaining. I've asked him to recheck this with all users.

Any other guesses, in case this doesn't pan out?

Thanks,
Jim Moseley

[Database Administrator]

May not be dropped users, may be just users who log off their session
without closing Paradox. Or (as I've seen many times and have been told
"never ever happens") users X'ing from their TS session without
bothering to close Paradox or log off. Then, of course, the message "too
many terminal server users" crops up a day or 3 later.

Have a look at the logged users list and see what they have open, then
check whether they are "actually" logged in and working.

Jim Moseley wrote:
>
> Their manager tells me that he doesn't think the users are getting dropped,
> but it might happen so often that they've just gotten used to it & stopped
> complaining. I've asked him to recheck this with all users.
>
> Any other guesses, in case this doesn't pan out?
>
> Thanks,
> Jim Moseley


--
Tom Krieg

---------------
http://www.krieg.com.au
Please use the contact page to contact me via email

[Database Administrator]

I think Tom is on the right track. I have the same problem here, users
running TS just shuts down without exiting the Paradox app.

There are some settings you can look at on the server side, terminal service
manager or what it's called, that will let you decide how and when sessions
should expire etc.

At the moment I have no problem with my TS app - maybe the users have
finally understood that they must close Paradox app before closing their
TS-session...

Anders

[Database Administrator]

I'm with Tom. My users cannot comprehend that they need to close what's
inside the "Remote Desktop Connection" window *before* they close the
RDC window (in my case, closing what's in the window will close the RDC
window too).

You can make it so that when a user reconnects to a terminal server,
they reconnect to the same session. You can also make it (as we have)
so an app launches automatically and the user doesn't have access to
anything other than the app and closing the app closes the session. (if
you wish).

IMO, your users are closing the session and leaving Paradox running on
the server.

The really bad part, from my experience, is that timers seem to stop
running when the user does this (so my timers to close the forms
automatically after n minutes of inactivity only work when the session
is open; once the user closes the session, the timer seems to stop).

FWIW,

Liz


Jim Moseley wrote:
> Tony & Steven (and all),
>
> The next time it happens, I'll try to login & use the LockWise tool Al Brevelerei
> wrote to see how many users the BDE thinks are active. Hopefully this points
> to 'dropped users' causing 'corrupt lock files'.
>
> Their manager tells me that he doesn't think the users are getting dropped,
> but it might happen so often that they've just gotten used to it & stopped
> complaining. I've asked him to recheck this with all users.
>
> Any other guesses, in case this doesn't pan out?
>
> Thanks,
> Jim Moseley