We have a client who is getting the following error on a recurring but seemingly random basis:

Linear Hash Client/Server.

Get Canocical Path Error.

File name "..\PROGS\VDSUTIL\REV57043.LK"

Error Number "0".

The set up is Arev 3.12, NLM 1.5, Novell 4.11 Network and Win95 workstation.

workstation PC is a Microbits Pentium II

Mostly the problem seems to occur when the client runs an enquiry routine. When the error occurs he has to reboot the system but the problem doesn't always go away. He was getting the problem around every 2 to 3 days. (Now that he has reported it, it is happening less often). There are a large number of system users at this client's site but only one client has a problem.

I have read the other stuff on this database on this topic but they don't seem to be directly relevant. I have been told that the REVPARAM stuff and the System.ini stuff is all set up, but will check it.

What does "canocical" mean?

Any ideas on how to make this problem go away would be appreciated.

Thanks

Scott

Canocical is a typo, I believe. It should be "canonical". The problem is that the system is unable to derive the appropriate DOS filename from the Arev filename. This is done by reading the REVMEDIA file. I have found empirically that this problem sometimes occurs with a stale network connection. Ask your user if he stays logged on constantly or if he logs off each day.

Alternatively, you may be encountering collision problems on the network. Review the NLM manual or view the FAQ to see how you can increase the number of retries.

These are just my best guesses. I have asked the same questions and have not received a good anwer. See another of my posts and related threads for more information. You may also wish to do a search on the words "canocical" and "canonical".

There is a DOS function call to get canonical path name. It is from memory, DOS interrupt 21h function 68h, I think. DOS 5 and 6 had an internal undocumented command TRUENAME using this function. It turns

f:\login\somepath\somefile to

\\SERVER\VOLUME\login\somepath\somefile

It is useful to get the absolute path and filespece on a server, or to get the server name for a drive, or to establish a lock reference for a file. For each file this canonical name would resolve uniquely, even across a LAN or WAN.

I am not sure what the NLM does with this call. I vaguely remember your problem / this error being reported before here.

Steve

View this thread on the forum...