We have a client running ARev, Novell, and Win 95 clients (and a few NT clients) that are randomly receiving "sharing violations" and "error writing drive NETWORK" during normal processing.  They have the current NLM and TSR running along with TURBODIS.  We are in the process of verifying that the network and all the workstations are configured correctly.  Most settings should be correct, but I am sure there will be some things that are a little bit off.  However, the system has been fairly stable for as large of a system as it is (73 ARev users, 100+ Novell users).

 I am aware that if SHARE.EXE is loaded in the AUTOEXEC.BAT / CONFIG.SYS and if the REV files do not have the same owner and are not set to "shareable-read-write", that this can cause a violation.

 Is anyone aware of any other reasons why this error comes up?

 This client also has a Vinca backup server/system that continually mirrors the deltas on the main server.  Although the claim is that the lock the Vinca puts on the server files as it copies should not create a problem, I am wondering if ARev would still detect if that file was locked.  It would explain the randomness of the errors since it happens on random machines during random processes.

 Any information or comments on this will be appreciated. Thanks.

[email protected]

SRP Computer Solutions

You might find the following threads helpful:

Sharing Violation

Lori Barron

06/01/98

Sharing violation

Madeleine Orda

05/07/98

AREV Sharing Violations errors while using Virus software

Martha Ferguson

06/03/97 06:59 PM

View this thread on the Works forum...