Fatal Error Reading 0 in table !po.rec.file (AREV Specific)
At 23 NOV 1998 04:54:00PM Denise Maeda wrote:
There was a main topic already created with the following subject:
Fatal Error Reading 50595 in Table "Audit" by Jane Henderson
However, the only response received was that this error occurs with clients using the Microsoft 32bit client rather than Novell.
Does anyone have any other recommendations?
Our error reads:
Fatal Error Reading 0 in table !PO.REC.FILE
FS466
Linear Hash Client/Server.
No Server response.
We are running the Microsoft client and not Novell's client, however, it is just one machine receiving this error. The other PC's which are basically identical with regards to hardware and software are running fine eventhough they are also using the Microsoft client and not Novell's.
We are running Arev 3.12 on a Novell 3.12 server on Windows 95 clients using the Revelation NLM v. 1.5. This began happening after I created a Revparam file on the server. The trouble PC is allowed to access the Arev program, but as soon as you select an option from the programs menu you receive the fatal error. Is there a way to correct this without having to change to the Novell client? It's also strange that the other PC's who are running the same client are working fine? What is a FS466 error and what causes it?
Thanks!
At 26 NOV 1998 10:04AM [email protected] - [url=http://www.sprezzatura.com]Sprezzatura, Inc.[/url] wrote:
Assuming a simple network, the basic causes for these errors are the Microsoft client or not setting a specific frame type. Changing the auto to 802.2 or whatever you're running sometimes makes a different. Setting source routing with the MS client sometimes helps as well.
On a more complex network, these errors could come because of SAP broadcasting failure and the ability to see across to another server.
You mentioned these problems started happening when you added a REVPARAM file. Since all this does is ensure that the driver will not let you in if it can't communicate with the NLM, the only thing I can think of that would cause a difference is when you choose this menu option, it starts hitting a different server. An already attached file shouldn't have an effect, at least in theory.
This error is probably happening when the system kicks into indexing mode. Can you narrow this down somewhat to specific programs or menu option and see what they are doing?
