Bad Record Lock (AREV Specific) [Revelation On-Line Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
[[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]]


==== Bad Record Lock (AREV Specific) ====
=== At 04 MAY 2000 10:29:43AM C.Miller wrote: ===
 
{{tag>"AREV Specific"}}
 
<QUOTE>
We are trying to delete a record on AREV 1.16 running novell networking. The record cannot be deleted since there is a lock on it. Only one workstation is using the software, and this workstation has been reset many times and locks cleared many times. Where specifically is this bad lock stored and how can it be cleared?
</QUOTE>
----

=== At 04 MAY 2000 12:51PM Don Miller - C3 Inc. wrote:  ===

<QUOTE>Locks are maintained on the Server (as Semaphores) if you're using the Novell Netware driver.  You can see these at the server by going to the File open/lock activity form in the Console Monitor.  If you're using the NPP driver then you will see it on the connection.  If you're using the NLM you can view it in the NLM_STATS utility.  Since there is only 1 workstation logged in, I'm suspicious that you somehow have gotten your own lock set somewhere.  You might try the following:

LOG in as SYSPROG and do a SETFILE to the file you want in the account that owns it.  Try to use the editor to open the record:

EDIT QFILE recordname

if you can read the record without a lock, then you can ALT+D the record.  If it is locked, you should be able to tell whether it's your lock or another station's lock.



Don Miller

C3 Inc.

</QUOTE>

----

=== At 04 MAY 2000 02:59PM Steve Smith wrote:  ===

<QUOTE>Sounds like a spurious lock conflict somewhere. First backup your system. Try changing the network drivers to non-networking and then put them back after you have resolved the issue. Another way would be to change paths (eg. copy your app into a path with a very different path/volume name and try from there).



Steve

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=94C8980B0ADA9CCB852568D5004FA01A|View this thread on the  forum...]]