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

At 12 AUG 1999 01:04:32PM Tamara wrote:

Has anyone out there ever experienced a record locking and only partially releasing? We have been using AREV 2.12 with several versions of the NLM and two versions of Novell Netware (4.10 and 5.0) We continue to have a growing list of records, all from the same file, that have frozen DOS, Windows98 and Windows95 workstations while saving (to the point that the user has to reboot to get their machines back). Once a record does this, others can read this record, without the AREV message indicating the record is locked, but cannot save it, and, while trying to save, hang their PC. I wrote a program with and without MFS programs to read and write to the locked record. I could always read and get a good lock on the record, but once again, hang when I go to write to it.

Anyone ever experience something like this?


At 13 AUG 1999 11:10AM Steve Smith wrote:

It's a long shot, but try FLAG.EXE -T *.* (or equivalent) on all Revelation files to turn off transaction tracking attributes. I have seen lock table saturation under these conditions under Novell 4.x. I know the NLM is different in its lock mechanism, but it's worth a shot anyway. Ensure all files have valid owners. Check you have the NLM version 5.0 for Netware 5 and the correct version (*not* 5.0) for Netware 4.x.

Steve

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/45838741aa11571c852567cb005dcc91.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1