I received two strange error messages last night,

1) I was running a process last night that did several complex calculations on multiple records and received the following error message.

 'Fatal error reading $IN.USE in table SYSOBJ'

 'FS481'

 'Linear Hash Client/Server.'

 'Server File Open Error'

 'File name "..\MAIN\REV46001.OV'

 'ESC to terminate, Break to debugger'

2) The second error message occured after a process had finished and the 5 computers running the process were waiting to user input on a 'Done' box. When I came in this morning, each of these computers had this message'

  'Fatal Error Reading *INDEXES in table !ACCOUNT_EXECUTIVE

  'FS466'

  'Linear Hash Client / Server.'

  'No Server Response'

  I can reliably recreate this error message by momentarialy removing the network cable from the workstation.  But I am very sure the network did not pause or disconnect, and the workstations were not disconnected either.

System Specs:

 Win95 - NLM1.12

  Advanced Revelation 3.11

  Novell IntraNetWare 4.11, latest service patch.

  100BaseT Ethernet network

  Compaq Servers and workstations

  Some routing (Internal to servers) involved.

  Any help is appreciated!

         Thanks,

1. Rob.

1) I was running a process last night that did several complex calculations on multiple records and received the following error message. 'Fatal error reading $IN.USE in table SYSOBJ' 'FS481' 'Linear Hash Client/Server.' 'Server File Open Error' 'File name "..\MAIN\REV46001.OV' 'ESC to terminate, Break to debugger'

FS481 is a server open error. You should make sure that you do not have any other processes running that might access the files (backup etc…) and that all workstations are accessing the files via the NLM by use of the REVPARAM file and the ServerOnly=1 setting.

John Revelation

We occasionally get your second error message on the indexer machine if someone forgets to log it out for the night. This occurs because while the indexer isn't watching, the backup software snags an open. When the indexer blinks again and looks at the file, it is no longer available. This solution always works:

The error message has an option to go to the debugger. Do that and enter "G" at the "!" prompt. The process will then continue where it left off.

View this thread on the forum...