I have a customer that is reporting FS481 error messages in their AREV application. The error states:
"Linear Hash Client/Server"
"Server File Open Error"
"File Name "N:\mm.d\Rev40160.OV"
The customer entered "B" and "G" to try to continue. The system reset and returned to the startup menu. The filename is different each time they receive the error. The error occurs once or twice a day, sometimes it skips a day.
To try and resolve this error I increased the settings in the lhipxtsr command line. /r=30. The NLM is version 1.5 and is configured without any specific parameters.
Thanks for any help
Did you have any other process running from different machines that might be locking the dos files? I ran into this one time when our network admin type starting a backup of our fileserver in the middle of the work day without telling any one. All of a sudden all of the workstations in my office bombed out of AREV with messages very similar to yours.
I've also seen hard drives that are on their way out cause similar problems.
Matt
The error messages only appear on one terminal at a time. They do not happen system wide. They usually happen on the indexer but not always. I have asked the customer about the backup and they are not doing a backup at the time.
I also increased the Retry command line in the TSR to 30. As far as I know no other program is touching the AREV files except for AREV and the NLM.
I did notice on one of their Windows 95 workstations that the shortcut was set to Always Suspend. If they had other workstations with this same setting in their shortcut do you think it would cause these errors?
Thanks,
John Bouley
It could, since the TSR can't send the keep-alive message to the server, which is all the TSR does anyway.