File lock that could only be cleared with rebooting (AREV Specific)
At 06 OCT 1999 08:39:39AM Erica Bartlett wrote:
I have a client who recently had a problem with a REVLOCKS file creating a lock that could not be cleared except by rebooting. When they tried to clear it using tools, they got a message that the file was already in use.
Environment:
Windows 95 clients who moved from a Novel network (which they still sometimes use) to an NT network. They do not have the NT service (which we know is not the recommended way of running). They are using an AREV 3.12 application.
Has anyone seen this sort of problem, or know why it might have happened? Any insight would be appreciated. Thanks.
At 06 OCT 1999 09:28AM ArjunRevelation wrote:
Rebooting the server should help. Also make sure you have all permissions set for the AREV directory. Grant the SYSTEM user on your NT server full rights to the specific folder/directory.
I would also suggest that you get the NT Service installed as soon as possible-if running more than five client/workstations or just the Network Performance Pack-if running less than five client/workstations.
At 06 OCT 1999 09:28AM Todd Meuth wrote:
Erica,
We had a problem with phantom locks on our Arev systems. One station would lock a file, and all other user's PCs would hang until the offending PC logged out of Arev. We tried everything and could not pinpoint the problem. We did find one situation that would always cause problems. One system had a large Rlist report that would always cause problems. But this was not the only cause of our lock problems.
When we purchased and applied the Novel NLM, the problem was completely cured!
Todd
At 06 OCT 1999 07:51PM Kgilfilen wrote:
Todd, IIRC, it sounds like your problem was related to workstations not closing ARev down correctly. In that case, Novell will clear the lock after they log out. The NLM might be expected to resolve that issue indirectly, by preventing ARev from halting (and not clearing its locks) due to network issues. However that may not resolve issues of resource allocation on NT, though you may have experience that suggests differently. It sounds to me that Arjun's advice is sound in that situation.
Kenny
At 08 OCT 1999 05:08AM Larry Wilson - TARDIS Systems, Inc. wrote:
I might suggest that the locking problem might be caused by a single machine using the wrong frome type (but getting away with it).
As Revelation said some time back (Aaron or Steve Smith), be sure to set that manually. Also, don't forget to remove write-behind cacheing.
You can find a pretty good compilation of Novell and NT FAQs on my website at:
Click on the AREV forum button on the left nav bar.
Larry Wilson
TARDIS Systems, Inc.
larry@tardis.cc
512-470-6973