Btrieve Record Manager Error Codes 1 - INVALID OPERATION 2 - I/O ERROR 3 - FILE NOT OPEN 4 - KEY VALUE NOT

FOUND 5 - DUPLICATE KEY VALUE 6 - INVALID KEY NUMBER 7 - DIFFERENT KEY NUMBER 8 - INVALID POSITIONING 9 - END OF FILE 10 - MODIFIABLE KEY VALUE ERROR 11 - INVALID FILENAME 12 - FILE NOT FOUND 13 - EXTENDED FILE ERROR 14 - PRE-IMAGE OPEN ERROR 15 - PRE-IMAGE I/O ERROR 16 - EXPANSION ERROR 17 - CLOSE ERROR 18 - DISK FULL 19 - UNRECOVERABLE ERROR 20 - RECORD MANAGER INACTIVE 21 - KEY BUFFER TOO SHORT 22 - DATA BUFFER LENGTH 23 - POSITION BLOCK LENGTH 24 - PAGE SIZE ERROR 25 - CREATE I/O ERROR 26 - NUMBER OF KEYS 27 - INVALID KEY POSITION 28 - INVALID RECORD LENGTH 29 - INVALID KEY LENGTH 30 - NOT A BTRIEVE FILE 31 - FILE ALREADY EXTENDED 32 - EXTEND I/O ERROR 33 - BTRIEVE UNLOAD NOT POSSIBLE 34 - INVALID EXTENSION NAME 35 - DIRECTORY ERROR 36 - TRANSACTION ERROR 37 - TRANSACTION IS ACTIVE 38 - TRANSACTION CONTROL FILE I/O ERROR 39 - END/ABORT TRANSACTION ERROR 40 - TRANSACTION MAX FILES 41 - OPERATION NOT ALLOWED 42 - INCOMPLETE ACCELERATED ACCESS 43 - INVALID RECORD ADDRESS 44 - NULL KEY PATH

45 - INCONSISTENT KEY FLAGS 46 - ACCESS TO FILE DENIED 47 - MAXIMUM OPEN FILES 48 - INVALID ALTERNATE SEQUENCE DEFINITION 49 - KEY TYPE ERROR 50 - OWNER ALREADY SET 51 - INVALID OWNER 52 - ERROR WRITING CACHE 53 - INVALID INTERFACE 54 - VARIABLE PAGE ERROR 55 - AUTO INCREMENT ERROR 56 - INCOMPLETE INDEX 58 - COMPRESSION BUFFER TOO SHORT 59 - FILE ALREADY EXISTS 60 - REJECT COUNT REACHED 61 - WORK SPACE TOO SMALL 62 - INCORRECT DESCRIPTOR 63 - INVALID EXTENDED INSERT BUFFER 64 - FILTER LIMIT REACHED 65 - INCORRECT FIELD OFFSET 66 - TOO MANY OPEN DATABASES 67 - SQL DICTIONARY OPENING NOT POSSIBLE 68 - CASCADE ERASE NOT POSSIBLE 69 - ATTEMPT TO ERASE INTO A DAMAGED FILE 71 - RI DEFINITION VIOLATION 72 - OPENING RI REFERENCE NOT POSSIBLE 73 - RI NOT SYNCHRONIZED 74 - AUTOMATIC TRANSACTION ABORT 76 - REFERENCED FILE CONFLICT 77 - FILE USED BY ANOTHER STATION 78 - DEADLOCK DETECTED 79 - PROGRAMMING ERROR 80 - CONFLICT 81 - LOCK ERROR 82 - LOST POSITION 83 - READ OUTSIDE TRANSACTION 84 - RECORD IN USE 85 - FILE IN USE 86 - FILE TABLE FULL 87 - HANDLE TABLE FULL 88 - INCOMPATIBLE MODE ERROR 90 - REDIRECTED DEVICE TABLE FULL 91 - SERVER ERROR 92 - TRANSACTION TABLE FULL 93 - INCOMPATIBLE LOCK TYPE 94 - PERMISSION ERROR 95 - SESSION NO LONGER VALID

96 - COMMUNICATIONS ENVIRONMENT ERROR 97 - DATA MESSAGE TOO SMALL 98 - INTERNAL TRANSACTION ERROR 99 - SERVER ACCESS NOT POSSIBLE 100 - INSUFFICIENT CACHE MEMORY 101 - INSUFFICIENT MEMORY 102 - INSUFFICIENT STACK 103 - FRAGMENT ADDRESS TOO BIG 104 - LOCALE INFORMATION NOT FOUND 105 - FILE CANNOT BE CREATED WITH VAT 106 - CAN'T ACCESS NEXT SEGMENT 107 - FILE NOT CAPABLE FOR SEGMENT ACCESS 109 - FLAG ERROR 110 - CANNOT ACCESS THE LOGGING CONFIGURATION FILE 111 - FILENAME NOT FOUND IN THE LOGGING CONFIGURATION FILE 112 - FILE IN USE BY ANOTHER CLIENT 113 - CANNOT FIND THE LOG FOR THE FILE 114 - LOG FILENAME OR PATH IS INVALID 115 - CANNOT ACCESS THE LOGGING DUMP FILE 130 - BLOCKS NOT AVAILABLE 132 - FILE FULL 133 - TOO MANY USERS 140 - SAVEPOINT ID IS INVALID 147 - LOG SEGMENT IS MISSING 148 - ROLL FORWARD ERROR 149 - MUST USE SQL TO MAKE CHANGES 151 - NESTING LEVEL TOO DEEP 161 - USER COUNT LICENSE LIMIT REACHED 162 - CLIENT TABLE IS FULL 1001 - BLOCK PARAMETER INVALID 1002 - INSUFFICIENT MEMORY 1003 - MEMORY SIZE TOO SMALL 1004 - PAGE SIZE ERROR 1005 - PRE-IMAGE DISK NOT VALID 1006 - PRE-IMAGE BUFFER SIZE NOT VALID 1007 - OPEN FILES NUMBER NOT VALID 1008 - CONFIGURATION NOT VALID 1009 - TRANSACTION'S NAMES NOT VALID 1010 - TRANSACTION ACCESS ERROR 1011 - INVALID COMPRESSION 1012 - INVALID NUMBER OF TRANSACTIONS 1013 - TASK TABLE FULL 1014 - APPLICATION ENCOUNTERED A STOP WARNING 1015 - INVALID PARAMETERS 1016 - BTRIEVE ALREADY RUNNING 1017 - WBTRVRES.DLL NOT FOUND 1018 - RECURSIVE CALL

1019 - OPERATION CANCELLED 1020 - ABNORMAL INTERRUPTION 2001 - INSUFFICIENT MEMORY 2002 - PARAMETER INVALID OR OUT OF RANGE 2003 - NO LOCAL ACCESS ALLOWED 2004 - SPX IS NOT INSTALLED 2005 - WRONG VERSION OF SPX INSTALLED 2006 - NO AVAILABLE SPX CONNECTION 2007 - INVALID PARAMETERS

Error Codes Initial description is taken from the Novell Btrieve Manual 1 - INVALID OPERATION The operation parameter specified in the call is invalid. 2 - I/O ERROR An error occurred during a disk read/write. This status code indicates that the file has been damaged and must be recreated, or that the file specified on the open call was not created. This status code also occurs if the application passed an invalid position block. NOTE: This is a general I/O error and does not necessary mean the file must be recreated. This can also indicate the file was created with a newer version of Btrieve. Analysis: Many times it is simply the index to the file which is corrupt and rebuilding the Btrieve file will correct this problem (Note: this process requires the file to be accessed in exclusive mode) 3 - FILE NOT OPEN The operation cannot execute because the file is not open. A successful Open operation must be performed before Btrieve can process any other operations. This status code also occurs if the application passed an invalid position block. NOTE: Remember to leave a blank space at the end of your Btrieve file spec. Analysis: Check that the path to the file is correct and you have the necessary rights to open the file. 4 - KEY VALUE NOT FOUND The specified key value in the index path was not found. NOTE: This can happen quite often during normal reads for specific key values if they are not located and does NOT mean something is wrong. This error should be trapped for all GetEqual and other random access read operations.

5 - DUPLICATE KEY VALUE A record with a key field containing a duplicate key value cannot be added to an index that does not allow duplicate values. NOTE: This is a valid error code, and does NOT mean something is wrong. Analysis May Happen if a modification is terminated abnormally (Power off station or server) some records and only portions of the record are saved. 6 - INVALID KEY NUMBER The value stored in the key number parameter is not valid for the file being accessed. The key number must correspond to one of the keys defined when the file was created or to a supplemental index. 7 - DIFFERENT KEY NUMBER The key number parameter changed before a GetNext, GetNextExtended, GetPrevious, GetPreviousExtended, Update, or Delete operation. The operation specified requires the same key number parameter as the previous operation because Btrieve uses positioning information relative to the previous key number. If you need to change key numbers between consecutive GetNext, GetNextExtended, GetPrevious, or GetPreviousExtended operations, use a GetPosition operation followed by a GetDirect operation to re-establish position for the new index path. 8 - INVALID POSITIONING The current position must be established to update or delete a record. Perform a Get or Step operation to establish the current position. This status code also occurs if the application passed an invalid position block. 9 - END OF FILE The operation tried to read past the file boundaries (end-of-file or start-of-file). When reading a file in ascending order according to an index path, Btrieve returns the last record in that index path. When reading a file in descending order according to an index path, Btrieve returns the first record in the index path. The GetExtended or StepExtended operations return this status code if the number of records satisfying the filtering condition is less than the number of specified records to be returned and the reject count has not been reached. NOTE: This is normal status code and does NOT mean something is wrong. This code should be trapped for all GetNext, GetPrevious and other sequential read operations. This status code is returned AFTER the last (or first in a ReadPrevious) record has been read. (for example, applications should check for EOF first and process the record only if not found.) Analysis: Could indicate a hardware problem if, for example, this status is returned after reading 1000 records and there are 2000 records in the file.

10 - MODIFIABLE KEY VALUE ERROR The operation tried to modify a key field that is defined as non-modifiable. NOTE: If this is a problem, add the record with the proper key and THEN delete the incorrect key record. 11 - INVALID FILENAME The filename specified does not conform to file naming conventions. NOTE: Remember to leave a blank space at the end of your Btrieve file spec. Analysis: Insure the path name to the database file is correct. (on DOS programs only DOS directory structure is supported) 12 - FILE NOT FOUND The filename specified does not exist. Check the key buffer parameter to make sure the pathname is terminated with a blank or a binary zero. Analysis: Insure the path name to the database file is correct. (on DOS programs only DOS directory structure is supported) 13 - EXTENDED FILE ERROR Btrieve could not find the extension file for an extended file that the application tried to open. Extension files must be loaded on the logical disk drive specified when the extension was created. Both the primary file and its extension file must be online to access an extended file. NOTE: Normally associated with an external index file error. 14 - PRE-IMAGE OPEN ERROR The pre-image file could not be created or opened. There are three possible causes for this error Btrieve could not create a new pre-image file because your disk is full of the preimage file is damaged. Btrieve could not open the pre-image file to restore file integrity. If the pre-image file was erased or damaged, Btrieve could not restore the file integrity. In this case, either use the RECOVER command in the BUTIL utility to retrieve the damaged file's data records in a sequential file or replace the file with its most recent backup.

Btrieve could not assign a handle to the pre-image file because Btrieve was not started by a user with access rights to the pre-image file. NOTE: Check to be sure there isn't a non-Btrieve file in the same directory with the Btrieve pre-image extension. (For example, "filename.btr" and a non-Btrieve file named "filename.pre") Analysis: If it is not a file name problem, rebuild the Btrieve file. 15 - PRE-IMAGE I/O ERROR An I/O error occurred during the pre-imaging function. Either the disk is full of the pre-image file is damaged. If the disk is full, erase any unnecessary files or extend the file to gain additional disk space. If the pre-image file is damaged, the integrity of the Btrieve file cannot be ensured. Either use the RECOVER command in the BUTIL utility to retrieve the damaged file's data records in a sequential file or replace the file with its most recent backup. NOTE: Refer to the Note & Analysis in Error Code 14. 16 - EXPANSION ERROR An error occurred while writing the directory structure to disk prior to the creation of the expanded file partition. Either Btrieve could not close the file or a new page was added to the file and Btrieve could not close and reopen the file to update the directory structure. Check for a disk hardware failure. 17 - CLOSE ERROR An error occurred while writing the directory structure to disk prior to closing the file. Either Btrieve could not close the file or a new page was added to the file and Btrieve could not close and reopen the file to update the directory structure. Check for a disk hardware failure. This status code may also occur if the application passed an invalid position block. 18 - DISK FULL This disk is full, and the file could not be expanded to accommodate the insertion. Either erase any unnecessary file or extend the file to gain additional disk space. Analysis: Delete any unneeded files if the hard disk is truly full. This error can also occur if there are insufficient rights to access the Btrieve file or the file's Novell owner is set to a null.

19 - UNRECOVERABLE ERROR An unrecoverable error has occurred. File integrity cannot be ensured. Either use the RECOVER command in the BUTIL utility to retrieve the damaged file's data records in a sequential file or replace the file with its most recent backup. Analysis Rebuild the Btrieve file to correct the file corruption. 20 - RECORD MANAGER INACTIVE The operation was not processed because requester or the NetWare Btrieve Record Manager was not loaded. Load the requester or the Btrieve Record Manager. Analysis: Verify that BTRIEVE.EXE or BREQUEST.EXE is loaded in memory prior to accessing the Btrieve data file. 21 - KEY BUFFER TOO SHORT The key buffer parameter was not long enough to accommodate the key field for the index path requested. Verify that the length of the key buffer equals the length of the key specified in the key number parameter. This status code can be returned only by certain interfaces. 22 - DATA BUFFER LENGTH The data buffer parameter was not long enough to accommodate the length of the data record defined when the file was created. Verify that the length of the data buffer is at least as long as the file's defined record length. For Get or Step operations, if the data buffer is too short to contain the fixed length portion of the record, Btrieve does not return any data to the data buffer. If the record is a variable length record and the data buffer is too short to contain the entire variable length portion of the record, Btrieve returns as much data as it can and a status code 22, indicating that it could not return the entire record. For the Insert operation, Btrieve does not insert the record if the data buffer is shorter than the fixed length portion of the record. For the Update operation, if the data buffer is too short to contain the fixed length portion of the record, Btrieve does not update the record. For the Create, Stat, and CreateSupplementalIndex operations, a status code 22 indicates that the data buffer is not long enough to contain all the file and key specifications, and the alternate collating sequence definition, if specified.

23 - POSITION BLOCK LENGTH The position block parameter is not 128 bytes long. This error can only be detected by certain language interfaces. 24 - PAGE SIZE ERROR Two possible reasons for this status code: The page size is invalid. The page size must be a multiple of 512 bytes but must be no larger than 4096 bytes. When you set the Btrieve page size configuration, the specified value must be greater than or equal to the page size of the file you plan to create or access. The value of the configuration option may need to be increased. Analysis: Be certain the Btrieve parameter or configuration considers the proper page size (Refer to BSETUP on Novell Servers or Pervasive Btrieve.) 25 - CREATE I/O ERROR The file specified cannot be created. Possible causes are a full disk directory or a full disk. If you are creating a file over an existing file, Btrieve returns this status if the existing file is open or flagged transactional. Analysis: Be certain you have proper access rights to create the file. 26 - NUMBER OF KEYS The number of keys specified for the page size is invalid. For standard Btrieve files with a page size of 512 bytes, the number of key segments must be between 1 and 8. For larger page sizes, the number of key segments must be between 1 and 24. You must define at least one key without the null attribute. 27 - INVALID KEY POSITION The key field position exceeds the defined record length for the file. Either the key position is greater than the record length or the key position plus the key length exceeds the record length. For key-only files, the key must begin in the first byte of the record (position 1). 28 - INVALID RECORD LENGTH The record length is invalid. The record length specified (plus overhead for duplicates) must be less than or equal to the page size minus 6, or greater than or equal to 4 bytes.

29 - INVALID KEY LENGTH The key length is invalid. The key length specified must be greater than 0 and cannot exceed 255. The length of a binary key must be even. Btrieve requires that each key page in the file must be large enough to hold at least eight keys. If the page size is too small to accommodate eight occurrences of the specified key length (plus overhead), either increase the file's page size or decrease the key length. 30 - NOT A BTRIEVE FILE The file specified is not a valid Btrieve file. Either the file was not created by Btrieve or it was created by an earlier version of Btrieve. Another possibility is that the first page of the File Control Record is damaged. Analysis You must try to use a recent backup, or try to use advanced recovery utilities like BTFILER, or BUTIL.NLM from Novell Netware 3.12 or 4.X with the recover and load options, this utility runs from server. 31 - FILE ALREADY EXTENDED The file specified has already been extended. A file can be extended only once. 32 - EXTEND I/O ERROR The file cannot be extended. Possible causes are that the directory or the disk is full. 33 - BTRIEVE UNLOAD NOT POSSIBLE 34 - INVALID EXTENSION NAME The filename specified for the extended partition is invalid. 35 - DIRECTORY ERROR An error occurred while changing to the directory that contains the Btrieve file. Either the drive specified in the GetDirectory operation does not exist or the pathname specified in a SetDirectory operation was invalid. 36 - TRANSACTION ERROR A BeginTransaction cannot be performed because no transactions were specified when NetWare Btrieve was configured.

37 - TRANSACTION IS ACTIVE A BeginTransaction was issued while another transaction was active at that station. Transactions cannot be nested. 38 - TRANSACTION CONTROL FILE I/O ERROR An error occurred when Btrieve tried to write to the transaction control file. Possible causes are that the disk is full, the disk is write-protected, or the transaction control file (which was created when NetWare Btrieve was loaded) is deleted. 39 - END/ABORT TRANSACTION ERROR An End or AbortTransaction operation was issued without a corresponding BeginTransaction operation. 40 - TRANSACTION MAX FILES The application tried to update more than the maximum number of files allows within a transaction. The maximum number of different files that may be updated during a logical transaction is set when NetWare Btrieve is configured. 41 - OPERATION NOT ALLOWED The application tried to perform an operation that is not allowed at this time. Some operations are not allowed under certain operating conditions. For example, Btrieve returns this status code if you attempt to perform a Step, Update, or Delete operation on a key-only file, or a Get on a data-only file. Also certain operations are prohibited during transactions because they have too great an effect on the pre-image file, or on Btrieve performance. These operations include Close, Set, ClearOwner, Extend, CreateSupplementalIndex, or DropSupplementalIndex. 42 - INCOMPLETE ACCELERATED ACCESS The application tried to open a file that was previously accessed in an accelerated mode, and was never successfully closed. The file's integrity cannot be ensured. Either use the RECOVER command in the BUTIL utility to build a new file or restore the file using the latest backup. 43 - INVALID RECORD ADDRESS The record address specified for a GetDirect operation is invalid. The address is outside of the file's boundaries; it is not a record boundary within a data page or on

a data page. The 4-byte address you specify for a GetDirect operation should be one that was obtained by a GetPosition operation. 44 - NULL KEY PATH The application tried to use the GetDirect operation to establish an index path for a key whose value is null in the corresponding record. Btrieve cannot establish positioning based on a null key value. 45 - INCONSISTENT KEY FLAGS The key flags specification on a Create operation is inconsistent. If a key has multiple segments, the duplicate, modifiable, and null attributes should be the same for each segment in the key. 46 - ACCESS TO FILE DENIED The application opened a file in the read-only mode, and tried to perform an Update, Delete, or Insert on that file. Another possible cause is that the owner name required for updates was not specified correctly when you opened the file. 47 - MAXIMUM OPEN FILES The number of files open in accelerated mode exceeds the number of buffers available in Btrieve's cache. When a file in opened in accelerated mode, Btrieve reserves one of its cache buffers for the file. Btrieve always reserves five empty buffers for index manipulation. Reconfigure Btrieve with a smaller page size to allocate more buffers. 48 - INVALID ALTERNATE SEQUENCE DEFINITION The first byte of an alternate collating sequence definition (the identification byte) did not contain the hexadecimal value AC. 49 - KEY TYPE ERROR The application tried to create a file or a supplemental index with an invalid extended key type or tried to assign an alternate collating sequence to a binary key or key segment. You can assign an alternate collating sequence to string, lstring, or zstring key types only. This status code is also returned if you define a supplemental index requiring an alternate collating sequence, and no alternate collating sequence definition exists either in the file or in the key definition passed in the data buffer. 50 - OWNER ALREADY SET

The application tried to perform a SetOwner operation on a file that already has an owner. Use the ClearOwner operation to remove the previous owner before specifying a new one. 51 - INVALID OWNER There are two possible causes for this status code If the Btrieve application received this status code after a SetOwner operation, the owner names specified in the key buffer and data buffer did not match. If the Btrieve application received this status code after an Open operation, the file you tried to open has an owner name assigned to it. Your application must specify the correct owner name in the data buffer. 52 - ERROR WRITING CACHE When trying to make a cache buffer available, Btrieve tried to write data to logical disk drive from a file that was previously open in accelerated mode. An I/O error occurred during a write. 53 - INVALID INTERFACE An application tried to access a file containing variable length records with a language interface from Btrieve 3.15 or earlier. To access files with variable length records, you must use a Btrieve v4.xx or later interface. 54 - VARIABLE PAGE ERROR During a StepDirect operation, Btrieve could not read all or part of the variable length portion of a record. In this case, Btrieve returns as much data as possible to your application. This error usually indicates file damage to one or more pages in a file. 55 - AUTO INCREMENT ERROR The application tried to specify either the segmented or variable attribute for an auto increment key type. An auto increment key cannot be part of another key and cannot allow duplicates. 56 - INCOMPLETE INDEX A supplemental index is damaged. This can occur if a CreateSupplementalIndex operation or DropSupplementalIndex operation is interrupted and does not run to completion. Perform a DropSupplemental- Index operation to completely remove the index from the file.

58 - COMPRESSION BUFFER TOO SHORT The application tried to read or write a record that is longer than the value specified for the size of the compression buffer. Reconfigure NetWare Btrieve, specifying a higher value for the Maximum Compressed Record Size configuration option. 59 - FILE ALREADY EXISTS This status code is return for the Create operation if you specified -1 in the key number parameter and the name of an existing file in the buffer parameter. 60 - REJECT COUNT REACHED Btrieve rejects the number of records specified by the reject count before an Extended Get/Step operation can find the requested number of records that satisfied the filter condition. Check the first two bytes of the data buffer returned for the number of records that were retrieved. 61 - WORK SPACE TOO SMALL The Extended Get/Step operations use the pre-image buffer as work space. The workspace buffer is not large enough to hold the filtering data buffer structure and the largest record to be received. The size of the workspace is specified by the Pre-image Buffer Size configuration option. Check the first two bytes of the data buffer returned for the number of records that were retrieved. 62 - INCORRECT DESCRIPTOR The descriptor (that is, the data buffer structure), which is passed for an Extended Get/Stop operation, is incorrect. The descriptor is the data buffer structure that is passed for a Get/Step Next/Previous operation. 63 - INVALID EXTENDED INSERT BUFFER An ExtendedInsert provides an invalid buffer. Either the buffer length is less than 5 bytes or the number of records specified is zero. 64 - FILTER LIMIT REACHED During an ExtendedGet Next/Previous operation, a rejected record was reached. Furthermore, this rejected record is such that no other record can satisfy the filtering condition, going in the direction specified by the operation. This is applicable only if the key specified by the key number is also used as the filtering condition. TS - This is a valid error code, and does NOT mean something is wrong. 65 - INCORRECT FIELD OFFSET

The field offset in the extractor of an Extended Get/Step operation is invalid based on the length of the retrieved record. 66 - TOO MANY OPEN DATABASES 67 - SQL DICTIONARY OPEN NOT POSSIBLE 68 - CASCADE ERASE NOT POSSIBLE 69 - DELETE OPERATION SPECIFIED A FILE THAT IS DAMAGED 71 - RI DEFINITIONS VIOLATION 72 - RI REFERENCE OPENING NOT POSSIBLE 73 - RI NOT SYNCHRONIZATED 74 - AUTOMATIC TRANSACTION ABORT This is an informative status code and is applicable only in the server-based environment. Btrieve replaced an EndTransaction operation with an AbortTransaction because an error had been detected for a TTS file inside a transaction. In addition, Btrieve executed the Abort Transaction operation. 76 - REFERENCED FILE CONFLICT 77 - FILE USED BY ANOTHER STATION 78 - DEADLOCK DETECTED Btrieve detected a deadlock condition. The application should clear all resources (such as aborting or ending the transaction or releasing all record locks) before proceeding. This allows the other applications to access the resources for which they are waiting. 79 - PROGRAMMING ERROR

This is an internal programming error. Contact the Novell Development Products Division. NOTE: As of November 1999, Novell's Btrieve and NetWare SQL products have been bought out by Pervasive Technologies Inc. 80 - RECORD-LEVEL CONFLICT The Update or Delete operation was not performed. When using Btrieve with DOS, Windows, or OS/2, this status code is returned when another application changes the record on the data page from which you originally read the record that you wanted to update or delete. In NetWare Btrieve, this status code is returned when the record that you originally read has been changed by another application since you read it. Your application should reread the record prior to reseeding an Update or Delete operation. 81 - LOCK ERROR This can result from any one of two conditions The Btrieve lock table is full. Decrease the number of locks that your application uses or reconfigure NetWare Btrieve and specify a higher value for the Maximum Number of Record Locks configuration option. The application tried to unlock one record that was locked with a multiple record lock, and the record position stored in the data buffer did not correspond to any record that was locked in that file. 82 - LOST POSITION When performing a GetNext or GetPrevious on a key with duplicates, the application tried to retrieve a record that was deleted or whose key value was modified by another application. Reestablish position using a GetEqual or a GetDirect operation. 83 - READ OUTSIDE TRANSACTION The application tried to update or delete a record within a transaction, but the record was not read within the transaction. If you are going to update or delete a record within a transaction, you must first read the record within the transaction to ensure you have obtained exclusive access to the data. 84 - RECORD IN USE The application tried to apply a no-wait lock on a record that was currently locked by another application, or to apply a no-wait lock on a file while another application

held active record lock(s) in that file. If this status code is returned, your application can use either of the following two methods Retry the operation until it is successful. Under light to moderate network use, this may be the simplest and quickest solution. Use the wait option (+100/+300) instead of the no-wait option. 85 - FILE IN USE The application tried to apply a no-wait record or file lock while another application held the file locked. This status code is also returned when the application tried to open a file outside of a transaction and the file is locked by another application. If this status code is returned, your application can use either of the following two methods Retry the operation until it is successful. Under light to moderate network use, this may be the simplest and quickest solution. Use the wait option (+100/+300) instead of the no-wait option. 86 - FILE TABLE FULL Btrieve's file table is full. Reconfigure Btrieve and specify a higher value for the Maximum Number of Open Files configuration option. Analysis: On Novell NetWare 2.X use BSETUP utility and the BTRIEVE.VAP must exist in Novell's system directory. On NetWare 3.X or 4.X use BSETUP.NLM to configure and BSTART.NCF to initialize (you can put it on AUTOEXEC.NCF). Otherwise, you must set the command line option /F using BTRIEVE.EXE program. 87 - HANDLE TABLE FULL Btrieve's handle table is full. Reconfigure Btrieve and specify a higher value for the Maximum Number of File Handles configuration option. Analysis: Use Bsetup on Novell servers or Pervasive Btrieve on Windows NT 88 - INCOMPATIBLE MODE ERROR The application tried to open a file in an incompatible mode. If the first application to access the file opens it in accelerated mode, all other applications must open it in accelerated mode. If the first application opens it in non-accelerated mode, other applications cannot open the file in accelerated mode. 90 - REDIRECTED DEVICE TABLE FULL

The Btrieve requester's redirection table or server routing table is full. This occurs if you attach to additional servers or map to additional drives after you've loaded BREQUEST. Reload BREQUEST specifying a larger number for the Number or File Servers, or the Number of Mapped Drives configuration options (/S and /R, respectively). This error also occurs if you detach from a particular server and attach to a different server. Once a workstation has attached to a server, BREQUEST will not remove its name from the server routing table. 91 - SERVER ERROR BREQUEST could not establish a session with the server. Either the NetWare Btrieve Record Manager has not been started or the server was not active. Verify that NetWare Btrieve is active on the server. Analysis: Be certain that your workstation is communicating to the network server on which Btrieve is running. 92 - TRANSACTION TABLE FULL The maximum number of transaction was exceeded. Reconfigure NetWare Btrieve and specify a higher value for the Number of Concurrent Transactions configuration option. 93 - INCOMPATIBLE LOCK TYPE Your application tried to mix single record locks (+100/+200) and multiple record locks (+300/+400) in the same file at the same time. All locks of one type must be released before a lock of the other type can be executed. 94 - PERMISSION ERROR Your application tried to open or create a file in a directory without the proper privileges. Btrieve does not override the network privileges assign to users. Analysis: Check your user access permissions for the directory in which the Btrieve file is located. 95 - SESSION NO LONGER VALID The previously established session was no longer active due to an error at the workstation, the file server, or on the network. Verify that your workstation is still attached to the file server and then reload the Btrieve requester. This status code is also returned if the maximum number of sessions for NetWare Btrieve has been reached. When using NetWare Btrieve in the 286 environment, use the console command BSTATUS to check whether the maximum number of sessions has been reached. When using NetWare Btrieve in the 386+ environment, use the Status

option of the Available Options menu of the BCONSOLE utility to check whether the maximum number of sessions has been reached. If so, reconfigure NetWare Btrieve to increase the number of available sessions. Analysis: This is likely caused by a break in the communication between the workstation and server. This can also indicate a hardware problem in the network communication. 96 - COMMUNICATIONS ENVIRONMENT ERROR This status code occurs when loading NetWare Btrieve on a NetWare server. The SPX connection table is full. Reload SPX, specifying a higher value for the connection table. Refer to the NetWare system documentation for more information. Analysis: Some implementations of Windows for Workgroups waste all SPX Connections. Increment your SPX Connections variable in Windows Network Setup. 97 - DATA MESSAGE TOO SMALL Your application tried to read or write a record that was longer than NetWare Btrieve or the Btrieve requester could handle. Reconfigure the Btrieve Record Manager and specify a higher value for the Record Length configuration option. Reload the requester and specify a higher value for the /D option. For an Update, Insert, or Create operation, the application receives this error if the data buffer length it specifies for the record exceeds the length specified for the Btrieve Record Manager or BSERVER. For a Get, Step, or Stop operation, the application receives this error if the value specified for the data buffer length is shorter than the length of the data Btrieve would return. , regardless of the data buffer length specified in the program. 98 - INTERNAL TRANSACTION ERROR An error has been detected while executing a previous operation on a NetWare TTS file. Therefore, no operation other than AbortTransaction (21) is allowed at this point. 99 - SERVER ACCESS NOT POSSIBLE 100 - INSUFFICIENT CACHE MEMORY 101 - INSUFFICIENT MEMORY

102 - INSUFFICIENT STACK 103 - FRAGMENT ADDRESS TOO BIG 104 - LOCALE INFORMATION NOT FOUND 105 - FILE CANNOT BE CREATED WITH VAT 106 - CAN'T ACCESS NEXT SEGMENT 107 - FILE NOT CAPABLE FOR SEGMENT ACCESS 109 - FLAG ERROR 130 - BLOCKS NOT AVAILABLE 132 - FILE FULL 133 - TOO MANY USERS 1001 - BLOCK PARAMETER NOT VALID The number specified for the Multiple Locks configuration option must be between 1 & 255, inclusive. 1002 - INSUFFICIENT MEMORY Make sure that the workstation has enough memory to load all the programs it requires. 1003 - MEMORY SIZE TOO SMALL Make sure that the value for the Memory Size configuration option is large enough to accomodate the required cache size. 1004 - PAGE SIZE ERROR The value of the Page Size configuration option must be an even multiple of 512, and it must be between 512 & 4096, inclusive. 1005 - PRE-IMAGE DISK NOT VALID You must specify a valid drive letter for the Pre-Image File Drive configuration option. 1006 - PRE-IMAGE BUFFER SIZE NOT VALID The Pre-Image Buffer Size configuration option must be between 1 & 64, inclusive. 1007 - OPEN FILES NUMBER NOT VALID The Open Files configuration option must be between 1 & 255, inclusive. 1008 - CONFIGURATION NOT VALID

The configuration options specified contain invalid or unidentifiable values. For more information on configuration options, refer to the installation and operation manual for your operating environment. 1009 - TRANSACTION'S NAMES NOT VALID The filename specified for the Transaction Filename configuration option is not valid. Check to make sure that the transaction filename is correct. 1010 - TRANSACTIONS ACCESS ERROR 1011 - INVALID COMPRESSION The Compression Buffer Size configuration option must be between 1 & 64, inclusive. 1012 - INVALID NUMBER OF TRANSACTIONS 1013 - TASK TABLE FULL The Btrieve DLL may return this status code if the task entry table is full. You can remedy this situation by increasing the number of available task entries; use the tasks initialization option (tasks=xxx) under the [BTRIEVE] or [BREQUESTDPMI] headings in NOVDB.INI. The minimum value for this option is 1; the maximum value is 255. 1014 - APPLICATION ENCOUNTERED A STOP WARNING WBTRVSTOP() returns this status code if the application still has open files or an active tranaction. The application must close all files and end all transactions before calling WBTRVSTOP(). 1015 - INVALID PARAMETERS One of the pointer parameters passed into Btrieve is invalid. 1016 - BTRIEVE ALREADY RUNNING The Btrieve DLL may return this status code if an attempt is made to initialize Btrieve when it is already initialized. To reinitialize Btrieve, close all files, end/abort all transactions, and call WBTRVSTOP() before calling the initialization function. 1017 - WBTRVRES.DLL NOT FOUND The WBTRCALL.DLL returns this status code when it cannot find the resource file WBTRVRES.DLL. You can remedy this situation by placing a copy of the WBTRVRES.DLL file in the same directory as the WBTRCALL.DLL file. 1018 - RECURSIVE CALL

1019 - OPERATION CANCELLED 1020 - ABNORMAL INTERRUPTION 2001 - INSUFFICIENT MEMORY BREQUEST cannot allocate enough memory for the parameters specified with the REQPARMS environmental variable. Either reduce the size of the /D: option, or reduce the size of the other memory resident routines loaded prior to BREQUEST. 2002 - PARAMETER INVALID OR OUT OF RANGE One of the parameters specified with the REQPARMS environment variable is either invalid (such as /P: instead of /D:) or the value specified for a parameter is out of range. Check the SET REQPARMS statement to make sure that it is correct. 2003 - NO LOCAL ACCESS ALLOWED The application attempted to access a file stored on a local drive. The version of BTRCALLS.DLL installed at the workstation does not allow access to local files. 2004 - SPX NOT INSTALLED Install the NetWare SPX v1.3 or later communications software for OS/2. 2005 - WRONG VERSION OF SPX INSTALLED Install the NetWare SPX v1.3 or later communications software for OS/2. 2006 - NO AVAILABLE SPX CONNECTION SPX has already established the maximum number of sessions it can handle. To increase the maximum, edit the NET.CFG file. Refer to your NetWare documentation for more information on NET.CFG. 2007 - INVALID PARAMETERS One of the pointer parameters passed to Btrieve is invalid. Check the program to ensure that the pointer parameters are correct.