Btrieve status codes and messages

This document describes status codes that are returned by Btrieve MicroKernel.
For more information, please visit the Pervasive Software Web site at www.pervasive.com.

1: The operation parameter is invalid.

The specified Btrieve operation does not exist or is not valid for this version of the MicroKernel.

2: The application encountered an I/O error.

An error occurred while reading from or writing to the disk. One of the following has occurred:

• The file is damaged, and you must recover it. Refer to the Pervasive.SQL User's Guide for more information about recovering a file.

• In NetWare, at least one MicroKernel data file is flagged as Shareable. All MicroKernel data files should be flagged as Non-Shareable. The MicroKernel is the only user that accesses the files (on behalf of many users). As the only user, the MicroKernel can control the integrity of the data files. If you flag your MicroKernel data files as Shareable, data corruption can occur.

• For pre-v6.0 data files, there is a large pre-image file inside a transaction, and there is not enough disk space for a write to the pre-image file.

• For pre-v6.0 data files, there is one pre-image file for multiple data files. For example, if you name the data files CUSTOMER.ONE and CUSTOMER.TWO, both files have pre-image files named CUSTOMER.PRE.

• For pre-v6.0 data files that are larger than 768 MB, there is a conflict among locking mechanisms. The file has not been corrupted. Your application can retry the operation until the conflict is resolved (when the competing application releases the lock your application requires).

• A pre-v6.0 Btrieve engine attempted to open a v6.x or later MicroKernel file.

3: The file is not open.

The operation cannot execute because the file is not open. The application must perform a successful Open operation before the MicroKernel can process any other operations. The MicroKernel also returns this status code if the application passed an invalid position block for the file, or if the application passed a position block with a client ID other than the client ID used to open the file.

4: The application cannot find the key value.

The MicroKernel cannot find the specified key value in the index path. When you receive this status code on an Update or Delete operation, it usually means that the file is damaged, and you must recreate it. Occasionally, a corrupt key can cause this status code. Drop the key, then add it again. Also, pre-v6.x server engines return this status code if two separate files have different ACSs, but those ACSs have the same name. Never use the same name for different ACSs, regardless of the version you are using.

5: The record has a key field containing a duplicate key value.

The MicroKernel cannot add or update a record because the record has a key field that contains a duplicate key value for an index that does not allow duplicate values. The MicroKernel also returns this status code when it cannot create an index that does not allow duplicate key values because a duplicate key value already exists.

In pre-v6.0 MicroKernels, this status code indicates that you added an AUTOINCREMENT key and the field being indexed contains more than one zero.

6: The key number parameter is invalid.

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 for the file. Valid key numbers are 0 through 118.

7: The key number has changed.

The key number parameter changed before a Get Next, Get Next Extended, Get Previous, or Get Previous Extended operation. The operation requires the same key number parameter as the previous operation, because the MicroKernel uses positioning information relative to the previous key number.

In a related situation, the MicroKernel returns this status code when an application performs a Delete or Update operation immediately following a Get operation. If the application changes the value of the key number in the Delete or Update operation (from the value used with the preceding Get operation), the MicroKernel deletes or updates the record as requested and does not return this status code, at least not at this point. However, the MicroKernel does return this status code on the very first Get Next, Get Next Extended, Get Previous, or Get Previous Extended operation performed after the deletion or update, even if that Get operation uses the same key value the application passed to the Delete or Update operation.

If you need to change key numbers between consecutive Get Next, Get Next Extended, Get Previous, or Get Previous Extended operations (or in Delete or Update operations as described in the preceding paragraph), use a Get Position operation followed by a Get Direct/Record operation to reestablish positioning for the new index path.

8: The current positioning is invalid.

You must establish the current position in order to update or delete a record. Perform a Get or Step operation to establish the current position. The MicroKernel also returns this status code if the application passed an invalid position block for the file.

9: The operation encountered the end-of-file.

The MicroKernel returns this status code in one of the following situations:

• The operation encountered an end-of-file boundary or tried to read past a file boundary (end-of-file or start-of-file).

• In a Get Next Extended, Get Previous Extended, Step Next Extended, or Step Previous Extended operation, the number of records satisfying the filtering condition is less than the number of specified records to be returned, and the reject count or filter limit has not been reached.

• When reading a file in ascending order according to an index path, the MicroKernel has already returned the last record in that index path. When reading a file in descending order according to an index path, the MicroKernel has already returned the first record in the index path.

• When using the Get By Percentage operation, either the value supplied for the percentage is too high--it exceeds 10,000 decimal (0x2710)--or the file contains no records.

10: The key field is not modifiable.

During an Update operation, the application attempted to modify a key field that is defined as nonmodifiable.

11: The specified filename is invalid.

This status code indicates either that the specified filename does not conform to file naming conventions, or that the pathname is invalid. Make sure the filename or pathname is valid for the environment. This status code can also have the following meanings in client/server versions of the MicroKernel:

• The application attempted to open a file that has .^^^ as its extension. This extension is reserved for the MicroKernel to use during continuous operation. (Only server engines can use continuous operation.)

• The data buffer for a Begin or End continuous operation is not set up correctly.

• You attempted to load a remote file when your Communications Requester settings of Local and Requester are incorrectly set to Yes and No, respectively. To resolve this condition, run the appropriate Setup utility and change the Requester setting to Yes. For more information on the Setup utility, refer to the Pervasive.SQL User's Guide.

12: The MicroKernel cannot find the specified file.

Check the key buffer parameter to make sure the pathname is terminated with a blank or a binary zero. Also, ensure that the file exists. When accessing a file on a server, ensure that you have FILE SCAN rights to the directory in which the file resides. Occasionally, a corrupt key can cause this status code. Drop the key, then add it again.

This error code may also be returned when the file DBNames.CFG has been removed (for example, by Pervasive.SQL's cleanup utility) and old Data Source Names (DSNs) which reference that file are not removed from the ODBC.

13: The MicroKernel could not open the extension file for an extended file.

The MicroKernel could not open the extension file for an extended file that the application tried to open. For v7.0 and later MicroKernels, an extended file can consist of a base file and up to 15 extension files. Extension files must remain in the same volume and directory as their base files. The MicroKernel returns this status code if you delete, move, or rename the extension files.

For pre-v6.0 MicroKernels, 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.

14: The MicroKernel cannot create or open the pre-image file.

The MicroKernel uses pre-image files only for pre-v6.0 data files.

The MicroKernel returns this status code in one of the following situations:

• The MicroKernel cannot create a new pre-image file because the disk directory is full. The MicroKernel must be able to create a pre-image file.

• The MicroKernel cannot open the pre-image file to restore file integrity. If the pre-image file is erased or damaged, the MicroKernel cannot restore the file's integrity. Refer to the Pervasive.SQL User's Guide for more information about recovering damaged files.

• The workstation MicroKernel cannot assign a handle to the pre-image file because the MicroKernel was not started by a user with access rights to the pre-image file.

• The file structure of a pre-image file created by a v6.0 or later MicroKernel is different from the file structure of a pre-image file created by a v5.x MicroKernel. If you have an extraneous .PRE file in v5.x format and you are using a v6.0 or later MicroKernel, the MicroKernel returns this status code when you try to open the data file to which the .PRE file belongs.

15: The application encountered an I/O error during pre-imaging.

The MicroKernel uses pre-image files only for pre-v6.0 data files.

This status code indicates that either the disk is full or the pre-image file is damaged. If you receive this status code, proceed as follows:

• If the pre-image file is damaged, the integrity of the data file cannot be ensured. Refer to the Pervasive.SQL User's Guide for more information about recovering damaged files.

• If the disk is full, erase any unnecessary files.

16: The application encountered an expansion error.

This status code is obsolete in MicroKernel versions 6.0 and later.

The MicroKernel returns this status code when it encounters an error while writing the directory structure to disk prior to creating the expanded file partition. Either the MicroKernel cannot close the file, or a new page was added to the file and the MicroKernel cannot close and reopen the file to update the directory structure. Check for a disk hardware failure.

17: The application encountered a close error.

This status code is obsolete in MicroKernel versions 6.0 and later.

The MicroKernel returns this status code when it encounters an error while writing the directory structure to disk prior to closing the file. Either the MicroKernel cannot close the file, or a new page was added to the file, and the MicroKernel cannot close and reopen the file to update the directory structure. Check for a disk hardware failure. The MicroKernel also returns this status code if the application passed an invalid position block for the file.

18: The disk is full.

The MicroKernel can return this status code in the following situations:

• The disk is full, and the MicroKernel cannot expand the file to accommodate additional records. Erase any unnecessary files. If using a pre-v6.0 MicroKernel, you can possibly extend the file to gain additional disk space.

• There is not enough space to append a new page to the data file.

• The pre-image file is out of disk space. If your files are in pre-v6.0 format and you are in a transaction, the pre-image file size increases for the duration of the transaction. If you receive this status code, either reduce the number of operations in the transaction, or obtain more disk space.

• For files located on a NetWare server, the NetWare owner name for the file is no longer valid, and your application tried to insert or update records in the file, thus causing the file to expand. In this case, the MicroKernel returns this status code when it needs to add a page to the file, regardless of how much disk space is available. To check for an owner name, use the NetWare utility NDIR. To add an owner name, use either FILER (a NetWare text utility) or the NetWare Administrator graphical utility.

• In some environments, you can restrict the amount of disk space available to each user. This status code indicates that the application attempted to expand a data file beyond the amount of disk space allocated to the file's owner.

• You tried to read or modify a file which was not closed properly after a disk full error. Make sure that every application that used the file at the time of the disk full error closed the file successfully.

• If a client connected to a Pervasive server encounters Status 18, other clients performing read-only operations from the same disk may also receive a non-zero status (18 or 2).

19: The application encountered an unrecoverable error.

To ensure file integrity, recover the file as described in the Pervasive.SQL User's Guide.

20: The MicroKernel or Btrieve Requester is inactive.

Verify that the IPX/SPX or TCP/IP protocol is properly installed at the client machine.

Verify that no two machines on the network have the same Internal Network Number.

In the DOS and NetWare environments, you must load the MicroKernel and, if applicable, the Btrieve Requester before generating any requests. Also for NetWare, ensure that the appropriate communications modules are loaded at the server.

If you are running an application in a client/server environment and also need to access files located on a local drive, ensure that you enable both Local and Server access and that the local MicroKernel is available.

By default in the Windows and Windows NT environments, the Setup utility enables the Local Engine Usage option. To access a server engine but not a workstation engine, turn the Local option off and turn the Server option on. To access both workstation and server MicroKernels, enable both the Server option and the Local option.

Also, in the Windows environment, ensure that the Btrieve for Windows DLLs and MicroKernel executable are in your path or in the Windows system directory. Ensure that you do not have multiple copies of WBTICOMM.DLL or WBTRCALL.DLL installed on the same machine.

In the Windows NT server environment, you must start the MicroKernel before generating any requests. Ensure that the Windows NT DLLs are in your path. Also ensure that the appropriate communications modules are loaded at the server.

21: The key buffer parameter is too short.

The key buffer parameter is not long enough to accommodate the key field for the requested index path. Verify that the length of the key buffer equals the defined length of the key specified in the key number parameter.

22: The data buffer parameter is too short.

The data buffer parameter specified by the application was not large enough to accommodate either the minimum length of the record for an Insert or Update operation, or the entire record length for a Get or Step operation. Also, the data buffer may not be large enough to accommodate the length of data required for operations such as Create, Create Index, Stat, Get By Percentage, Find Percentage, or Version.

• For Get or Step operations, the MicroKernel returns as much data as it can and this status code, indicating that it cannot return the entire record.

• For an Insert operation, the MicroKernel does not insert the record if the data buffer is shorter than the fixed-length portion of the record.

• For an Update operation, if the data buffer is too short to contain the fixed-length portion of a record, the MicroKernel does not update the record.

• For the Create, Stat, and Create Index operations, the data buffer is not long enough to contain all the file specifications, the key specifications, and (if specified) the ACS definition.

• For the Get by Percentage or Find Percentage operation, the data buffer length is less than 4 bytes.

• For the Version operation, the data buffer length is less than 5 bytes.

  This status code can also indicate a corrupt file if the file allows variable-length records and you receive this status code on a Get or Step operation. In such a corrupt file, you can receive Status Code 54 when you use Get or Step operations to read other records. Recover the file according to the instructions in the Pervasive.SQL User's Guide.

23: The position block parameter is not 128 bytes long.

This status code is obsolete in Btrieve language interface versions 6.0 and later.

The position block parameter must be exactly 128 bytes long.

24: The page size or data buffer size is invalid.

The MicroKernel returns this status code in one of the following situations:

• The page size you specified when creating a file is invalid. The page size must be a multiple of 512 bytes and cannot exceed 4096 bytes.

• During a Create operation, the page size is the first file specification the MicroKernel checks. A Status Code 24 at this point can indicate an invalid data buffer parameter.

  In pre-v6.1 MicroKernels, the Open operation can return this status code. In this case, the MicroKernel cannot open the file because the file's page size exceeds the Largest Page Size configuration option. To successfully open the file, you must increase the value of the Largest Page Size configuration option and then reload the MicroKernel. The v6.1 or later MicroKernel does not return this status code from the Open operation.

25: The application cannot create the specified file.

The MicroKernel can return this status code if an application attempts to create a data file, but the disk directory or the disk itself is full. If the application is creating a file over an existing file, the MicroKernel returns this status code when the existing file is open or when the operating system prevents the operation for some other reason (for example, because the file is flagged transactional in NetWare).

Sometimes pre-v6.0 MicroKernels can return this status code if the HOLD parameter in NET.CFG or SHELL.CFG is set to ON and the application attempts to create a data file on a network drive. (The HOLD parameter is set to OFF by default.) Creating the file on a local drive is successful regardless of the value of the HOLD parameter.

26: The number of keys specified is invalid.

The number of keys specified for the page size is invalid. The number of key segments must be within the following limits:

Page Size	512	1024	1536	2048	2560	3072	3584	4096
Max. No. Key Segments	8	23	24	54	54	54	54	119

If the MicroKernel is configured to create files in v5.x format, the maximum number of key segments is 8 for files using 512 byte page sizes; the maximum number of key segments for all other v5.x files is 24.

For a key-only file, this status code is also returned if the number of keys specified is not one, or the avaliable linked keys is not zero (only one key is allowed for a key-only file.)

27: The key position is invalid.

The specified key field position is less than 1 or 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.

28: The record length is invalid.

The specified record length (plus overhead for duplicates, record usage count, variable record pointers, key pointers, and blank truncation information) must be less than or equal to the page size minus 6 bytes, and greater than or equal to 6 bytes.

For key-only files, the maximum record length is 253 bytes (255 bytes for a pre-v6.0 file).

29: The key length is invalid.

The specified key length must be greater than 0 but cannot exceed 255 bytes. The length of a key segment must agree with its key type if the key type implies a length (for example, an integer key must have a length evenly divisible by two). 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.

This error could also occur through a SQL CREATE INDEX statement, or through the creation of a SQL PRIMARY KEY or FOREIGN KEY, if the index, or key, references a nullable CHAR column of 255 characters (or VARCHAR or 254). This is because an additional byte of storage space is needed for the null indicator for the column. This additional byte causes the actual length of the index to be one byte longer, or 256 bytes. If status code 29 is received during any of these SQL operations, reduce the size of the column and try again, or create the column as NOT NULL and try again. For a foreign key, if you decrease the size of the column, you must decrease both the referencing column and the referenced column.

30: The file specified is not a MicroKernel file.

Either the MicroKernel did not create the file, or a pre-v3.x MicroKernel created it. You can also receive this status code from earlier versions of Btrieve when you open a file created by a later version, if the file has a format incompatible with the earlier version. This status code can also indicate that the first page of the file is damaged. Use a backup copy of your data file. If you receive this status code and you suspect that the header page of the source file is damaged, recover the file as described in the Pervasive.SQL User's Guide.

31: The file is already extended.

This status code is obsolete in MicroKernel versions 6.0 and later.

The MicroKernel returns this status code if an application tries to extend a file that has already been extended; you can only extend a file once.

32: The file cannot be extended.

The MicroKernel returns this status code when it must create an extension file to accommodate a file which is growing larger than the operating system's file size limit, but the MicroKernel encounters an error from the operating system when it tries to create and open the new extension file. Possible causes for receiving this status code include the following: the directory is full, the disk is full, or the MicroKernel has not been granted sufficient rights by the operating system.

33: The MicroKernel cannot unload.

In the DOS environment, the MicroKernel returns this status code for one of the following two reasons:

• You attempted to unload the MicroKernel when you have loaded another terminate and stay resident (TSR) program after you loaded the MicroKernel. Unload the other TSR before unloading the MicroKernel.

• You attempted to unload the MicroKernel from a 32-bit application that uses the BSTUB interface with the DOS/4G extender.

34: The specified extension name is invalid.

This status code is obsolete in MicroKernel versions 6.0 and later.

The MicroKernel returns this status code if an application specified an invalid filename for the extended partition. Check the validity of the filename.

35: The application encountered a directory error.

Either a Get Directory operation specified a drive that does not exist, or a Set Directory operation specified an invalid pathname. Check the validity of both the drive and the pathname.

36: The application encountered a transaction error.

Version 7.0 and later MicroKernels return this status code if the MKDE defines too many transaction nesting levels. The v7.0 MicroKernel allows each transaction a total of 255 internal nesting levels. However, the MKDE v4.0 uses some of these levels internally to enforce atomicity on INSERT, UPDATE, and DELETE statements. Therefore, a session can effectively define no more than 253 savepoints to be active at one time. This limit may be further reduced by triggers that contain additional INSERT, UPDATE, and DELETE statements. If your operation reaches this limit, you must reduce the number of savepoints or the number of atomic statements contained within it.

Version 6.x MicroKernels return this status code if the MicroKernel tried to perform a Begin Transaction operation, but it was not configured to allow transactions. Use the Setup utility to specify a higher value for the Number of Transactions configuration setting. Next, stop and then restart the MicroKernel so that your changes take effect.

• On a machine that is running both a workstation MicroKernel and a Btrieve Requester accessing a client/server MicroKernel, ensure that both the workstation MicroKernel and the client/server MicroKernel are configured for transactions.

• In a client/server environment, all servers running MicroKernels to which the client machine is attached must be configured for transactions, even if the files involved in the transaction are only located on one of the servers.

37: Another transaction is active.

The application issued a Begin Transaction (19 or 1019) operation while another transaction was active by the same user or task; the active transaction can be nested or non-nested. This status code often indicates a problem in nested transactions within your application.

38: The MicroKernel encountered a transaction control file I/O error.

This status code is obsolete in MicroKernel versions 7.0 and later.

The MicroKernel returns this status code if an error occurs when the MicroKernel tries to write to the transaction control file. Possible causes for receiving this status code are that the disk is full, the disk is write protected, the transaction control file (BTRIEVE.TRN) that is created when you load the MicroKernel has been deleted, or the transaction control file is flagged read-only or is corrupt.

39: A Begin Transaction operation must precede an End/Abort Transaction operation.

The application issued an End Transaction (20), End Nested Transaction (2020), Abort Transaction (21), or Abort Nested Transaction (2021) operation without a corresponding Begin Transaction (19 or 1019) or Begin Nested Transaction (2019 or 3019) operation. Make sure that each End or Abort Transaction operation in your program is executed only after a successful Begin Transaction operation.

40: The file access request exceeds the maximum number of files allowed.

This status code is obsolete in MicroKernel versions 6.0 and later.

The application tried to access more than the maximum number of files allowed within a transaction. You set the maximum number of different files that you can access during a logical transaction when you configure the MicroKernel.

41: The MicroKernel does not allow the attempted operation.

The MicroKernel returns this status code for one of the following reasons:

• The application tried to perform an operation that is not allowed at this time. The MicroKernel does not allow some operations under certain operating conditions. For example, the MicroKernel returns this status code if the application attempts to perform a Step operation on a key-only file.

• If using a server engine, the key number parameter of a continuous operation MicroKernel call is not valid.

  Also, the MicroKernel prohibits certain operations during transactions because they have too great an effect on the file or on performance. These operations include Set Owner, Clear Owner, Create Index, and Drop Index.

42: A file previously opened in Accelerated mode was not closed.

This status code is obsolete in MicroKernel versions 6.0 and later.

The MicroKernel returns this status code for one of the following reasons:

• Either the application tried to open a v5.x data file that was previously accessed in Accelerated mode by a v5.x MicroKernel and never successfully closed, or the application tried to open a file for which a v6.0 or later MicroKernel encountered an unrecoverable error during a Set or Clear Owner operation. The file's integrity cannot be ensured. Refer to the Pervasive.SQL User's Guide for information about recovering damaged files.

• Your application tried to open a file in MicroKernel v5.x format using a v5.x MicroKernel; however, that same file was previously accessed by a v6.0 or later MicroKernel, which failed to close the file successfully and left a pre-image file on the disk. Version 5.x MicroKernels cannot read pre-image files created in v6.0 or later format.

43: The specified record address is invalid.

The MicroKernel returns this status code for one of the following reasons:

• The record address specified for a Get Direct operation is invalid. Either the address is outside the file's boundaries, or it is not on a record boundary within or on a data page, or the record at the specified address has been deleted. For a Get Direct operation, specify the 4-byte address obtained by a Get Position operation.

• If the records' file is in v5.x format, this status code can indicate a file access conflict. For example, task 1 has a file locked in an exclusive transaction. Task 2 is reading records from the same file and tries to update a record that the transaction inserted. If task 2 reads the record and then task 1 aborts the transaction, task 2 receives this status code when issuing the Update operation.

• For a Find Percentage operation that is seeking a percentage based on a record's physical location within the file, the specified record address is invalid.

• The file may be corrupt, and you must recover it. Refer to the Pervasive.SQL User's Guide for information about recovering damaged files.

44: The specified key path is invalid.

The application tried to use the Get Direct/Record operation to establish positioning on an index path for a key whose value is null in the corresponding record. The MicroKernel cannot establish positioning based on a null key value. Pre-v6.x MicroKernels return Status Code 82 in this situation; therefore, write your application to check for both of these status codes.

45: The specified key flags are invalid.

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. Also, you cannot use the null or manual key attributes in a key-only file. The MicroKernel also returns this status code if the application attempted to specify a different ACS for two or more segments of a segmented key.

46: Access to the requested file is denied.

The MicroKernel returns this status code for one of the following reasons:

• The application opened a file in Read-only mode and tried to perform a Write operation on that file.

• The application attempted to perform a Write operation on a file that is flagged read-only by the operating system.

• When the application opened the file, it did not correctly specify the owner name required for updates.

• (Workstations Only) If a workstation engine user or task opens a file that client machine has opened using a server MicroKernel, the MicroKernel returns this status code if the workstation engine user attempts to write to the file.

47: The number of files opened exceeds the maximum allowed.

This status code is obsolete in MicroKernel versions 6.0 and later.

Pre-v6.0 workstation MicroKernels return this status code when the number of files opened in Accelerated mode exceeded the number of buffers available in the MicroKernel's cache. When a file is opened in Accelerated mode, the MicroKernel reserves one of its cache buffers for the file. It always reserves five empty buffers for index manipulation. Reconfigure Btrieve with both a smaller /P configuration option (to allocate more buffers) and a larger /M option (to increase the cache allocation).

48: The alternate collating sequence definition is invalid.

The MicroKernel returns this status code for one of the following reasons:

• The first byte of an ACS definition (the identification byte) does not contain the hexadecimal value AC (for user-defined ACSs), AD (for locale-specific ACSs), or AE (for international sorting rules support). Make sure that the first byte contains the appropriate value.

• You are running a pre-v6.0 MicroKernel, and you attempted to add an index with a locale-specific ACS to a file in v5.x format. Pre-v6.0 files do not support locale-specific ACSs.

• You are running the v6.0 or later MicroKernel with the Create File Version option set to v5.x, and you attempted to create a file that contains a key with a locale-specific ACS. Pre-v6.0 files do not support locale-specific ACSs.

49: The extended key type is invalid.

The MicroKernel returns this status code for one of the following reasons:

• You tried to create a file or an index with an invalid extended key type, or you are trying to assign an ACS to a BINARY key or key segment. You can assign an ACS only to a STRING, LSTRING, or ZSTRING key type.

• You defined an index requiring an ACS, but no ACS definition exists (either in the file or in the key definition passed in the data buffer).

• You attempted to create a key segment with both the Case Insensitivity and the Alternate Collating Sequence flags set, and the MicroKernel is configured to create files in v5.x format. This combination is invalid for v5.x files.

• You attempted to create a file that contains multiple ACSs, but you are running a pre-v6.1 MicroKernel. Only v6.1 and later MicroKernels support multiple ACSs.

• You are running the v6.x or later MicroKernel with the Create File Version option set to v5.x, and you attempted to create a file with a NUMERICSA or NUMERICSTS key. Pre-v6.0 files do not support these key types.

• You set the default file creation format to v6.x, but you are using one of the new Pervasive.SQL 2000 data types, such as CURRENCY or TIMESTAMP, which require the v7.x file format.

50: The file owner is already set.

The application tried to perform a Set Owner operation on a file that already has an owner. Use the Clear Owner operation to remove the previous owner before specifying a new one.

51: The owner name is invalid.

The MicroKernel returns this status code for one of the following reasons:

• If the application received this status code from a Set Owner operation, the owner names specified in the key buffer and data buffer do not match.

• If this status code occurred during an Open operation or a DROP TABLE statement, the application attempted to open a file that has an owner name assigned to it. The application must specify the correct owner name in the data buffer. Ensure that the owner name is null-terminated in the data buffer and that the data buffer length is set long enough to include the owner name plus the null terminator.

• If an application received this status code when removing a file from Continuous Operation mode, then the client ID of the calling application differs from the client ID of the application that originally put the file into Continuous Operation mode. (Version 7.0 and later MicroKernels return Status Code 88 in this instance.)

52: An error occurred while writing to the cache.

This status code is obsolete in MicroKernel versions 6.0 and later.

While trying to make a cache buffer available, the MicroKernel attempted to write data to a disk from a file that was previously opened in Accelerated mode. The operating system returned an I/O error during the write. This generally indicates a hardware memory problem. Unload and reload Btrieve before you continue.

53: The language interface version is invalid.

An application tried to access a file containing variable-length records with a language interface from Btrieve v3.15 or earlier. To access files with variable-length records, you must use a v4.x or later interface. The MicroKernel can also return this status code when an application calls BTRVID using a pre-v6.0 MicroKernel with the DOS interface. Pre-v6.0 MicroKernels do not support BTRVID.

54: The variable-length portion of the record is corrupt.

During a Get or Step operation, the MicroKernel could not read all or part of the variable-length portion of a record. The MicroKernel returns as much data as possible to the application. This status code usually indicates that one or more pages used to store variable-length records are corrupt. Check the data buffer length the MicroKernel returns to see how much of the record was returned. Recover the damaged file as described in the Pervasive.SQL User's Guide.

55: The application specified an invalid attribute for an AUTOINCREMENT key.

The application tried to specify either the segmented or duplicate attribute for an AUTOINCREMENT key type. An AUTOINCREMENT key can be part of a segmented key only if the key number of the AUTOINCREMENT key is less than the key number of the segmented key. An AUTOINCREMENT key cannot allow duplicates.

56: An index is incomplete.

An index can be damaged if a Create Index operation (31) or a Drop Index operation (32) is interrupted before it runs to completion. Perform a Drop Index operation to completely remove the damaged index from the file, then rebuild the index with the Create Index operation, if desired.

57: An expanded memory error occurred.

This status code is obsolete in MicroKernel versions 6.0 and later.

Btrieve for DOS returns this status code if it receives an error from the Expanded Memory Manager. This status code usually means that the MicroKernel was unable to save or restore the memory mapping register context, indicating an incompatibility with another application that uses expanded memory.

58: The compression buffer length is 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 the MicroKernel using the Setup utility, specifying a higher value for the Largest Compressed Record Size option.

59: The specified file already exists.

This status code is returned for the Create operation if the application specified -1 in the key number parameter and the name of an existing file in the key buffer parameter. To overwrite the existing file, remove the -1 from the key number parameter. To preserve the existing file, alter the filename specified in the key buffer parameter.

60: The specified reject count has been reached.

The MicroKernel rejected the number of records specified by the reject count before a Get Next Extended, Get Previous Extended, Step Next Extended, or Step Previous Extended operation found the requested number of records that satisfy the filtering condition. Check the first two bytes returned in the data buffer for the number of records that were retrieved.

61: The work space is too small.

The Get Next Extended, Get Previous Extended, Step Next Extended, and Step Previous Extended operations use a buffer as work space. This status code indicates that the work space (set by default to 16 KB) is not large enough to hold the filtering data buffer structure and the largest record to be received. When using v6.15.2 and later MicroKernels, you receive Status Code 0 if the work space is large enough to hold the filter/extraction expression and enough of the record to include all of the fields to be filtered or extracted.

62: The descriptor is incorrect.

The descriptor (data buffer structure), which is passed for a Get Next Extended, Get Previous Extended, Step Next Extended, or Step Previous Extended operation, is incorrect. The descriptor length (the first two bytes of the data buffer) on the extended operation call must be the exact length of the descriptor. This requirement does not apply to the data buffer length option, which can still be declared longer than necessary.

On a Stat Extended operation, the signature field in the data buffer is not set to 0x74537845, the subfunction field is not set to 0x00000001, or the namespace field is not set to 0x00000000.

On a Get Direct/Chunk or Update Chunk operation, the descriptor structure in the data buffer is incorrect, or it is inconsistent (either internally or with respect to the data buffer length).

63: The data buffer parameter specified on an Insert Extended operation is invalid.

An Insert Extended operation provided an invalid buffer. Either the buffer length is less than 5 bytes, or the number of records specified is 0. Correct the buffer length or the number of records.

64: The filter limit has been reached.

The MicroKernel returns this status code for any of the following reasons:

• During a Get Next Extended, Get Previous Extended, Step Next Extended, or Step Previous Extended operation, a rejected record was reached; no other record can satisfy the given filtering condition, going in the direction that the operation specified. This is applicable only if the first segment of the key that the key number specified is also used as the first term of the filtering field.

• You can receive this status code when the number of records to be retrieved, which is specified in the data buffer of the extended operations, is greater than the number of records present in the Btrieve file that satisfy the filter condition.

65: The field offset is incorrect.

The field offset in the extractor of a Get Next Extended, Get Previous Extended, Step Next Extended, or Step Previous Extended operation is invalid based on the length of the retrieved record. Make sure that the field offset is a valid value (from 0 through the record length minus 1).

66: The maximum number of open databases has been exceeded.

The MicroKernel tried to open files bound to too many the MKDE databases. Use the Setup utility to configure a higher value for the Maximum Databases option. Refer to the Pervasive.SQL Programmer's Guide for more information about bound files.

67: The MicroKernel cannot open the SQL data dictionary files.

The MicroKernel returns this status code for one of the following reasons:

• An application attempted to use a data file that is bound to a the MKDE database, but the MicroKernel could not open one of the MKDE data dictionary files (FILE.DDF or, if the file has RI definitions, RELATE.DDF) or the configuration file (DBNAMES.CFG).

• You attempted to create a file with the Replace option, and a bound the MKDE data file with the same name and location already exists. However, the MicroKernel could not open the MKDE data dictionary file FILE.DDF, or the configuration file (DBNAMES.CFG).

  If the data file has RI definitions, the DBNAMES.CFG file must be in the location you specified using the Setup utility; you determine the location of DBNAMES.CFG by using the Database Names Directory option for the MicroKernel. Also, ensure that FILE.DDF and RELATE.DDF (if the file has RI definitions) are in the locations specified by the database's configuration.

  Refer to the Pervasive.SQL Programmer's Guide for more information about RI.

68: The MicroKernel cannot perform the RI Delete Cascade operation.

The MicroKernel cannot enforce the Delete Cascade rule on a file under RI control because the record that the application attempted to delete has more than 16 levels of descendants. Delete records from the lower levels, and then try again to delete the record that the application was attempting to delete initially. Refer to the Pervasive.SQL Programmer's Guide for more information about RI.

69: The Delete operation specified a file that is damaged.

The application encountered an error while the MicroKernel was attempting to enforce the Delete Cascade rule in response to a Delete operation. This status code indicates that the related file has been damaged and must be recreated. Refer to the Pervasive.SQL User's Guide for more information about recovering damaged files.

Refer to the Pervasive.SQL Programmer's Guide for more information about RI and the Delete Cascade rule.

71: There is a violation of the RI definitions.

If you have attempted an Insert operation on a file under RI control, you can receive this status code if a foreign key value in the record to be inserted does not have a corresponding primary key in the referenced file. If you are performing an Update operation, there are two possible causes for this status code:

• You attempted to change the value of a primary key.

• You attempted to change the value of a foreign key to a value that does not exist for the defined primary key.

  If you attempted a Delete operation, the restrict rule is enforced, and a primary key value in the record you are trying to delete references a foreign key in the referenced file. Refer to the Pervasive.SQL Programmer's Guide for more information about RI.

72: The MicroKernel cannot open the RI referenced file.

The referenced file cannot be found at the location specified by FILE.DDF and DBNAMES.CFG. Be sure that the referenced file is in one of the data file locations that the DBNAMES.CFG file specifies for the named database.

• If the DBNAMES.CFG file is defined on a server, verify that the file location does not contain a drive letter.

• If the DBNAMES.CFG file is defined for a workstation engine, make sure that the drive letters are the same (and map to the same locations) as specified in DBNAMES.CFG.

  Refer to the Pervasive.SQL Programmer's Guide for more information about RI.

73: The RI definition is out of sync.

The MicroKernel returns this status code for one of the following reasons:

• You tried to open a data file that is bound to a the MKDE database, and the database to which the file is bound was not found in the DBNAMES.CFG file.

• You tried to open a data file with RI definitions that is bound to a the MKDE database, and the table to which the file is bound was not found in the database's FILE.DDF file, or the table's location and filename does not match the file's location and filename as configured in the DBNAMES.CFG or FILE.DDF file.

• You attempted to modify a bound file, and the RI definition for that file disagrees with the definition in the RELATE.DDF file.

• You can also receive this status code on an Insert or Delete operation, or on an Update operation that would change a foreign key, if the file related to this file is out of sync (an attempt to open or modify the related file would have returned this same status code).

• You attempted to create a file with the Replace option, and a bound the MKDE data file with the same name and location already exists. However, the MicroKernel detected that the existing bound file was out of sync (that is, an attempt to open the existing file would have returned this same status code).

  Check the RI constraints on your database. For information about how to do this, refer to the Pervasive.SQL User's Guide.

74: The MicroKernel aborted the transaction.

This status code is obsolete in MicroKernel versions 6.0 and later.

This is an informative status code. A NetWare-based MicroKernel replaced an End Transaction operation with an Abort Transaction operation after detecting an error for a Transaction Tracking System (TTS) file inside the transaction. The MicroKernel then executed the Abort Transaction operation.

76: There is a conflict on the referenced file.

An application attempted to perform an Update, Insert, or Delete operation on an RI-controlled file that references another file. The application cannot open the referenced file for RI checking because it is already open in Exclusive mode. Wait until the referenced file is closed or is opened in a mode other than Exclusive, and then retry the operation. Refer to the Pervasive.SQL Programmer's Guide for more information about RI.

77: The application encountered a wait error.

This status code is obsolete in MicroKernel versions 7.0 and later.

This is an informative status code. You must retry the operation yourself; the MicroKernel does not automatically retry the operation. A client/server MicroKernel returns this status code in one of the following situations:

• The application specified a wait lock bias for an operation, but another user has locked the requested resource.

• The application is currently processing a wait transaction and tried to access a file that another user has locked.

  When you are using the Btrieve Requester to access the MicroKernel, the Requester waits and retries if a requested resource is locked. When a server-based application is accessing the MicroKernel and the requested resource is locked, a wait is also required. In this case, the MicroKernel is expected to perform the wait. Because this would occupy the MicroKernel and lock out other users who might be trying to release the requested resource, the MicroKernel does not perform the wait. Instead, it returns this status code, and the server-based application must retry later.

78: The MicroKernel detected a deadlock condition.

The application should clear all resources (for example, by aborting or ending the transaction or releasing all record locks) before proceeding. This breaks the deadlock, allowing other applications to access the resources for which they are waiting.

79: A programming error occurred.

This status code is obsolete in MicroKernel versions 7.0 and later.

Although very rare, it is possible to receive this status code when there is a malfunction that the MicroKernel cannot specifically detect or from which the MicroKernel cannot recover. Retry the operation. If the error persists, there may be system corruption; try to clear the system by rebooting, and then try the operation again.

80: The MicroKernel encountered a record-level conflict.

The MicroKernel did not perform the Update or Delete operation because of a record-level conflict. For example, station A reads a record, station B reads the same record and updates it, and then station A attempts to update the record. The application should reread the record prior to resending an Update or Delete operation. Alternatively, the application can employ record locks to avoid conflicts.

In key-only files, you receive this status code if the record is moved in the file's b-tree after being read and before being updated or deleted. A record can move as a result of other records being inserted, updated, or deleted.

In pre-v6.0 workstation MicroKernels, a page-level conflict also produces this status code. For example, station A reads a record, station B reads and updates a different record on the same data page, and then station A attempts to update the record it read. (You also receive this status code with v6.0 and later MicroKernels if the files are in v5.x format.)

In pre-v6.0 workstation MicroKernels, a conflict can also occur if station A reads a record, station B reads a different record and updates it, causing duplicate pointers to be updated on record A, and then station A tries to update the record.

81: The MicroKernel encountered a lock error.

The MicroKernel returns this status code in one of the following situations:

• The application tried to unlock a record that is locked with a multiple record lock, but the record position stored in the data buffer does not correspond to any record locked in the associated file.

• The application tried to unlock a single-record lock with a multiple-record lock or vice-versa.

• (Workstation Only) You tried to open a v6.0 or later file in Read-only mode on a NetWare drive on which you only have Read and Filescan rights. The MicroKernel cannot create the .LCK file. You must obtain Create and Write rights or redirect the .LCK files to a directory on which you have Create and Write rights. This directory must be shared by all users of a single datafile. For example, if two users are sharing a data file located at \\example\stats1:\test\file.btr and the lock files are redirected to C:\, then file sharing problems occur due to the users not sharing a single lock file directory.

• (Workstation Only) You tried to open a file in MEFS mode on a local drive, and the DOS SHARE.EXE program is not loaded. Either load SHARE.EXE or open the file in SEFS mode.

• (Workstation Only) You manipulated a file (you opened and then locked all or part of the file) in MEFS mode on a local drive, and the DOS SHARE.EXE program ran out of locks. Reload the SHARE program and specify a higher value for the /L and /F options.

• (Workstation Only) You redirected the lock file to a local drive with the /I option, and the DOS SHARE.EXE program is not loaded.

• (Workstation Only) You are running in MEFS mode, and you ran out of operating system file handles when the MicroKernel attempted to allocate a file handle to the .LCK file. Refer to your operating system documentation for instructions about configuring your operating system to allow more file handles.

• In pre-v7.x MicroKernels, the lock table is full. Decrease the number of locks that the application uses, or use the Setup utility to specify a higher value for the Number of Locks option.

82: The MicroKernel lost positioning.

When performing a Get Next or Get Previous operation on a key with duplicates, the application tried to retrieve a record that was deleted or whose key value was modified by another application. Use a Get Equal or a Get Direct/Record operation to re-establish positioning. (See Status Code 44: The specified key path is invalid. for a related positioning problem.)

83: The MicroKernel attempted to update or delete a record that was read outside the transaction.

This status code is obsolete in MicroKernel versions 7.0 and later.

The MicroKernel returns this status code if the application tried to update or delete a record within a transaction, but it did not read the record within the transaction. The application must read the record within the transaction before attempting to modify the data.

84: The record or page is locked.

The application tried to apply a no-wait lock on a record that is currently locked by another application, or the application tried to access a file in a no-wait transaction while another application holds one or more active record locks in that file. This status code can also occur if the application tried to update or delete a record locked by another application.

The application can use either of the following recovery methods:

• Retry the operation until it is successful. This can be the simplest and quickest solution for a network with light to moderate use.

• Use the wait option (+100/+300) instead of the no-wait option (in versions that support the wait option).

  The MicroKernel can return this status code on an Insert, Update, or Delete operation when it attempts to lock an index page to insert or delete a key value. Have your application check for this status code and retry the operation if the status code is returned.

  On Btrieve for NetWare, you can receive status 84 when running an application on a Win95 client if the NetWare operating system runs out of record locks. To solve this, increase the "maximum record locks per connection" and, if necessary, the "maximum record locks" (system wide limit) on the NetWare server.

85: The file is locked.

The MicroKernel returns this status code in one of the following situations:

• The workstation MicroKernel has a file open, and client machine that has the Requester loaded tries to open the same file via the server MicroKernel. The server MicroKernel cannot open the file because it cannot obtain exclusive access. The client machine that has the Requester loaded receives this status code.

• In a workstation engine environment, the MicroKernel can return this status code on an Open, Insert, Update, or Delete operation for a file under heavy usage by multiple users or tasks. The MicroKernel must momentarily have exclusive access to the file during these operations, and it retries the operation several times before returning this status code. In this case, the application can reissue the operation. In addition, you can reconfigure the workstation MicroKernel with a lower Operation Bundle Limit and Initiation Time Limit to reduce the amount of time the MicroKernel keeps a lock on the file. Refer to the Pervasive.SQL User's Guide for more information on how to do this.

• In a workstation environment, a v6.15 or later MicroKernel has a pending modification (Insert, Update, or Delete) as an incomplete system transaction in a file that has been opened in MEFS mode. If multiple users or tasks attempt to access (Get/Step) or modify (Insert, Update, or Delete) the shared file, the MicroKernel returns this status code. An access operation can receive this status code only if the writing phase of the system transaction has started.

  Reconfiguring the MicroKernel with a lower Operation Bundle Limit and Initiation Time Limit reduces the occurrences of file contention that produce this status code. Refer to the Pervasive.SQL User's Guide for more information about using the setup utility to reconfigure the MicroKernel.

  If you are a developer and want more information about system transactions, refer to the Pervasive.SQL Programmer's Guide.

• While one user has a file locked in an exclusive transaction, another user attempts to lock all or part of that file.

• When opened by a server MicroKernel, a file is in transition into Continuous Operation mode. Retrying eventually works.

• When opened by a server MicroKernel, two data files have the same filename but different extensions (for example, INVOICE.HDR and INVOICE.DET). One file is open and in Continuous Operation mode, causing the MicroKernel to generate a delta file (for example, INVOICE.^^^). The MicroKernel returns this status code when you attempt to open the second file.

• When opened by a Windows NT server MicroKernel using Microsoft File and Print Services for NetWare on behalf of a Win16 Windows client, the file was also opened simultaneously by a Win32 Windows NT or Windows 95 machine. This causes the server MicroKernel to open the same physical file using two different paths.

86: The file table is full.

Using the Setup utility, specify a higher value for the Open Files configuration option.

87: The handle table is full.

Either you have attempted to open more handles than the MicroKernel is configured to support, or the MicroKernel attempted to open more files than the operating system allows. To configure the MicroKernel to allow more handles, use the Setup utility and increase the value of the Handles option.

To configure your operating system to allow more handles, refer to your operating system documentation. It is helpful to know the following details regarding the MicroKernel's requirements for handles from the operating system. When the same file is opened multiple times, the MicroKernel uses only one operating system handle. However, if the file is in v6.x or later format and the file is shared via MEFS mode, the MicroKernel opens a second handle for the associated .LCK file.

If the file is in v5.x format, the MicroKernel might request a second handle, for the .PRE file. Also, if the file (in any format) is placed in Continuous Operation mode, the MicroKernel requests another handle for the delta file. If the file is extended, the MicroKernel requests an operating system handle for each of the extension files.

88: The application encountered an incompatible mode error.

The MicroKernel returns this status code in one of the following situations:

• If an application opens a file in Exclusive mode, all other applications receive this status code when they try to open the same file in any mode.

• If an application opens a file in any mode other than Exclusive, all other applications receive this status code when they try to open the same file in Exclusive mode.

• (Workstation Only) If a user or task opens a file in MEFS mode, all other users or tasks using the same MicroKernel receive this status code when they try to open the same file in SEFS mode.

• (Workstation Only) Similarly, if a user or task opens a file in SEFS mode, all other users or tasks using the same MicroKernel receive this status code when they try to open the same file in MEFS mode.

• (Workstation Only) If a user or task opens a file in Accelerated mode and MEFS is enabled, all other remote users or tasks receive this status code when they try to open the same file in any mode. All other local users or tasks receive this status code when they try to open the same file in any mode other than Accelerated.

• If another client machine has the Requester loaded and has the file open, applications running v6.15 or later MicroKernels receive this status code when they try to open the same file in SEFS mode.

  Using the MicroKernel's Continuous Operation mode, this status code can also indicate one of the following situations:

• You attempted to remove a file from continuous operation, but the file is not in Continuous Operation mode.

• You attempted to remove a file from continuous operation, but a different client placed the file into continuous operation.

• You attempted to include two files in continuous operation that have the same name but different extensions.

• You attempted to include a file in continuous operation, but the file is already in continuous operation.

89: A name error occurred.

This status code is obsolete in MicroKernel versions 5.0 and later.

BSERVER was loaded before you specified the short name to which the device was redirected. You must specify all short names that you want to share with the NET SHARE command before you start BSERVER.

90: The redirected device table is full.

This status code is obsolete in MicroKernel versions 6.0 and later.

The DOS Requester's redirection table or server routing table is full. This occurs if you attach to additional servers or map additional drives after loading the Requester. Reload the Requester, specifying a larger value for either the Number of File Servers (/S) option or the Number of Mapped Drives (/R) option. This status code also occurs if you detach from a server and attach to a different server. Once a client has attached to a server, the Requester does not remove its name from the server routing table.

91: The application encountered a server error.

The MicroKernel returns this status code in one of the following situations:

• The Requester cannot establish a session with the server. Either the client/server MicroKernel is not loaded or the server is not active.

• The SPX drivers are not installed or are outdated.

• The value for the Number of Sessions configuration option is too low. Use the Setup utility to specify a higher value for this option.

• An application specified a path for a file and did not include the volume name in the path.

• The Btrieve Message Router has not been loaded, and the following situation has occurred: an application that uses both the Btrieve Message Router and the MicroKernel to make remote calls (and which therefore includes the server and volume name when performing an Open operation) has attempted to open a remote file. Because the Btrieve Message Router does not interpret the server name, the MicroKernel attempts to do so but cannot.

• A communication or network addressing problem exists in your network environment, so the MicroKernel requests never reach their destination server address. Ensure that your client and server network components are up to date and certified for your network environment.

• For NetWare servers only:
  • the Maximum Packet Receive Size configuration option is inappropriate for your environment. For example, the setting should be 1500 for an Ethernet LAN or 4096 for a Token-Ring LAN.
  • The user count limit has been exceeded. Either close a session or upgrade your user count. For more information about purchasing and installing additive user counts, refer to the Pervasive.SQL User's Guide.
  • Ensure that the NDS network number is the same as the Internal Network Number viewed by BINDER.EXE output.
  • You ran BUTIL.NLM to roll forward a file using a log filename other than the default, and your BLOG.CFG file did not contain a correct entry such as "\dir\file.ext=vol:\dir\log.ext".

92: The transaction table is full.

This status code is obsolete in MicroKernel versions 7.0 and later.

The MicroKernel returns this status code if the application exceeded the maximum number of active transactions. Use the Setup utility to specify a higher value for the Number of Transactions configuration option.

93: The record lock types are incompatible.

The application tried to mix single-record locks (+100/+200) and multiple-record locks (+300/+400) in the same file at the same time. You must release all locks of one type before you can execute a lock of the other type.

94: The application encountered a permission error.

The MicroKernel returns this status code in one of the following situations:

• The application tried to open or create a file in a directory without the proper privileges. The MicroKernel does not override the network privileges assigned to users.

• The designated server is in the server routing table, but your particular client is not logged into that server.

• The system data source name (DSN) on the server has an error in the pathname to the data files.

• Both the server-based and workstation MicroKernels (pre-v6.15) are trying to access the same file at the same time.

• A NetWare application tried to access a file using NetWare Runtime support with the given username. Specifically, one of the following situations exists regarding the supplied username:
  • The user is not a valid user on the NetWare Runtime server.
  • The user does not have the appropriate rights to access the file.
  • The username is ADMIN or SUPERVISOR. For security reasons, the MicroKernel does not enable you to use ADMIN or SUPERVISOR as a username when enabling NetWare Runtime support.

• When using the Win32 Requester from a Windows NT or Windows 95 client machine to a NetWare server, you must use the same username for logging in to both the client machine and the NetWare server. You cannot be logged in to NetWare as SUPERVISOR or ADMINISTRATOR.

• When using the Win32 Requester from a Windows NT or Windows 95 client machine using NetWare emulation to a Windows NT server, the server cannot use Microsoft File and Print Services for NetWare. This causes the requester to attempt authentication as though the server were a NetWare Runtime server.

• It is recommended that you keep the default Requester setting of Yes on FPNW servers running Pervasive.SQL. You may receive a Status Code 94 if you change this setting to No when you are running the Btrieve Interface locally on the FPNW server and are using a local FPNW drive mapping or local FPNW UNC path.

95: The session is no longer valid.

The server MicroKernel returns this status code for one of the following reasons:

• The previously established session is no longer active due to an error at the client machine, at the server, or on the network. Verify that the client machine is still attached to the server, and then unload and reload the Btrieve Requester.

• The server MicroKernel has reached the maximum number of SPX sessions. Use the Monitor utility to check this statistic. Use the Setup utility to specify a higher value for the Number of Sessions configuration option.

• This status code could indicate a time delay problem if the client machine does not receive a response back from the server in an appropriate timeframe or after an appropriate number of retries. Refer to your network configuration documentation for information about increasing timeout and retry parameters. This is often necessary in a WAN environment or a LAN configuration with heavy network traffic.

• For NetWare servers:
  • Verify that the Maximum Packet Receive Size configuration option is appropriate for your environment. For example, the setting should be 1500 for an Ethernet LAN.
  • Ensure that the SPX timeout parameters are set as follows in both the client machine's NET.CFG file and the server's SPXCONFG.NLM file:

    SPX VERIFY TIMEOUT=54
    SPX LISTEN TIMEOUT=108
    SPX ABORT TIMEOUT=540
    
    These three values must have a 1:2:10 ratio. You can increase these
    values to at most three times the default. If you continue to receive this
    status code after increasing these values, the problem is most likely
    not related to these settings.
    

• For Windows NT servers, verify that the Maximum Packet Size registry setting is 576 decimal or 240h. The path to the MaxPktSize registry setting is HKEY_LOCAL_MACHINE\System\currentControlSet\
  Services\NwInkIPX\NetConfig\MaxPktSize.

  If you continue to receive this status code after increasing the network timeout parameters, this status code usually indicates a problem with network communications. Verify that you have up to date network cards and drivers; for example, incompatible LAN card drivers can also cause this status code to occur. Consult your LAN administrator for network communication troubleshooting.

96: A communications environment error occurred.

The MicroKernel returns this status code for one of the following reasons:

• You tried to attach to the MicroKernel on a server, but the SPX connection table or the MicroKernel's client table is full. Use the Setup utility to specify a higher value for the Number of Remote Sessions configuration option.

• An application that calls the MicroKernel can return this status code for the following reasons:
  • Not all of the clients have been properly reset.
  • You loaded the MicroKernel with a value that is too small for its Active Clients setting. Use the Setup utility to increase the Active Clients configuration option.
  • You are using a limited user count version of the MicroKernel, and it has reached the maximum number of users.
  • The DBNAMES.CFG file contains a named database definition specifying a data location on a different server.

• In the Windows environment, the v6.15 and later MicroKernel returns this status code if you try to run a Btrieve-based application, but the client table is full. Use the Setup utility to specify a higher value for the Active Clients configuration option. Refer to the Pervasive.SQL User's Guide for information on the Active Clients option.

• You attempted to connect to a Btrieve v6.10 server using a Win32 Btrieve v7.0 requester. This combination is not compatible and is therefore prevented by design.

97: The data buffer is too small.

The application either tried to read or write a record that is longer than the current allowed settings for the MicroKernel or the Btrieve Requester, as follows:

• For an Update, Insert, or Create operation, the application receives this status code if the data buffer length it specifies for the record exceeds the message buffer length.

• For a Get, Step, or Stat operation, the application receives this status code if the message buffer is shorter than the length of the data the MicroKernel would return, regardless of the data buffer length specified in the application.

• For a Get Chunk or Update Chunk operation, the total size of the retrieved or updated chunk exceeds the message buffer length.

  For information about configuring the message buffer size, refer to the Pervasive.SQL User's Guide.

  To avoid receiving this status code, perform one of the following steps:

• Increase the size of the message buffer by using the Setup utility to specify a higher value for the Communications Buffer Size option.
  • For local files, the setting is MicroKernel Database Engine/Memory Resources/Communications Buffer Size.
  • For remote files, the setting is Btrieve Communications Manager/Server Communications Configuration/Communications Buffer Size.

• DOS Requesters only: Reload the Btrieve Requester and specify a higher value for the message buffer size. This is done using the /D parameter which is documented in Getting Started With Pervasive.SQL .

• For Windows NT servers, verify that the Maximum Packet Size registry setting is 576 decimal or 240h. The path to the MaxPktSize registry setting is HKEY_LOCAL_MACHINE\System\currentControlSet\
  Services\NwInkIPX\NetConfig\MaxPktSize.

98: The MicroKernel detected an internal transaction error.

This status code is obsolete in MicroKernel versions 6.0 and later.

A NetWare-based MicroKernel detected an error while executing the operation on a NetWare Transaction Tracking System (TTS) file. The application can perform only an Abort Transaction operation at this point.

99: The Btrieve Requester is unable to access the NetWare Runtime server.

The Btrieve Requester returns this status code when you enable NetWare Runtime server support and the Requester either detects no existing connection or cannot find a valid login username. SUPERVISOR and ADMIN are not valid usernames, even if supplied with the correct password. If the Requester cannot find a login username other than SUPERVISOR or ADMIN, there is no valid name to pass.

This error is also returned if you try to access a server with the NetWare Runtime server support disabled and you do not have an existing connection to that server.

100: No cache buffers are available.

This status code, returned by v6.0 and later MicroKernels, indicates that the MicroKernel has used all the cache buffers it allocated at load time. Use the Setup utility to increase the value for the Cache Allocation configuration option.

101: Insufficient operating system memory is available.

This status code, returned by v6.0 and later client/server MicroKernels, indicates that there is not enough operating system memory available to perform the requested operation. To fix this problem, perform one or more of the following:

• Use the Setup utility to decrease the value for the Cache Allocation configuration option.

• Add memory to the server.

  For more information about the configuration options, see Status Code "1002: A memory allocation error occurred." , a similar status code that the Windows-based MicroKernel returns in the same situation.

102: Insufficient stack space is available.

This status code, returned as a run-time error by v6.0 and later MicroKernels, indicates that the MicroKernel has run out of stack space. To increase the amount of stack space available to your application, relink the application, setting the stack size to a higher value. The MicroKernel returns this status code only to Windows-based applications that call WBTRCALL.DLL, or applications that call the Btrieve interface on the local server.

103: The chunk offset is too big.

The MicroKernel returns this status code in one of the following situations:

• A Get Direct/Chunk operation specified an offset beyond the end of the record, either explicitly or using the next-in-record bias to the subfunction value. Unless the MicroKernel returns this status code while processing the first chunk, the operation was partially successful. Check the data buffer length parameter immediately after the call to see how much data was retrieved (and therefore how many chunks).

• An Update Chunk operation specified an offset that is more than one byte beyond the end of the record. This status code indicates that the MicroKernel has made no changes to the record.

• An Update Chunk operation with an Append subfunction causes a record length to exceed its operating system file size limit. The MicroKernel has made no changes to the record.

104: The MicroKernel does not recognize the locale.

In v6.0 or later MicroKernels, the Create or Create Index operation returns this status code to indicate that the operating system was not able to return a collation table for the country ID and code page specified. Ensure that the application specified the locale's country ID and code page correctly and that the operating system is configured to support the country ID and code page.

105: The file cannot be created with Variable-tail Allocation Tables (VATs).

Version 6.0 and later MicroKernels return this status code when an application tries to create a file with Variable-tail Allocation Tables (VATs) but without variable-length records (a precondition for files to use VATs). This status code applies to key-only files as well as to regular data files.

106: The MicroKernel cannot perform a Get Next Chunk operation.

Version 6.0 and later MicroKernels return this status code when an application calls the Get Direct/Chunk operation to retrieve a chunk from a record and uses the next-in-record bias on the descriptor subfunction, but after the application establishes its positioning in the record (and prior to this call), the target record is deleted.

107: The application attempted to perform a chunk operation on a pre-v6.0 file.

Version 6.0 and later MicroKernels return this status code when an application tries to use either a Get Direct/Chunk operation or an Update Chunk operation on a file in pre-v6.0 format.

109: An unknown error was encountered either creating or accessing a semaphore.

Windows NT workstation MicroKernels return this status code when trying to perform an operation using incompatible versions of the DLLs. Shut down the MicroKernel and make sure that you are using the most recent versions of the DLLs.

110: The MicroKernel cannot access the archival logging configuration file.

The archival logging configuration file (BLOG.CFG) contains entries for the data files on the drive for which you want to perform archival logging. The MicroKernel returns this status code for the following reasons:

• The MicroKernel cannot find the BLOG.CFG file. Ensure that the file is in the \BLOG directory in a real root directory of the physical drive that contains data files you want to log. (That is, do not use a mapped root directory.) If your files are on multiple volumes, you must create a \BLOG directory on each volume.

• The MicroKernel cannot open the BLOG.CFG file. Either the file is locked or it does not exist.

• The MicroKernel cannot read the BLOG.CFG file. Either the file does not use the correct format or it is corrupt. Refer to the Pervasive.SQL User's Guide for information about the format of the BLOG.CFG file.

111: The specified filename was not found in the archival logging configuration file.

The MicroKernel cannot find the specified file in the BLOG.CFG file. The file must be specified in the BLOG.CFG file on the same physical drive.

112: The specified file is in use by another client.

Before the MicroKernel can perform a roll forward, the file must be in the same state it was in when it was last backed up. If another client changes the file, you must restore the file again before rolling forward.

113: The MicroKernel cannot find the archival log for the specified file.

The MicroKernel cannot find the archival log file associated with the specified file. By default, the MicroKernel names the archival log file the same as the logged file, but with a .LOG extension. However, you can specify a different filename for the archival log file in the BLOG.CFG file. Ensure that the BLOG.CFG file indicates the correct filename for the archival log and ensure that the archival log file exists.

114: The archival log for the specified file is invalid.

The archival log associated with the specified file is not a valid archival log file. By default, the MicroKernel names the archival log file the same as the logged file, but with a .LOG extension. However, you can specify a different filename for the archival log file in the BLOG.CFG file. Ensure that the BLOG.CFG file indicates the correct filename for the archival log and ensure that the archival log file exists.

115: The MicroKernel cannot access the archival logging dump file.

The MicroKernel cannot access the archival logging dump file for one of the following reasons:

• The filename indicated for dumping entries in an archival log is not a valid filename. Be sure this filename does not contain a volume specification. The dump file is created on the same volume as the log file.

• The caller does not have access rights to the dump file.

• The MicroKernel cannot open the file because another user has opened the file using an exclusive operating system lock.

116: The file is owned by another Microkernel engine acting as a Gateway.

130: The MicroKernel ran out of system locks.

This status code is obsolete in MicroKernel versions 6.15 and later.

This status code can indicate a temporary condition in which no system locks are currently available. The following are example cases:

• A single client is performing a very large transaction, in which thousands of records are being modified.

• Many clients are performing large transactions concurrently.

  A client can receive this status code whether or not it is in a transaction. In some cases, a client can simply retry the failed operation. If other clients have released system locks in the interim, the retried operation may succeed. If a client in a transaction receives this status code, end or abort the transaction. If the transaction is very large, consider breaking it into multiple, smaller transactions. You can also use the Setup utility to lower the number of system locks devoted to explicit locking. To do so, lower the values assigned to the Number of Locks and/or Number of Sessions configuration options.

132: The file has reached its size limit.

The MicroKernel returns this status code in one of the following situations:

• An operation attempted to allocate more than 16,777,216 pages to a data file.

• A data file has remained in continuous operation for a lengthy period of time, causing its delta file to exceed the operating system limit.

• A pre-v6.15 data file has reached the operating system file size limit.

133: More than 5 concurrent users attempted to access the same data file.

In the Pervasive.SQL Developer Kit for a workstation environment, you attempted to access a data file with more than five MicroKernels at the same time. The Pervasive.SQL Developer Kit for workstation environments limits the number of concurrent users of a file to five engines.

134: The MicroKernel cannot read the International Sorting Rule.

The MicroKernel returns this status code for one of the following reasons:

• The ISR is not found in the COLLATE.CFG file.

• The COLLATE.CFG file is missing or corrupt.

• The MicroKernel cannot read the ISR from the COLLATE.CFG file.

135: The specified ISR table is corrupt or otherwise invalid.

The MicroKernel returns this status code when it has found a readable COLLATE.CFG file, but the specific International Sorting Rule table is invalid.

136: The MicroKernel cannot find the specified Alternate Collating Sequence in the file.

The MicroKernel returns this status code in the following situations:

• You tried to create an index that uses an ACS, but the MicroKernel cannot locate an ACS with the specified name in the file.

• You called a Step Next Extended, Get Next Extended, Step Previous Extended, or Get Previous Extended operation and specified an ACS name, but the MicroKernel cannot locate an ACS with the specified name in the file.

138: The NULL indicator position is invalid.

• In order to ensure accessibility to your data from all of the Pervasive.SQL access methods, the NULL indicator segment (NIS) must appear immediately before the data segment that the NIS indicates. Otherwise, status 138 is returned.

• A NIS cannot be indicated by another NIS, otherwise, a status 138 is returned.

139: The MicroKernel has detected an unacceptable value in the key number.

Certain Btrieve operations either use, or reserve the use of, the key number parameter as a subfunction number, rather than as a means to specify a file's index to be used with the operation (as is done, for example, in the Get Equal operation). This status code is returned if an application does not specify a valid subfunction number (via the key number parameter) to one of these operations. For information about acceptable values for the operation's key number parameter, consult the section in the Btrieve Programmer's Guide that documents the operation that returned this status code.

140: The savepoint ID is invalid.

The application supplied an invalid savepoint ID in a nested transaction operation. Ensure that you specify valid savepoint ID's.

143: The MicroKernel cannot allow unauthorized access to files in a secure MKDE database.

You attempted to open a data file bound to a the MKDE database that has security enabled. The MicroKernel does not allow access to such files, except through the MKDE.

The MicroKernel also returns this status code if you are not using the MKDE and all of the following are true:

• You attempt to create a file with the Replace option.

• A bound MKDE data file with the same name and location already exists.

• The database to which the existing file is bound has security enabled.

147: The log segment is missing.

The MicroKernel cannot find a log segment that is necessary for rolling at least one file forward.

148: A roll forward error occurred.

The MicroKernel encountered an error while rolling a file forward. Depending on the operating system, the MicroKernel reports an error message as follows:

• The NetWare MicroKernel displays the message on the server's system console and writes the message to the Pervasive Event Log (PVSW.LOG), which resides in SYS:\SYSTEM.

• The Windows 95 and Windows NT workstation MicroKernel displays the message in the console message window and writes the message to the Pervasive Event Log (PVSW.LOG), which is located in the WINDOWS\SYSTEM or WINNT\SYSTEM32 directory.

• The Windows NT server MicroKernel does not display a message, but writes the message to the Pervasive Event Log (PVSW.LOG) in the WINNT\SYSTEM32 directory.

151: The nesting level is too deep.

You have exceeded the number of nesting levels that the MicroKernel allows. The MicroKernel's nesting level limit is 4,095. Specify fewer nesting levels. If you are using the MKDE and you specified fewer than 4,095 nesting levels, you may have specified more nesting levels than your system memory can hold.

161: The maximum number of user count licences has been reached.

You attempted to open another session when you were at the limit of your user count licence. Either close a session or upgrade your user count. For more information about purchasing and installing additive user counts, refer to Getting Started With Pervasive.SQL . You can use the Monitor utility to determine which users currently have connections to Pervasive.SQL. For information about the Monitor utility, refer to the Pervasive.SQL User's Guide.

162: The client table is full. Try increasing the number of Active Clients in the MicroKernel Database Engine System Resource setting.

You receive this status code when your setting for Active Clients in the Configuration utility is set too low, causing Pervasive.SQL to exhaust its client table space.

1. Click Start, point to Programs, then to Pervasive SQL 7.5 .

2. Select Configuration (Setup) from the list of programs.

3. If you are running Configuration from a client, click Connect and type the name of the server on which Pervasive.SQL is installed.

4. Select MicroKernel Database Engine from the list of components.

5. Select System Resources/Directories from the list of categories for the MicroKernel Database Engine.

6. Select the Active Clients setting.

7. Increase the value to the number of clients that access the server engine at any one time.

   The name you specified for a new index already exists as an index name or column name in the dictionary. Specify a unique name for the index.

163: The NULL indicator cannot be the last segment.

The NULL indicator segment (NIS) should not be the last segment of the key descriptor. Otherwise, a status 163 is returned.