NLM - FS466 - No Server Response if key too large (Networking Products)
At 14 APR 1998 02:11:27PM Bob Fleischman wrote:
NLM 1.5, happened with 1.12, Novell 4.10
I have a client site where we can repeatedly cause a "No server response" error. It seems that if the key to the record is too large the NLM gets confused. We tried changing the /s and the /p switches.
This first arose when we turned on the NLM and some indexes broke. We have a field that has data that occasionally exceeds 1500 characters; this field has a btree index on it. Without the NLM fine, with the NLM no server response on the long record.
I experimented and tried to just create a record with a very long key and that is where I found the error.
We have tried tweaking the /s and /p parameters as suggested in the docs, however if anyone else has any suggestions please let me know here or at:
Thanks
At 15 APR 1998 10:00AM John Duquette wrote:
Bob,
The parameters you might want to change on the nlm are:
set the TSR to be /r:100 /c:120
LHIPXSER.NLM /M:20
Additionally I would not reccomend using the /S setting on the NLM since this can have adverse effects on both the Server and the NLM.
John Revelation