I have a frequent problem where an Arev record remains locked after Arev is closed prematurely due to a system crash. The record remains locked for at least a hour before it is released. This has happened since the Universal Driver was installed. The client is running on Arev on a Novell Sever. Is there any way of unlocking the record besides restarting the Novell Sever?

A method that usually works, if you can identify the workstation that set the lock, is to shut that workstation down completely, including powering it off, wait for at least a minute, and then turn it on and log back on to the network. I think what happens is that the server gets a notice that the workstation is making a fresh connection, hence any existing locks cannot possibly be valid, so they are dumped.

Victor

That's what we normally do. Perhaps I will give it a minute next time and see if it helps. Of course this would be more difficult on Terminal Server where we can have 20 sessions running. Thanks!

You can usually go into the system monitor and identify the "ghost" connection by the user name that was logged in and delete/kill connection/session. You can verify which connection it is by the login time, network traffic and files open all in monitor.

View this thread on the forum...