Fatal Error 466 reading row (num) (AREV Specific)
At 19 MAY 1999 10:46:35PM Alec Lamberton, PSD wrote:
Our client is running a number of reports, some in EasyWriter, some not, that are simple SELECTs, but return a large amount of data. The select seems to be OK, but when the report is printing it will suddenly terminate in the middle of the page with the following line: '* Fatal Error 466 reading row (number) *'.
When their system pops up the messasge 'Fatal Error Linear Hash Client Server - No Server Response', during other types of processing, we hit the debug and then go, and the job keeps processing as if nothing happened, implying a temporary loss of connection to the server. Is this the same thing here, loss of connection terminating the print job? If so, what solutions exist to keep the connection up, or cache the print data so it isn't lost, or halt the print job until the connection is re-established?
Any help appreciated, as this problem has been irritating us for a while.
System
AREV vers 3.12
running MFS (no vers no)
NLMs installed
Server: Novell 4.1
Client: WinNT vers4 SP3
Desktops: Compaq Deskpro running Win 3.1 or 95
At 20 MAY 1999 03:56AM amcauley@sprezzatura.com onmouseover=window.status=why not click here to send me email?;return(true)", [url=http://www.sprezzatura.com" onMouseOver=window.status=Why not click here to visit our web site?';return(true)]Sprezzatura Group[/url] wrote:
Have you ensured that the system ini changes have been made correctly? We've seen this with a timeout value of 1000 instead of 10000.
amcauley@sprezzatura.com
World Leaders in all things RevSoft
At 25 MAY 1999 02:33AM Alec Lamberton wrote:
Tried the method as suggested, as the machines the reports are running on are fairly new and had not been configured according to the NLM documentation, which I added to the SYSTEM.INI. However, there was no discernable difference: the reports still cut out and showed the 'fatal error' message.