We are running Novell with Client Srever and Win95.
ARev3 is setup for Novell Netware.
Trying to add an index to a symbolic field gives a write violation, even though we are logged in under supervisor which should give us all the access rights required.
If ARev3 is changed to Non-Networking, then the indexing can be done.
Any reason for this?
Try flagging all your files shareable read-write, except for AREV.EXE which is shareable-read-only.
FLAG *.* SRW
FLAG AREV.EXE SRO
Also, flag the removal of the T flag (Transaction tracking).
FLAG *.* -T
Check the account SUPERVISOR has no space limits.
Run non-destructive disk scan across your network drives to check for disk integrity. Do not use MAP ROOT= drives. Do not use the root directory of a drive as your REVBOOT directory.
Steve
You said, "Do not use MAP ROOT= drives. Do not use the root directory of a drive as your REVBOOT directory."
Why? I can understand the last item if it's limited to directory entries. Why not map root?
Victor,
I have had all sorts of problems with MAP ROOT drives, including odd locking events, spurious read errors (especially under NT workstation), and have come to generally distrust this feature, especially under Netware 3.x
Steve
Steve,
As usual, good, clear explanation. I, too, came to the same conclusion, but it was so long ago, I had forgotten in (I just never even thought about setting ROOT again), I'll put it in my FAQ.I might mention that under Novell and all things NT, if you set your SORT path to a LOCAL drive (as well as rollout), it really reduces the load on the server.