Skip to main content

I have a user who is running Maximizer through terminal services.

For whatever reason (usually lost connections) he has ended up with multiple logins to the database, such that he now gets the "record in use, waiting" message, which is actually himself (if you get what I mean).

I have removed all *.lck files, and attempted to remove the *.loc files. I have also tried to replace the MXZU file, but naturally all these files are "in use" and cannot be deleted.

Therefore, is there a way I can clear all the logins manually? Or another method?
Original Post

Replies sorted oldest to newest

We also use Terminal Services, and have had the same issue. The only way our IT team has been able to find to do this cleanly is to reboot the Terminal Server. I believe an option is to stop & start the Pervasive engine (I assume you're using Pervasive, as we are and it seems to be a Pervasive issue), and there is supposed to be a way to do this via batch file, but we haven't implemented this.

Our problem seemed to relate to users walking away from their workstations without logging off TS. Something would break the connection, they would re-login and voila - duplicate connections. Now we have it set up so idle sessions are disconnected automatically after X period of time, and logged off after Y period. Seems to work for us.

- R.
idavies:

Start > Programs > Pervasive.SQL V8 > Other Utilities > Monitor

Microkernel > Active Users...

Then click the "Delete All Users" button (or "Delete Current User" if you want to be more selective).

Is that what you had in mind?


Rooster:

If you're running client/server then a batch file with...

net stop "Pervasive.SQL (relational)"
net stop "Pervasive.SQL (transactional)"
net start "Pervasive.SQL (relational)"
net start "Pervasive.SQL (transactional)"

...should do it. If you're running the WGE as a service then something similar should work as well (only one "net stop" and one "net start" required).
Last edited by gord
>I assume this can just be added to the logon script

No, I wouldn't recommend that unless the user who is having problems is the _only_ person who uses Maximizer. Otherwise you could have all of your users disconnecting each other every time they logged on, and that might adversely affect productivity....

I'd recommend looking into Rooster's suggestion about having your TS sessions timeout and logoff.

Add Reply

Post
LEGAL INFO
CONTACT US
Copyright 2007-2018 Advoco Solutions Ltd. All Rights Reserved.
×
×
×
×
Link copied to your clipboard.
×