Terminal Services issue

#51

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:

Quote:

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

#52

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:

Quote:

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

#53

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:

Quote:

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

#54

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:

Quote:

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

#55

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:

Quote:

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

#56

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:

Quote:

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

#57

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:

Quote:

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

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Terminal Services issue

comp.databases.paradox comp.databases.paradox

Re: Terminal Services issue - 10-15-2008 , 05:42 PM

Re: Terminal Services issue - 10-15-2008 , 05:42 PM

Re: Terminal Services issue - 10-15-2008 , 05:42 PM

Re: Terminal Services issue - 10-15-2008 , 05:42 PM

Re: Terminal Services issue - 10-15-2008 , 05:42 PM

Re: Terminal Services issue - 10-15-2008 , 05:42 PM

Re: Terminal Services issue - 10-15-2008 , 05:42 PM