[[https://www.revelation.com/|Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community]]
==== Arev Record Locked (AREV Specific) ====
=== At 02 FEB 2006 12:01:20PM Jim Leong wrote: ===
{{tag>"AREV Specific"}}
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?
----
=== At 02 FEB 2006 12:38PM Victor Engel wrote: ===
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
----
=== At 02 FEB 2006 02:46PM Jim Leong wrote: ===
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!
----
=== At 03 FEB 2006 08:56AM Warren Auyong wrote: ===
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.
[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=BF24AFD5BBDD688985257109005D81B6|View this thread on the forum...]]