Sharing Violation reading NETWORK (AREV Specific)
At 17 JUN 1999 05:02:28PM ETA wrote:
We recently moved our 3.12 A/Rev apps to a dedicated Server running Netware 4.11. CLIB, TurboD and the NLM v1.5 are installed as they were on the old 4.11 box.
We are experiencing sporadic occurances of a "Sharing Violation reading Network" as soon as a user launches A/Rev, "Abort, Retry, Fail" are the choices. I selected Fail and the program continued to load, however and A/Rev error message was displayed warning that the Workstation ID could not be obtained (Machine Address Code / NIC address). I confirmed this with the "WHO" command at TCL.
Since we are at the threshold of using all Netware licenses for the server, we are speculating that there may be a conflict with Netware. Does anyone out there have any other theories??
At 17 JUN 1999 06:34PM Paul Rule wrote:
Are the files flagged as Shareable/Read/Write ?
At 17 JUN 1999 06:42PM ETA wrote:
Yes, they are all flagged.
At 18 JUN 1999 06:57AM Steve Smith wrote:
Had this recently on a REVMEDIA where the LK and OV
portions had different owners. One was flagged
shareable-read-write, the other just read-write.
NDIR /A (or its 4.x equivalent) might shed some light
on what's going on. Check all volumes for your
application. If it happens with AREV SYSPROG then
it's likely to be REVBOOT.
Check all AREV users have equivalent Novell file
access rights also.
Steve
At 18 JUN 1999 11:53AM Warren wrote:
Do all the files have an owner name associated with them? Some backup/restore programs will leave this blank and file sharing/locking will not work properly without them.
If no owner names the quickest way to add them (provided you have the storage space) is to ncopy or move the directories and files to another directory and copy them back if on different volumes, if on the same volume delete the old directory and rename the new.
At 18 JUN 1999 01:59PM Don Miller C3 Inc. wrote:
Have you checked the Frame Type on the desktop? Go to the Network Neighborhood and check the IPX/SPX properties. The default for Windows 95 is to auto-detect the frame type. This can cause all sorts of sporadic wierd problems (FS errors, etc.). Make sure the frame type selected matches the frame type being used on the server. Netware 4.11 defaults to 802.3 (I think..or maybe it's 802.2). Select the proper frame type and check the only connect using that type.
I have also seen strange behavior if a bad version of Share has been loaded (e.g., the Windows 95 or NT driver has been loaded previously and is not the primary protocol). Sometimes the Dial-Up networking feature will cause problems, too.
Don Miller
C3 Inc.
At 18 JUN 1999 02:02PM Don Miller - C3 Inc. wrote:
You can also set the owner with the Flag command and with Filer.
Don Miller
At 19 JUN 1999 04:30AM Warren wrote:
Yes, but you have to do it one file at a time. Not fun if you have dozens or even hundreds of Revelation files spread over many directories and volumes.