Pervasive says: Btrieve for NetWare v6.15 and Status 91 and Status 95 Issues Related to NetWare Patches
Several customers running Btrieve for NetWare v6.15 in a NetWare 3.x or 4.x environment are experiencing system wide status 95s "Session No Longer Valid" and status 91s "Server Error". Usually, applications will be running fine for some period of time, and then everyone will start getting the errors. The period of time can be anywhere from ten minutes to several days. Investigation of this problem is indicating that the problem is being caused by two of the patches Novell has released. They are called SPXTRMFX.NLM and SPXACKFX.NLM. If you are experiencing this problem, it is suggested that you remove these patches and see if the problem persists. Novell is in the process of re-examining these patches. These patches are in all the NetWare 3.x and 4.x patch sets, and have been included in several past revisions as well.
We will provide more information as it becomes available.
Les Martin <firstname.lastname@example.org> also says that:
Even though the article only mentions Btrieve 6.15 we've found that removing the Netware patches also appears to solve the problem using Btrieve 6.1c.
This information helped us out a lot and why it is no longer on Pervasives site it beong me as I'm sure that there are other people ou there suffering the same symptoms (even though now I believe that Novell are no longer releasing these particular .NLMs).
With BTRIEVE.NLM v6.0, a successful Btrieve operation (status = 0) that accesses the NLM must be performed from a workstation before that station can remotely reset the other station. With BTRIEVE.NLM v5.15, the reset is not dependent on the success (status !=0) of the call. If a Btrieve file is opened with Brequest v6.0 and needs to be reset remotely, run Brequest v6.0 on the remote workstation. Before the reset operation, make a successful call to BTRIEVE.NLM to establish a connection.
BC7XBTRV.ASM BC7RBTRV.OBJ BC7PBTRV.OBJ COBPBTRV.OBJ MFXBTRV.OBJ COBRBTRV.OBJ REALBTRV.OBJ MFXBTRV.BIN MF2BTRV.BIN
The interfaces are only available on NDEVREL for those customers that have purchased the Btrieve v6.x SDK Supplement.
When you issue an Extended Insert (40) operation to insert multiple records with a single call to Btrieve, if the data file contains an autoincrement key, the multiple records in the data buffer will be updated with the autoincrement value, as well.
Currently, there is no solution for this inconsistency between the two Btrieve products.
CISCO routers can be configured to delay SAP packets by setting the NOVELL OUT-SAP-DELAY parameter in the port configuration setup. The LENGTH parameter is measured in milliseconds. To prevent the Btrieve NLM from being deleted from the bindery, be sure to set this parameter to a value that will not delay SAP packets too long.
128 (# of pages that a PAT can reference) * 32K (# of PAT pages a Btrieve file can contain) * 512 (the physical size of the Btrieve page) ---------------------------------------------------- 2 Gigabytes total file size
If you need to make a larger file, use a larger page size. Files with any other page size can grow up to four gigabytes in size.
BUTIL-6.10-53: Btrieve error 59 occurred for file or command butiltmp.btr. BUTIL-6.10-72: BUTIL has recovered 0 records. BUTIL-6.10-9: The command did not complete due to an unrecoverable error.
These messages result whenever BUTIL tries to create a file called BUTILTMP.BTR in the same directory as the Btrieve file to be saved or recovered, and this file already exists in the directory.
To avoid these messages, delete or rename the BUTILTMP.BTR file before performing the BUTIL -SAVE or BUTIL -RECOVER. BUTILTMP.BTR is a temporary file created by BUTIL so that it can check if the current Btrieve engine running on the server supports "chunk" operations.
Copyright © Madis Kaal 2000-