Continuing Timeout Problems (AREV Specific)
At 15 JUN 1999 09:09:17PM Alec Lamberton wrote:
A month ago, I was having a problem with timeouts. The original question was:
+++++++++
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
++++++
Suggestion received was to check changes had been mande to the SYSTEM.INI regarding NLMs.
Did this, but the problem still occurring.
Any other possibilities???
At 16 JUN 1999 01:09AM Jonathan Bird wrote:
Any TSRs running?? I've seen the error you describe, and it seems a TSR was blocking the "keep-alive" packets from LHIPXTSR.EXE from ketting through. Removed it and we never had the errors again.
J
At 16 JUN 1999 10:23AM Victor Engel wrote:
You may want to try adjusting some of the optional parameters to LHIPXTSR and LHIPXSER (they have to be adjusted together). See the NLM manual for details. It refers to your error message specifically.