I am an independent consultant with a client running AREV 3.12, Win95 clients on a Netware 4.1 LAN. The workstations are Pentium 233's with 32Mb Ram. On only 2 of the 25 workstations, when using the shared index lookup, searching on more than 1 index eg last_name & first_name, we are getting "FS445 - IDX_SETS function 1 returned error code - 9731" the error code differs depending on which combination of indexed fields is used in the search. The batch file starting AREV has switches /x M1024 and the memory property in windows has all parameters set to "Auto". This has only occured recently but no changes have been made to either PC. Any suggestions??

Yes, get more memory. Just use /X and let Win95/NT allocate as much as possible. I usually get 8MB showing in WHO.

Added /X switch to arev startup and now have approx 8Mb memory but still have the problem. ie FS445 IDX_SETS function 1 error when searching on more than 1 indexed field. Only happens on two workstations on the LAN. I need more help.

Until I get my Novell FAQ up, check these things:

TRANSACTION tracking should be OFF on the server.

*ALL* workstations should have write caching turned off

I would set the SORT and ROLLOUT files and paths to a LOCAL directory

Run MAKETABLE (no parameters) and enter the filename and check the parameters (# of rec, size, etc.) and do the same for the ! file.

Make sure that the !file is SHARED; Novell has, with some Client 32s, a nasty habit of unsharing files you've had for years.

Check the OWNER of the !, data and DICT tables; make sure one is assigned.

Make SURE that there is only ONE index on any one dictionary item.

i.e. a dict item should not have a relational AND a Btree, or any other combination.

Check the workstations (actually, this is the FIRST thing to do) to make sure they're locking properly. Edit a record, then go to the other station and try to edit the same record.

I think you said 3.12; if not, set NETWORK CACHE to 00 in REVBOOT (lots of folks will tell you how; it's simple).

In AUTOEXEC, insert the line:

SET AREVLOCKFILE=J:LOCKFILE

J (or whatever) should be a network drive letter.

Lastly, ALL stations should be using the SAME drive letter and path to get to AREV. I.E. F:\AREV\AREV.EXE or R:\AREVXXX\AREV.EXE.

If you have stations using a different drive letter/path, locking will NOT be reliable.

Ok, NOW tell me you still have the problem!

Larry

303-680-8555

First off, you should check the ARev FAQ for all the proper settings. Second, you should never, ever, ever, allocate more than 4 megs of EMS to the system, so always limit to /M4096. Third, you should never allocate more memory than available. Also, ensure valid sort paths and all that other basic stuff.

akaplan@sprezzatura.com

Sprezzatura, Inc.

View this thread on the forum...