Status Codes and Messages

disclaimer

PERVASIVE SOFTWARE INC. LICENSES THE SOFTWARE AND DOCUMENTATION PRODUCT TO YOU OR YOUR COMPANY SOLELY ON AN "AS IS" BASIS AND SOLELY IN ACCORDANCE WITH THE TERMS AND CONDITIONS OF THE ACCOMPANYING LICENSE AGREEMENT. PERVASIVE SOFTWARE INC. MAKES NO OTHER WARRANTIES WHATSOEVER, EITHER EXPRESS OR IMPLIED, REGARDING THE SOFTWARE OR THE CONTENT OF THE DOCUMENTATION; PERVASIVE SOFTWARE INC. HEREBY EXPRESSLY STATES AND YOU OR YOUR COMPANY ACKNOWLEDGES THAT PERVASIVE SOFTWARE INC. DOES NOT MAKE ANY WARRANTIES, INCLUDING, FOR EXAMPLE, WITH RESPECT TO MERCHANTABILITY, TITLE, OR FITNESS FOR ANY PARTICULAR PURPOSE OR ARISING FROM COURSE OF DEALING OR USAGE OF TRADE, AMONG OTHERS. Btrieve and XQL are registered trademarks of Pervasive Software Inc. Btrieve Pro, Built on Btrieve, Built on Scalable SQL, Client/Server in a Box, DDF Ease InstallScout, MicroKernel Database Engine, Pervasive.SQL, Pervasive.SQL 2000, Scalable SQL, Smart Naming, SmartScout, Smart Components, Smart Component Management, Navigational Client/Server, MicroKernel Database Architecture,and Xtrieve PLUS are trademarks of Pervasive Software Inc. Microsoft, MS-DOS, Windows, Windows NT, Win32, Win32s, and Visual Basic are registered trademarks of Microsoft Corporation. Windows 95 is a trademark of Microsoft Corporation. NetWare and Novell are registered trademarks of Novell, Inc. NetWare Loadable Module, NLM, Novell DOS, Transaction Tracking System, and TTS are trademarks of Novell, Inc. All company and product names are the trademarks or registered trademarks of their respective companies.

trademarks

Copyright 1999 Pervasive Software Inc. All rights reserved. Reproduction, photocopying, or transmittal of this publication, or portions of this publication, is prohibited without the express prior written consent of the publisher, unless such reproduction, photocopying, or transmittal is part of a Derivative Software Product as defined in the licenses granted in conjunction with the purchase of this publication and associated software. This product includes software developed by Powerdog Industries. 1994 Powerdog Industries. All rights reserved. The ODBC Driver Manager for NetWare (ODBC.NLM) included in this product is based upon the GNU iODBC software Copyright (C) 1995 by Ke Jin <[email protected]> and was modified by Simba Technologies Incorporated on June 1999. This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. A copy of the GNU Lesser General Public License is included in your installation of Pervasive.SQL 2000 at \PVSW\DOC\LESSER.HTM. If you cannot find this license, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA. You may contact Pervasive Software, Inc. using the contact information on the back cover of this manual.

Pervasive Software Inc. 12365 Riata Trace Parkway, Building II Austin, Texas 78727 USA

Status Codes and Messages June 1999 Part Number 100-003674-001

Contents
About This Manual . . . . . . . . . . . . . . . . . . . . . . . . .
Who Should Read This Manual? . . . . . . . . . . . . . . . . . . . . . . . Manual Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

v
vi vii viii

Status Codes . . . . . . . . . . . . . . . . . . . . . . . . . .
-5040 to -1000 -199 to -100 . . 0 . . . . . . . 1 to 199 . . . . 1000 to 1999 . 2000 to 2099 . 2300 to 2399 . 2900 to 2999 . 3000 to 3099 . 3100 to 3199 . 7000 to 7099 . 8000 to 8499 . 8500 to 8589 . 8590 to 8599 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-1
1-3 1-9 1-15 1-16 1-62 1-67 1-69 1-74 1-81 1-88 1-93 1-100 1-105 1-108

Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(No prefix). . BDROUTER BREQUEST. BREQUTIL . BROUTER . BSPXCOM . BTCPCOM . BUTIL . . . . MKDE . . . . NWBSRVCM UCINIT . . . UCMGR. . . UCUTIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-1
2-3 2-6 2-8 2-11 2-12 2-13 2-16 2-20 2-29 2-53 2-55 2-57 2-65

Contents iii

iv Status Codes and Messages

About This Manual

This manual describes the status codes and messages you may encounter while using components of Pervasive.SQL 2000. An explanation or corrective action accompanies each message or code. The status codes and messages in this manual are not specific to any one platform or product. This manual may refer to utilities, products, or platforms that are not part of your product distribution. Pervasive Software would appreciate your comments and suggestions about this manual. As a user of our documentation, you are in a unique position to provide ideas that can have a direct impact on future releases of this and other manuals. To give us any comments or suggestions, simply send e-mail to [email protected].

About This Manual v

Who Should Read This Manual?

This manual provides information for developers, testers, and support personnel who install and run Pervasive.SQL server and workstation products. Status codes may be displayed during product installation, while using the utilities, or while using an application.

vi Status Codes and Messages

Manual Organization
The following list briefly describes each chapter in the manual:

Chapter 1Status Codes This chapter lists and explains each status code you may receive. A brief description follows each code. The status codes are listed in numeric order. Some status codes listed in this chapter refer to engines and utilities for environments other than your own. Status codes are returned by API calls.

Chapter 2Messages This chapter lists and explains the numbered and non-numbered text message you may receive. The messages are categorized by the application or component that generates them. Some messages listed in this chapter refer to engines and utilities for environments other than your own.

This manual also includes an index.

About This Manual vii

Conventions
Unless otherwise noted, command syntax, code, and examples use the following conventions: CASE Commands and reserved words typically appear in uppercase letters. Unless the manual states otherwise, you can enter these items using uppercase, lowercase, or both. For example, you can type MYPROG, myprog, or MYprog. Words appearing in bold include the following: menu names, dialog box names, commands, options, buttons, statements, etc. Monospaced font is reserved for words you enter, such as command syntax. Square brackets enclose optional information, as in [log_name]. If information is not enclosed in square brackets, it is required. A vertical bar indicates a choice of information to enter, as in [file name | @file name]. Angle brackets enclose multiple choices for a required item, as in /D=<5|6|7>. Words appearing in italics are variables that you must replace with appropriate values, as in file name. An ellipsis following information indicates you can repeat the information more than one time, as in [parameter ...]. The symbol ::= means one item is defined in terms of another. For example, a::=b means the item a is defined in terms of b.

Bold

Monospaced font [ ]

| < > variable ... ::=

viii Status Codes and Messages

chapter

Status Codes
This chapter describes the status codes and messages generated by any of the components of Pervasive.SQL. Status codes are not the same as numbered messages (see Chapter 2, Messages); messages are returned to end users by utilities or specific components and generally begin with a prefix and a number. For example: MKDE16: There is insufficient memory to load the MicroKernel Database Engine. Status codes are returned to an application making a Pervasive.SQL interface call. The application determines whether or not to display the status code to the user. Applications will often display status codes in addition to helpful messages about a problem that has occurred, but the application developer determines this. Many utilities provided with Pervasive.SQL use transactional and relational access interfaces, and they may therefore return status codes as well as utility-specific messages. Some messages include references to status codes.

Status Codes 1-1

The status codes appear in numeric order. Table 1-1 lists the numeric ranges for each type of code. Table 1-1 Status Code Ranges
Range -5040 to -1000 199 to 100 0 1 to 199 1000 to 1999 2000 to 2099 2300 to 2399 2900 to 2999 3000 to 3099 3100 to 3199 7000 to 7099 8000 to 8499 8500 to 8589 8590 to 8599 Type of Code SQL Relational Database Engine Status Codes Informative Status Codes Successful Interface Completion Status Code MicroKernel Database Engine Status Codes MicroKernel Status Codes for Windows and DOS Workstations Btrieve Requester Status Codes Named Database Status Codes Inscribe Status Codes MicroKernel Router Status Codes Network Services Layer Status Codes User Count Manager Status Codes Component Management Status Codes ECAS Interface Status Codes W3DBSMGR Status Codes

Note This chapter may refer to utilities, products, or platforms that are not part of your product distribution.

1-2 Status Codes and Messages

-5040 to -1000
SQL Relational Database Engine Status Codes
The following table lists status codes returned by the SQL Relational Database Engine (SRDE).

Table A-2

Status Codes Returned by SQL Relational Database Engine

Status Code -1001 -1002 -1003 -1004 -1006 -1010 -1011 -1020 -1021 -1022 -1023 -1024 -1025 -1026 -1027 -1028 -1029 Description API not supported Invalid name Invalid API parameter Column is NULL-valued Buf too short, data truncated Invalid database id Out of memory No more file handles Disk not ready Disk IO error Invalid path Sharing violation File locking violation Record length exceeds max Database limit reached This isn't a database TamInit not yet called

Status Codes 1-3

Status Code -1031 -1032 -1038 -1039 -1040 -1041 -1044 -1045 -1047 -1051 -1060 -1064 -1101 -1102 -1104 -1105 -1113 -1114 -1202 -1203 -1204 -1206 -1207 -1301 -1302

Description File locking unavailable File access denied Buffer is too small SeekLE or SeekGE didn't find exact match Too many columns defined All the keyset columns are null in the table Filename is invalid Invalid bookmark Data buffer doesn't match column size Index is in use Can not append long value Can not build key for this sort order Can not begin session Write lock failed due to outstanding write lock Invalid session handle Commit lock failed due to outstanding read lock Too many active sessions Invalid session option Database in use, can't detach No such database Invalid database name Non-db file or corrupted db Database exclusively locked open an empty table Table is exclusively locked

1-4 Status Codes and Messages

Status Code -1303 -1304 -1305 -1309 -1310 -1311 -1402 -1403 -1404 -1501 -1504 -1505 -1506 -1507 -1508 -1511 -1512 -1513 -1514 -1515 -1516 -1517 -1601 -1603 -1605

Description Table already exists Table is in use, cannot lock No such table or object No DDLs w/o exclusive lock Invalid table id Can not open any more tables Primary index already defined Index is already defined No such index Column value is long Null not valid Column indexed, cannot delete Field length is > maximum No such column Field is already defined Invalid column data type Max length too big, truncated Can not index Bit, LongText, LongBinary No non-NULL tagged fields Invalid w/o a current index The key is completely made Column Id incorrect The key was not found Currency not on a record Illegal duplicate key

Status Codes 1-5

Status Code -1608 -1609 -1612 -1613 -1804 -1805 -1806 -1807 -1808 -1809 -1811 -1901 -1902 -1903 -1905 -1907 -2001 -2002 -2003 -2004 -2065 -3012 -3600 -4000 -4001

Description No call to DrmMakeKey No call to DrmInitUpdate References to key exist No referenced key exists Database file can't be opened Too many open databases Db file could not be closed Too many files open No space left on disk Permission denied File not found Failed sysdb on beginsession Invalid logon at beginsession Invalid account name Invalid password Access denied Filter not supported Push-down join was discarded Push-down filter was discarded Push-down filter accepted, keep index optimization No available buffers; or, queue is full Bin file open Cursor wrapped during fast find Table invalid format Too few columns

1-6 Status Codes and Messages

Status Code -4002 -4003 -4004 -4005 -4006 -4007 -4008 -4009 -4010 -4011 -4099 -4106 -4107 -4108 -4109 -4110 -4111 -4112 -4113

Description Invalid ODBC ini entry File open error File read error Invalid schema ini entry Index file open error Tag name error Create index error Invalid DB list Invalid argument Bin file open error Sendsize too small Comm buffer too small More data Invalid IDX Invalid direction The specified DSN does not exist. A DSN already exists with this name. Login failed. An error occurred during the initialization of the Windows Sockets Interface. The request to SQL Connection Manager to obtain the list of connected users failed. The request to SQL Connection Manager to kill the specified list of connections failed. UNDONE: Paradox: Report to Pervasive Record locked UNDONE: Paradox: data truncated

-4114

-4115

-5001 -5002 -5003

Status Codes 1-7

Status Code -5004 -5007 -5008 -5011 -5019 -5020 -5021 -5022 -5040

Description Table is not open Currency lost - must seek Invalid date I-ISAM: options were ignored translation failed... Invalid procedure name Invalid predicate name Invalid Code Page value Warning: too many columns

1-8 Status Codes and Messages

-199 to -100
Informative Status Codes
This section lists the informative status codes that the MKDE can return. The MKDE returns these codes as negative values.

101: The SET statement completed successfully.

The following statements return this status code when they execute successfully: SET BINARYNULL SET BLANK (in v3.01 mode) SET DATAPATH SET DEFAULT SET OPENMODE SET SECURITY SET DDPATH (in v3.01 mode) SET ISOLATION SET OWNER SET STRINGNULL SET CHAR SET DECIMALNULL SET MASK SET RANGE SET VALUES

the MKDE made the change you requested. However, if you issued a SET OPENMODE, SET OWNER, or SET ISOLATION statement during a transaction, the change does not take effect until you start a new transaction.

102: The INSERT statement completed successfully.

the MKDE added the specified rows to the table(s).

103: The UPDATE statement completed successfully.

the MKDE made the specified changes to the table(s).

104: The DELETE statement completed successfully.

the MKDE deleted the specified rows from the table(s).

Status Codes 1-9

105: The CREATE statement completed successfully.

The following statements return this status code when they execute successfully: CREATE DICTIONARY CREATE GROUP CREATE INDEX CREATE PROCEDURE If you issued a CREATE DICTIONARY statement, the MKDE successfully created the X$File, X$Index, and X$Field system tables. Otherwise, the MKDE successfully added the group, index, stored procedure, table, trigger, or view to the data dictionary. CREATE TABLE CREATE TRIGGER CREATE VIEW

106: The ALTER TABLE statement completed successfully.

the MKDE successfully made the specified change to the tables dictionary definition. If you altered a column (including a primary key or foreign key) without specifying the IN DICTIONARY keyword, the MKDE also changed the data file.

-107: The DROP statement completed successfully.

The following statements return this status code when they execute successfully: DROP DICTIONARY DROP GROUP DROP INDEX DROP PROCEDURE If you specified DROP DICTIONARY, the MKDE deleted the dictionary files and all associated data files. Otherwise, the MKDE successfully removed the group, index, stored procedure, table, trigger, or view from the dictionary. (Dropping a table also deletes the data file for that table.) DROP TABLE DROP TRIGGER DROP VIEW

1-10 Status Codes and Messages

108: The statement contains unresolved substitution variables and cannot be executed.
The current SQL statement contains substitution variables; you cannot execute the statement until you supply values for each variable. If you are using an application that allows substitution variables, refer to the documentation included with the application to determine how to use them with that application. If you are a developer using the MKDE interfaces to execute the statement, perform the following steps: 1. 2. Supply values for the variables using the XQLSubst function. Use the XQLExec function to verify the substitution values and, if the statement is not a SELECT statement, to execute the statement. If the statement is a SELECT statement, use the XQLFetch function to fetch the data.

3.

109: The view contains no more records.

You have reached either the beginning or the end of the view based on the current XQLFetch or xFetch option code.

110: The GRANT statement completed successfully.

the MKDE assigned the specified rights to the user or group.

111: The REVOKE statement completed successfully.

the MKDE revoked the specified rights from the user or group.

112: The START TRANSACTION statement completed successfully.

the MKDE has begun a transaction. All subsequent statements you issue are part of this transaction until you issue either a COMMIT WORK or a ROLLBACK WORK statement. For a savepoint, the SAVEPOINT label remains in effect until you explicitly release or roll back to that label, or until the end of any outer transaction within which the savepoint is nested.

Status Codes 1-11

113: The COMMIT WORK statement completed successfully.

the MKDE committed the changes made by your transaction to the data tables. You can no longer undo the changes with a ROLLBACK WORK statement. For a RELEASE SAVEPOINT statement, any changes made since the savepoint was declared can no longer be rolled back separately. They can only be committed or rolled back as part of an outer transaction.

114: The ROLLBACK WORK statement completed successfully.

the MKDE reversed the changes you made during the transaction except for any changes you made with operations that are not affected by transaction processing. If you perform one of the following operations within a transaction, the MKDE completes the operation, but you cannot roll back the results:

Operations that create or change dictionary definitions. Therefore, you cannot roll back the results of the following statements: ALTER TABLE, CREATE DICTIONARY, CREATE GROUP, CREATE INDEX, CREATE PROCEDURE, CREATE TABLE, CREATE TRIGGER, and CREATE VIEW. Operations that remove dictionary definitions. Therefore, you cannot roll back the results of the following statements: DROP DICTIONARY, DROP GROUP, DROP INDEX, DROP PROCEDURE, DROP TABLE, DROP TRIGGER, and DROP VIEW. Operations that grant or revoke security rights. Therefore, you cannot roll back the results of the following statements: GRANT (access rights), GRANT CREATETAB, GRANT LOGIN, REVOKE (access rights), REVOKE CREATETAB, and REVOKE LOGIN.

For a ROLLBACK TO SAVEPOINT statement, any changes made since the savepoint was declared are rolled back.

115: The MKDE successfully recalled the stored SQL statement.

This status code is obsolete in the MKDE versions 4.0 and later, except when using v3.01 Compatibility mode.

1-12 Status Codes and Messages

the MKDE successfully recalled the specified stored statement in the XQLCompile statement buffer, indicating that you can now execute the stored statement. Perform the following steps: 1. Execute the statement using the XQLExec function. the MKDE executes each statement within the stored statement until it finds either a SELECT statement or no more statements. 2. If the MKDE finds a SELECT statement, use the XQLFetch function to fetch the data. If you just retrieved data with XQLFetch, use XQLExec to continue executing the statements in the stored statement.

3.

116: The MKDE successfully executed the stored SQL statement.

This status code is obsolete in the MKDE versions 4.0 and later, except when using v3.01 Compatibility mode. In the MKDE v4.0 and later, stored procedures are used instead of stored statements. the MKDE executed the stored statement that you submitted for execution.

118: The DECLARE statement completed successfully.

The following statements return this status code when they execute successfully: DECLARE CURSOR DECLARE CONDITION If you issued a DECLARE statement, the MKDE successfully created the cursor, variable, or condition you defined. DECLARE VARIABLE

119: The SET assignment statement completed successfully.

The SET variable = expression statement returns this status code upon successful completion.

120: The OPEN statement completed successfully.

The OPEN CURSOR statement returns this status code upon successful completion. Status Codes 1-13

121: The CLOSE statement completed successfully.

The CLOSE CURSOR statement returns this status code upon successful completion.

122: The FETCH statement completed successfully.

The FETCH statement returns this status code upon successful completion.

123: The positioned UPDATE statement completed successfully.

The UPDATE [table_reference] SET set_clause WHERE CURRENT OF statement returns this status code upon successful completion.

124: The positioned DELETE statement completed successfully.

The DELETE [FROM table_reference] WHERE CURRENT OF cursor_name statement returns this status code upon successful completion.

125: The CALL stored procedure statement completed successfully.

The CALL statement returns this status code upon successful completion. This status code indicates the successful completion condition for the stored procedure.

1-14 Status Codes and Messages

0
Successful Interface Completion Status Code
Any interface call can return the following status code.

0: The interface completed successfully.

This status code is returned for any interface call that completes successfully. If an operation is not successful, a positive, nonzero status code is returned.

Status Codes 1-15

1 to 199
MicroKernel Database Engine Status Codes
This section describes status codes that the MicroKernel returns.

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 Users 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.

1-16 Status Codes and Messages

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.

Status Codes 1-17

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.

1-18 Status Codes and Messages

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 highit 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 Users 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.

Status Codes 1-19

This error code may also be returned when the file DBNames.CFG has been removed (for example, by Pervasive.SQLs 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 on-line 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 files integrity. Refer to the Pervasive.SQL Users 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.

1-20 Status Codes and Messages

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 Users 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. Status Codes 1-21

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 files 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 Users 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.

1-22 Status Codes and Messages

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.

Status Codes 1-23

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 variablelength 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 Users 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 files 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.

1-24 Status Codes and Messages

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 Max. No. Key Segments 512 8 1024 23 1536 24 2048 54 2560 54 3072 54 3584 54 4096 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. Status Codes 1-25

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 files 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 Users 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.

1-26 Status Codes and Messages

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 systems 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

Status Codes 1-27

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.

1-28 Status Codes and Messages

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:

Status Codes 1-29

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 files integrity cannot be ensured. Refer to the Pervasive.SQL Users 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 files 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 records 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 Users Guide for information about recovering damaged files.

1-30 Status Codes and Messages

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.

Status Codes 1-31

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 MicroKernels 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.

1-32 Status Codes and Messages

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.

Status Codes 1-33

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 Users 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.

1-34 Status Codes and Messages

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.

Status Codes 1-35

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.

1-36 Status Codes and Messages

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 Programmers 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 Programmers Guide for more information about RI.

Status Codes 1-37

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 Programmers 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 Users Guide for more information about recovering damaged files. Refer to the Pervasive.SQL Programmers 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 Programmers 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.

1-38 Status Codes and Messages

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 Programmers 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 Users Guide.

74: The MicroKernel aborted the transaction.

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

Status Codes 1-39

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 Programmers 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 serverbased 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.

1-40 Status Codes and Messages

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 files 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 multiplerecord lock or vice-versa. Status Codes 1-41

(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.)

1-42 Status Codes and Messages

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 nowait 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.

Status Codes 1-43

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 Users 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 Users 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 Programmers 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.

1-44 Status Codes and Messages

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 MicroKernels 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.

Status Codes 1-45

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 MicroKernels 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.

1-46 Status Codes and Messages

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 Requesters 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.

Status Codes 1-47

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 Users 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 multiplerecord 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.

1-48 Status Codes and Messages

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:

Status Codes 1-49

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 machines NET.CFG file and the servers 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.

1-50 Status Codes and Messages

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 MicroKernels 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 Users 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.

Status Codes 1-51

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 Users 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.

1-52 Status Codes and Messages

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. Status Codes 1-53

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 locales 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.

1-54 Status Codes and Messages

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 Users Guide for information about the format of the BLOG.CFG file.

Status Codes 1-55

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.

1-56 Status Codes and Messages

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.

Status Codes 1-57

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.

1-58 Status Codes and Messages

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 files 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 operations key number parameter, consult the section in the Btrieve Programmers 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 IDs.

143: The MicroKernel cannot allow unauthorized access to files in a secure the 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 the 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.

Status Codes 1-59

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 servers 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 MicroKernels 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 licenses has been reached.
You attempted to open another session when you were at the limit of your user count license. 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 Users Guide.

1-60 Status Codes and Messages

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.

To increase your Active Clients setting and solve Status 162:

1. 2. 3. Click Start, point to Programs, then to Pervasive SQL 7.5 . Select Configuration (Setup) from the list of programs. If you are running Configuration from a client, click Connect and type the name of the server on which Pervasive.SQL is installed. Select MicroKernel Database Engine from the list of components. Select System Resources/Directories from the list of categories for the MicroKernel Database Engine. Select the Active Clients setting. Increase the value to the number of clients that access the server engine at any one time.

4. 5.

6. 7.

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.

Status Codes 1-61

1000 to 1999
MicroKernel Status Codes for Windows and DOS Workstations
The workstation MicroKernel engine returns the following status codes in Windows and DOS environments.

1001: The lock parameter is out of range.

This status code is obsolete in MicroKernel versions 7.0 and later. Version 6.x MicroKernels return this status code when the value specified for the Number of Locks configuration option is out of range. Pre-v6.0 MicroKernels return this status code when the value specified for the Multiple Locks configuration option is out of range.

1002: A memory allocation error occurred.

Make sure that the workstation has enough memory to load all the programs it requires. For workstation versions of the MicroKernel, or client requesters, the insufficient memory may apply to conventional memory, expanded memory, or both.

1003: An invalid memory size parameter was specified.

Ensure that the value for the Cache Allocation configuration option is large enough to accommodate the required cache size. See the Pervasive.SQL Users Guide for more information.

1004: A page size error occurred.

This status code is obsolete in MicroKernel versions 7.0 and later. The value of the Page Size configuration option must be an even multiple of 512, and it must be between 512 and 4096, inclusive.

1-62 Status Codes and Messages

1005: The pre-image or lock file drive parameter is invalid.

You must specify a valid drive letter for the Pre-Image/Lock File Drive configuration option. Note Pre-image files are used only for pre-v6.0 files. Lock files are used only for v6.0 and later files opened in MEFS mode.

1006: The pre-image buffer parameter is out of range.

The Extended Operation Buffer Size configuration option must be between 0 and 64,000, inclusive. Both the v6.15 and v7.0 MicroKernel return Status 1006 for this reason The Pre-Image Buffer Size configuration option must be between 1 and 64, inclusive. The pre-image file is used in pre-v6.0 files and by v6.0 and later MicroKernels that are loaded with the Create Files in Pre-v6.x Format configuration option set to Yes.

1007: The files parameter is out of range.

For pre-v6.0 engines, the Open Files configuration option must be between 1 and 250, inclusive. For v6.0 and later engines, refer to the Pervasive.SQL Users Guide for valid range information.

1008: The initialization parameter is invalid.

The specified configuration options contain invalid or unidentifiable values.

1009: The transaction filename parameter is invalid.

This status code is obsolete in MicroKernel versions 7.0 and later. The filename specified for the Transaction filename configuration option is not valid. Ensure that the transaction filename is correct.

1010: An error occurred during the access of the transaction control file.
This status code is obsolete in MicroKernel versions 7.0 and later.

Status Codes 1-63

The MicroKernel is unable to create, open, read, or write to BTRIEVE.TRN or MKDE.TRN. Set the TRNFILE setting in the BTI.INI file to C:\.

1011: The compression buffer parameter is out of range.

The Compression Buffer Size configuration option is out of range. Refer to the Pervasive.SQL Users Guide for valid range information.

1012: Invalid /n: option.

This status code is obsolete in MicroKernel versions 6.0 and later. The Maximum Number Of Files In A Transaction configuration option is invalid. Valid values are 0 to 18; the default is 12.

1013: The task list is full.

In the Windows environment, this status code is returned if the task entry table is full. You can change the value for the Number of Tasks option using the Setup utility. For more information, refer to the Pervasive.SQL Users Guide. In the DOS environment, this status code is returned if the BREQUEST or BREQNT requesters are used without the /t parameter when BTRVID calls are present in the application. Reload the requester with a non-zero value for the /t parameter. For more information on the DOS Requester parameters, refer to Getting Started With Pervasive.SQL .

1015: One of the pointer parameters passed to the MicroKernel is invalid.

One of the pointer parameters passed into the MicroKernel is invalid. The MicroKernel checks for invalid pointers (and therefore only returns this status code) if you put the following line under the [BTRIEVE] heading in your initialization file: CHKPARMS=YES. By default, the MicroKernel performs no pointer checking.

1016: The MicroKernel is already initialized.

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

1-64 Status Codes and Messages

The MicroKernel returns this status code if you attempt to initialize the MicroKernel when it is already initialized. To reinitialize the MicroKernel, close all files, end/abort all transactions, and issue Btrieve operation 25, using the BTRV interface before calling the initialization function.

1017: The Btrieve Requester is unable to find the resource file WBTRVRES.DLL.
WBTRCALL.DLL returns this status code when it cannot find the resource file WBTRVRES.DLL. Place the WBTRVRES.DLL file in the same directory as the WBTRCALL.DLL file.

1018: The application attempted to call the MicroKernel from a Btrieve callback function.
The Windows MicroKernel does not allow a task to call the MicroKernel from a Btrieve callback function. You can only use the callback function with Btrieve for Windows.

1019: The MicroKernel cancelled the current Btrieve operation at the request of the applications Btrieve callback function.
The applications MicroKernel callback function returned a nonzero value, indicating that the application wants to terminate the current operation immediately. When the MicroKernel receives such a cancellation request, it attempts to terminate the currently executing operation and ceases to call the callback function for the duration of that operation. The MicroKernel may be unable to cancel the operation. However, if successful in doing so, the MicroKernel returns this status code.

1020: Btrieve Requester Interface communications error.

The MicroKernel loader and requester Interface returns this status code when it cannot send a message to the MicroKernel. This occurs when Windows is shutting down or when you terminate the MicroKernel using Ctrl+Alt+Delete. This is an informational status code only. No action is required. Your application continues the shutdown process. You also receive this status code when running an application that prevents Windows from processing messages.

Status Codes 1-65

1021: The MicroKernel failed to initialize.

The MicroKernel could not complete its initialization tasks. Check the MicroKernels console or error log for a message that specifies the problem that prevented the MicroKernel from initializing. The NetWare MicroKernel displays the message on the servers system console, and it also writes the message to the Pervasive Event Log (PVSW.LOG), which is located at SYS:SYSTEM. The Win32 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 C:\WINDOWS directory. The Windows NT server MicroKernel does not display a message, but writes the message in the Pervasive Event Log (PVSW.LOG), which is located in the C:\WINNT directory. Correct the problem, using the Setup utility if necessary, then retry the operation. If you are using a NetWare MicroKernel, you must first correct the problem, then unload and reload the MicroKernel before you can retry the operation.

1022: The MicroKernel is shutting down.

The operation cannot be completed because the MicroKernel is shutting down. To correct this problem, allow the engine to completely shut down, and then restart.

1-66 Status Codes and Messages

2000 to 2099
Btrieve Requester Status Codes
This section lists the status codes that the Btrieve Requesters generate.

2000: Internal error.

The Btrieve requester encountered an internal error. Check the Pervasive Event Log (PVSW.LOG) for more information.

2001: The memory allocation is insufficient.

In a DOS environment, reduce the value specified for the /D configuration option.

2003: The Requester does not allow local access to the specified file.
The application attempted to access a file stored on a local drive. The configuration of the MicroKernel installed at the client machine does not allow access to local files.

2004: SPX is not installed.

Install the NetWare SPX v2.0.

2005: An incorrect version of SPX is installed.

Install the NetWare SPX v2.0.

2006: There is 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 about NET.CFG.

Status Codes 1-67

2007: A pointer parameter is invalid.

One of the pointer parameters passed to the MicroKernel is invalid. Check the program to ensure that the pointer parameters are correct.

2008: Router cannot find engine.

The MicroKernel Router cannot communicate with the 6.15 engine. This status code is only used with the MKDE v4.0.100.

2009: Cannot load MicroKernel Router component.

The Btrieve requester cannot load the MicroKernel Router. This can occur if the DLL fails to load or fails to obtain the necessary DLL entry point.

2010: Thunk not possible - the Win32 MicroKernel router could not be found or is incompatible.
You receive this status code when the system is configured for thunking and the path is not accessible. This can occur if a necessary system file cannot be found (for example, kernel32.dll). It can also occur if the required system calls (for example, Win32s library) are not available.

2011: Btrieve requester resource DLL not loaded.

The resource DLL controls options that you can set with the Setup utility. You receive this status code when the resource DLL is either missing or incompatible with the current version of the requester. If this happens, the MicroKernel reverts to its default settings and continues to run.

2012: The Btrieve requester encountered an operating system error.

Check the Pervasive Event Log (PVSW.LOG) for more information.

1-68 Status Codes and Messages

2300 to 2399
Named Database Status Codes
This section lists the status codes you can receive when using the named database features of the Pervasive.SQL 2000 engine.

2300: No more database names are defined.

No more database names are defined. If the buffer is large enough to hold multiple database names, you might receive this status code and still have one or more database names returned. The application should check iBufLen to determine the number of names returned.

2301: The database name is invalid. 2302: Invalid buffer length. 2303: The database name must be unique; the specified database name already exists.
While creating a database, you specified a database name that already exists in the DBNAMES.CFG file. Specify a different, unique name for the database, or remove the existing database name first.

2304: The database type is invalid. 2305: The specified path for data dictionary or data file locations is invalid.
The path you specified for the bound, named database is invalid or the paths you specified for the data file locations are invalid. Ensure that the entered paths are either UNC paths or local paths (a local path for a NetWare server would be volume:path) and then retry the operation. Paths that contain mapped drive letters are not allowed.

Status Codes 1-69

2306: DBNAMES.CFG could not be updated.

The path you specified for the bound, named database is invalid or the paths you specified for the data file locations are invalid. Ensure that the specified paths are either UNC or local paths (a local path for a NetWare server would be volume:path) and then retry the operation. Paths that contain mapped drive letters are not allowed.

2307: Cannot open DBNAMES.CFG file.

If you are trying to access the workstation DBNAMES.CFG file to obtain a list of database names defined for the workstation engine, ensure that the DBNAMES.CFG file is in your Windows directory or in the directory specified by the Database Names Directory configuration option.

2308: The specified RI flag is invalid. 2309: The database is in use. 2312: The bound database cannot share table data files.
You cannot bind a data file referenced by a table in a bound, named database to another named database, or to another table in the same named database. For more information about bound databases, refer to the Pervasive.SQL Programmers Guide.

2313: The bound database cannot share data dictionary files.

The data dictionary files for a bound, named database cannot be referenced by another named database. For more information about bound databases, refer to the Pervasive.SQL Programmers Guide.

2314: Cannot create DBNAMES.CFG file. 2316: Cannot create DDF files for the bound database.
Pervasive.SQL cannot create the database files for the bound database. Ensure that the data dictionary files do not already exist at the specified location. Remove any existing data dictionary files before creating the bound, named database. For more information about bound databases, refer to the Pervasive.SQL Programmers Guide. 1-70 Status Codes and Messages

2324: Data dictionary files are not bound.

The data dictionary files for the specified named database are not bound, but should be. This normally indicates a situation in which the data dictionary files have been restored from a backup prior to the database being bound. Make sure that you restore your data dictionary from a backup which is consistent with the bound state of the databases. For more information about bound databases, refer to the Pervasive.SQL Programmers Guide.

2325: Data dictionary files are already bound.

The data dictionary files for the specified named database are already bound to another database. However, the other named database is not defined to the Scalable SQL engine that is trying to bind or unbind the database. Make sure that you only reference the data dictionary files for a bound database from one Scalable SQL engine. For more information about bound databases, refer to the Pervasive.SQL Programmers Guide.

2326: Data dictionary files are bound, but do not need to be bound.
This status code is returned when an unbound named database is checked. This does not indicate an invalid, or corrupted, named database, but does indicate an inconsistency between the named database definition and the actual state of the database. This status code often indicates a situation in which the data dictionary files have been restored from a backup that was made when the database was bound. Either restore the data dictionary from a backup that is consistent with the bound state of the database, or bind and then unbind the database. The unbinding of the database removes the binding information from the data dictionary files.

2329: Data file for a table is not bound.

The data file for a table in the database is not bound, but should be. This normally indicates a situation in which the data files for the database have been restored from a backup prior to the database being bound. Make sure that you restore your data from a backup that is consistent with the bound state of the database.

Status Codes 1-71

2330: Data file for a table is bound, but does not need to be bound.
This status code is returned when an unbound, named database is checked. This does not indicate an invalid, or corrupted, named database but does indicate an inconsistency between the named database definition and the actual state of the database. This status code often indicates a situation in which the data files for the database was bound. Either restore your data files from a backup that is consistent with the bound state of the database, or bind and then unbind the database. The unbinding of the database removes the binding information from the data files if the binding information is no longer needed.

2331: Not allowed to change data dictionary location and change name at the same time. 2332: Not allowed to bind database and change name at the same time. 2333: Not allowed to unbind database and change name at the same time. 2334: Not allowed to create data dictionary and change name at the same time. 2335: Not allowed to change data locations and change name at the same time. 2336: Not allowed to change data dictionary location and bind database at the same time. 2337: Not allowed to change data dictionary location and unbind database at the same time. 2338: Not allowed to change data dictionary location and create data dictionary at the same time. 2339: Not allowed to create data dictionary and bind database at the same time.

1-72 Status Codes and Messages

2340: Not allowed to create data dictionary and unbind database at the same time. 2341: Not allowed to bind database and change data locations at the same time. 2342: Not allowed to unbind database and change data locations at the same time. 2343: Named database general error.

Status Codes 1-73

2900 to 2999
Inscribe Status Codes
This section lists the status codes you can receive when using the Inscribe engine.

2900: The Inscribe Interpreter could not be initialized correctly.

The EPInit interface made a call to initialize the Inscribe Interpreter, but the initialization call was unsuccessful. Verify that the proper Inscribe Interpreter is installed on your system (WINSIA6.DLL for Windows 3.1, WINSIA32.DLL for Windows 95 and Windows NT, NWINSIA.NLM for NetWare). Also verify that you have sufficient available memory for Inscribe to run.

2901: The Inscribe Interpreter could not be terminated correctly.

The EPDeInit interface made a call to terminate the Inscribe Interpreter, but the call was unsuccessful. You can receive this status code when the Inscribe engine terminates the Inscribe Interpreter. This error should not affect active applications.

2902: An attempt to create an internal thread within the Inscribe Interpreter failed.
When EPCall executes procedures, internal resources (or threads) are allocated for those procedures. This status code indicates that an attempt to perform this allocation for a procedure failed. Verify that you have sufficient available memory for Inscribe to run.

2903: An attempt to kill an internal thread within the Inscribe Interpreter failed.
When EPCall executes procedures, internal resources (or threads) are allocated for those procedures. Once the procedures complete execution, those resources are freed, or killed, so other procedures can use them. This status code indicates that an attempt to perform this deallocation for a procedure failed. This error should not affect active applications; the effect of this status code is that a small amount of allocated memory is not freed. 1-74 Status Codes and Messages

2904: An attempt to load a module containing an Inscribe procedure failed.

You used the EPCall interface to execute a procedure, but when EPCall attempted to load the module containing the procedure, the load failed. Because you use the Inscribe Developer Kit to install the modules containing the procedures into a database, verify that you installed the modules correctly and have sufficient available memory to allow Inscribe to load new modules. This status code can also be returned if the procedure being loaded is unable to find a DLL or NLM referenced by the procedure.

2905: An attempt to unload a module containing an Inscribe procedure failed.

You used the EPCall interface to execute a procedure, but when EPCall attempted to unload a previously loaded module to make room for the module containing this procedure, the unload failed. Verify that you have enough memory for Inscribe to run; some memory is temporarily allocated to perform the unload operation.

2906: A request was made to execute an Inscribe procedure, but no procedure with the specified name was found.
You used the EPCall interface to execute a procedure, but when EPCall attempted to locate the procedure in the database specified in the EPLogin call, the search failed. If you receive this status code, check the following:

Because different procedures are associated with different databases, verify that the database name specified in EPLogin is correct. Verify that the procedure name passed as a parameter to EPCall is spelled correctly. Because you use the Inscribe Developer Kit to install the modules containing the procedures into a database, verify that you installed the modules correctly.

Status Codes 1-75

2907: The execution of an Inscribe procedure failed.

You used the EPCall interface to execute a procedure, but when EPCall executed it, the procedure did not terminate normally. Use the Inscribe Developer Kit to locate and correct any problems in the Inscribe procedure that could result in errors during execution. The Visual Basic-compatible language Inscribe uses supports the On Error statement, which you can also use to handle run-time errors such as an attempt to open a non-existent file.

2908: The type or number of the arguments passed to an Inscribe procedure does not match the type or number of the parameters defined for that procedure.
You used the EPCall interface to execute a procedure, but when EPCall compared the number and types of the arguments passed to EPCall with the number and types of the parameters defined for the procedure, it found one or more conflicts. Correct any discrepancies between the number and types of the parameters defined for the procedure and the arguments that you passed to EPCall.

2909: An error was encountered building the argument vector to be passed to an Inscribe procedure.
You used the EPCall interface to execute a procedure, but when EPCall processed the arguments passed in to EPCall, Inscribe attempted to convert the input information into an argument vector usable by the Inscribe procedure and then detected an error. Verify that the input argument information is in the correct format. For example, you must specify the DATE, TIME, and TIMESTAMP data types in a particular format when you pass them to EPCall. Also verify that you have sufficient available memory for Inscribe to run; Inscribe uses additional memory for some parameter types.

2910: An error was encountered extracting values from the argument vector returned by an Inscribe procedure.
You used the EPCall interface to execute a procedure, but when EPCall processed the argument vector returned to EPCall after the procedure completed, Inscribe attempted to process an output argument and detected an error. When a string argument is returned from an Inscribe procedure, a buffer is provided by the function that called EPCall to store the string. Inscribe returns this status code when the buffer is too small to hold the string. Check all output string arguments and verify that sufficient space is provided to hold all output values. 1-76 Status Codes and Messages

2911: The Inscribe Interpreter did not load successfully.

Under Windows 3.1, Windows 95, Windows NT, or NetWare, the Inscribe Interface loads the Inscribe Interpreter to execute procedures. The Inscribe Interface failed to load the Inscribe Interpreter. Verify that you installed the proper Inscribe Interpreter module on your system and that you have sufficient available memory to run Inscribe. the MKDE also returns this status code if it is unable to load Inscribe. Verify that you installed the proper Inscribe components on your system and that the MicroKernels Enable External Procedures configuration option is set to On. For more information about configuring the MKDE, refer to the Pervasive.SQL Users Guide.

2912: The Inscribe Interface encountered an error setting the internal instance flags that specify execution characteristics for the Inscribe Interpreter.
The Inscribe Interface sets certain instance flags, such as flags for multithreading, to allow the Inscribe Interpreter to run correctly in a particular environment. Inscribe returns this status code when an attempt to set these instance flags fails. If you receive this status code, the Inscribe Interpreter (WINSIA32.DLL, WINSIA16.DLL, or NWINSIA.NLM) may be corrupt. Try reinstalling it.

2913: The amount of available memory is less than that needed for Inscribe to run.
The operating system has insufficient memory for Inscribe to run. Terminate other applications to make additional memory available.

2915: The database specified as an argument to the EPLogin interface is not a valid database.
The string passed to EPLogin representing the database may be invalid. In Inscribe 1.0, if the string is valid, Inscribe was unable to access and read the databases EPMAP.TXT file to get information about the Inscribe procedures defined for that database. Verify that the database name is correct. If it is correct, verify that the Inscribe Developer Kit was used to create an EPMAP.DDF file for the database that contains information about the Inscribe procedures associated with that database.

Status Codes 1-77

2916: The Inscribe session ID is invalid.

The Inscribe session ID passed as an input argument to EPLogout or EPCall is not a valid Inscribe session ID. Verify that the Inscribe session ID that was returned as an output value from EPLogin is the same one that is being used as the input session ID to EPLogout and EPCall.

2917: The credential specified by the caller when Inscribe was initialized does not match the credential specified when Inscribe was terminated.
The Inscribe credential passed as an input argument to EPDeInit is not a valid Inscribe credential. Verify that the Inscribe credential that was specified as an input argument to EPInit is the same one that is used as the input argument to EPDeInit.

2918: An error was encountered deregistering a callback function in EPCallback, or an error was encountered in EPCall specifying a callback function for use by the Inscribe Interpreter.
If EPCallback returns this status code, then the callback function specified in the fCallback parameter does not match the currently registered callback. If EPCall returns this status code, then there was an error establishing this callback function as the one for the Inscribe Interpreter to use. For EPCallback, verify that the fCallback parameter contains the correct value. (Callbacks must be deregistered in the reverse order in which they were registered.) For EPCall, verify that the callback function specified in EPCallback is a valid pointer to a callback function.

2919: While logged in with the same Inscribe login ID, an attempt was made to execute an Inscribe procedure before a previous Inscribe procedure completed.
When logged in with the same Inscribe login ID, only one Inscribe procedure can be executed at a time so that callback functions can be handled correctly. Typically, Inscribe only returns this status code in multi-threaded applications. If you need multiple threads to concurrently execute Inscribe procedures, then have each thread perform its own separate EPLogin call to get a unique login ID. Do not try to share the same login ID among multiple threads.

1-78 Status Codes and Messages

2920: An attempt was made to call an Inscribe Interface interface function, but Inscribe has been disabled in the users environment.
A call was made to the EPVersion interface to get version information for an Inscribe component, but an invalid value was passed in the flags argument. Verify that the value you set in the flags argument is correct.

2921: The Inscribe engine encountered an error reading an Inscribe module.

Inscribe modules are .SBX files, which you produce by compiling an Inscribe script using the SBL Developer Tools and then copy to a database directory. The Inscribe engine returns this status code when the engine is unable to read a module or the contents of a module are invalid. Verify that no other active applications (such as the 16- or 32-bit SBL Developer Tools) are accessing any Inscribe modules; such access may prevent the Inscribe engine from reading the modules. If no other applications are accessing any Inscribe modules, one or more of the modules may contain invalid data, caused by one of the following:

Disk errors. Presence of modules compiled with Inscribe v1.0. (Any modules created with Inscribe v1.0 are not compatible with Inscribe v2.0 and must be recompiled with Inscribe v2.0.) Another application that overwrote some of the modules.

Recreate the Inscribe modules by recompiling them in a SBL Developer Tool and copying them to the database directory.

2922: The Inscribe engine encountered a duplicate procedure name when processing an Inscribe module.
Inscribe modules are .SBX files, which you produce by compiling an Inscribe script using the SBL Developer Tools and then copy to a database directory. The procedure names within these modules must be unique so that Inscribe can uniquely determine which Inscribe procedure to invoke for a particular the MKDE external procedure name. Examine the Inscribe modules to find the duplicate names, change the names to avoid the conflict, then recompile the modules in a SBL Developer Tool and copy them to the database directory. Status Codes 1-79

Note The main procedure can appear in multiple modules without causing this status code, because main procedures are intended for debugging with the SBL Developer Tools and are ignored by the Inscribe engine. Similarly, private procedures that appear in multiple modules can have the same name, because private procedures are also ignored by the Inscribe engine.

1-80 Status Codes and Messages

3000 to 3099
MicroKernel Router Status Codes
This section lists the status codes you can receive from the MicroKernel router, which receives requests from the Btrieve requesters and routes them to the correct version of the MicroKernel.

3000: The MicroKernel router encountered a memory allocation error.

The MicroKernel router could not internally allocate memory. Check the Pervasive Event Log (PVSW.LOG) for more information.

3001: Local access is unavailable to the MicroKernel router.

A call to the MicroKernel failed. This is most likely the result of an incorrect configuration. For example, if the MicroKernel is unavailable because of configuration settings and the file to be opened is local, then the MicroKernel router returns this status code.

3002: The MicroKernel router resource DLL is unavailable.

The MicroKernel router returns this status code when its resource DLL is either missing or incompatible with the current version of the router. If this happens, the MicroKernel reverts to its default settings and continues to run. Check the Pervasive Event Log (PVSW.LOG) for more information.

3003: The MicroKernel router detected an incompatible network component.

The networking services component is not compatible with this version of the MicroKernel router. The most likely cause is that the Networking services DLL has been replaced by an older version. Check the Pervasive Event Log (PVSW.LOG) for more information.

Status Codes 1-81

3004: The MicroKernel is not responding to the MicroKernel router.

The MicroKernel is not responding to requests from the MicroKernel router. Verify that the MicroKernel is running.

3005: The MicroKernel router encountered an operating system error.

The MicroKernel router encountered an unexpected error from the operating system, such as a shared memory failure. Check the Pervasive Event Log (PVSW.LOG) for more information.

3006: The MicroKernel router detected an invalid session.

The session information contained in a position block is invalid. This status code occurs for one of the following reasons:

The application is trying to use a position block for a file that resides on an engine and for which the connection has been previously terminated via a B_STOP (25) or B_RESET (28) operation. The application is trying to use a position block for a file that resides on a remote server and that encountered an abnormal network error on a previous operation.

3008: Invalid configuration for MicroKernel router.

This status code results from an invalid configuration. For example, if the Local, Remote, and Thunk options have all been set to No, the router has no valid path to take. If this happens, set one of these options to Yes, depending on your setup.

3009: NETinterface.DLL is not loaded.

The MicroKernel router could not find NETAPI.DLL.

3010: NetWare API DLLs are not loaded.

The MicroKernel router could not find the NetWare API DLLs.

1-82 Status Codes and Messages

3011: Thunk not possible - the Win32 MicroKernel router could not be found or is incompatible.
This status code is only relevant to the Win16 MicroKernel router. You receive this status code when the Use Thunk option is set to Yes and the thunk path is not accessible. Possible causes include:

The Win32 MicroKernel Router DLL does not exist or is not compatible. The Win32s routines failed to initialize.

Check the Pervasive Event Log (PVSW.LOG) for more information.

3012: Local engine is not accessible to the MicroKernel router.

Access to the local engine is not possible because it is not loaded or could not be launched. You can receive this status code if you try to access a local file on a client and you do not have a MicroKernel workstation engine installed or if you try to access a local file on a server and the MicroKernel server engine is not running. If you have only a server engine installed and your Pervasive Event Log (PVSW.LOG) contains Status Code 3012 warning entries, perform the following steps:

To Turn Off Local Engine support:

1. 2. 3. 4. 5. 6. 7. Click Start, point to Programs, then to the Pervasive folder. Select Setup (Win32 or Win16). Select the MicroKernel router component. Select the Local setting and change it to Off. Select the MKDE Requester component. Select the Local Usage setting and change it to Off. Click Save and then Exit.

Status Codes 1-83

3013: The remote engine is inaccessible to the MicroKernel router because the networking component is not loaded.
Access to the remote engine is not possible because the MicroKernel router could not initialize the networking component. Possible causes include:

The Remote option is incorrectly set to No. The required networking component could not be found or is not compatible.

3014: The MicroKernel router cannot find an engine.

The MicroKernel router could not complete the operation because it did not find an engine (local or remote) that could process the operation. Possible causes include:

The target network operating system is not available. The target engine is not available. In a Windows 3.x environment, you are using a shared drive name that contains a space. To resolve the condition, remove the space from the shared drive name. For example, if you connect to a server named D Drive, change the share name to D_Drive.

3015: The MicroKernel router encountered an initialization error.

An unexpected error occurred during the initialization of the MicroKernel router. Check the Pervasive Event Log (PVSW.LOG) for more information.

3016: The MicroKernel router encountered an internal error.

The MicroKernel router encountered an internal error. Check the Pervasive Event Log (PVSW.LOG) for more information.

1-84 Status Codes and Messages

3017: Data buffer of the local engine is too small.

You receive this status code when the requester has more data to send the MicroKernel than the MicroKernels buffers can handle. This status code is only relevant to an engine running locally; it does not apply to client/server environments. Some possible solutions include:

Specify a higher value for the Communications buffer size parameter in the Setup utility. Use smaller buffers in Btrieve operations.

3018: The file is already closed.

You receive this status code when the MicroKernel router is shut down and is not accepting any more requests.

3019: The MicroKernel router encountered a semaphore error.

A semaphore error occurred while trying to establish contact with the local engine. Check the Pervasive Event Log (PVSW.LOG) for more information.

3020: An error occurred while loading the MicroKernel.

You receive this status code when an error occurs while loading the MicroKernel or when access to the server and client machines shared memory objects are unavailable. Check the Pervasive Event Log (PVSW.LOG) for more information.

3021: The MicroKernel router received a badly formatted data packet.

The MicroKernel router rejected the response from the engine because it was badly formatted. Check the Pervasive Event Log (PVSW.LOG) for more information.

Status Codes 1-85

3022: The MicroKernel router could not send the request to the remote engine because the specified data buffer length resulted in a data packet object that is too large.
A request to the MicroKernel router specified a data buffer length that resulted in a data packet size greater than 64 KB, which is the maximum. This can occur even if the data buffer length for the request is smaller than 64 KB because the MicroKernel router adds some packet overhead as it forms the data packet. Check the Pervasive Event Log (PVSW.LOG) for more information.

3023: The task table of the MicroKernel router is full.

An internal table used by the MicroKernel router to manage tasks is full. This error should only occur in Win16 environments and indicates that a large number of applications are using the Win16 MicroKernel router at the same time.

3025 : Cannot load IDS client requester.

The MicroKernel router could not load the IDS client requester. The IDS client requester is W3ICRxxx.DLL, where xxx is a revision number (100, 101, etc.). The IDS client requester needs to be located in a directory listed in your PERVASIVE_PATH or PATH environment variable.

3026 : Incompatible IDS client requester.

The MicroKernel router found an incompatible IDS client requester. The IDS client requester was found, but is a version that cannot be used by the MicroKernel router, or the file is corrupt.

3027 : Connection failure to IDS target server.

The MicroKernel router could not connect to the IDS target server. Be sure that IDS is running on the target server. If you are connecting to the IDS target by a host name, ensure that the name is spelled correctly and can be resolved to a TCP/IP address. If you are connecting by a TCP/IP dotted notation address, be sure that the address is correct and accessible from the client.You can use SmartScout as a diagnostic tool. 1-86 Status Codes and Messages

3028 : Login failure to IDS target server.

The MicroKernel router could not login to the IDS target server. Be sure that the user name, password, and database set name used are correct. Some applications may prompt for this information; others may require MicroKernel Router configuration parameters to be set. See the Pervasive.SQL User's Guide or the Getting Started with I*net Data Server for more information regarding MicroKernel Router configuration parameters.

3029 : IDS Not Allowed.

This code will be returned if the path indicates an IDS request and either: 1. 2. the key number on the open request indicates 'local only'; OR the config setting for 'Allow IDS' == 'No'.

3030 : Remote access not allowed.

This code is returned if the path is remote, the config setting for 'Local' == 'No', and either: 1. 2. the key number on the open request indicates 'local only'; OR the config setting for 'Requestor' == 'No'.

Status Codes 1-87

3100 to 3199
Network Services Layer Status Codes
The following status codes originate from the Pervasive Network Services Layer (PNSL).

3103: Server name not found by Pervasive Network Services Layer.

The search for a target server name was unable to resolve an address after searching NDS, bindery, named pipes, and DNS. Some possible causes include:

No common communication protocol is available between the server and the client. To check this, use the Setup utility to check the Supported Protocols setting of the requester (under Communications Requester section) and the server (under Btrieve Communications Manager and the MKDE Communications Manager sections). Ensure that there is a common protocol (either SPX or TCP/IP) between the server and the requester. For Windows NT: The MicroKernel engine not running. For NetWare:

The Server Addressing Protocol (SAP) filtered out the server name. SAP is used in NetWare 3.x and can be used in version 4.x. This type of filtering is common in WAN environments. NWCALLS.DLL and/or NWIPXSPX.DLL is missing when using the Win16 client. This is especially likely if the Win32 clients are functioning but the Win16 clients do not. These are NetWare system files that can be obtained from Novells web site (http://www.novell.com).

For NetWare using TCP/IP: The server name is not in DNS. For Windows NT Server: Named pipes are used in these two operating systems to resolve server names. The networking at the operating system level was unable to find the target named pipe.

Check the Pervasive Event Log (PVSW.LOG) for more information.

1-88 Status Codes and Messages

3104: The Pervasive Network Services Layer encountered a permission error.

This status code is relevant to Windows NT only. Permission to access the target named pipe is denied. If you receive this status code:

Verify that you have access to the inter process communication mechanism. Ensure that your passwords are identical if you have the same user name on two systems.

3105: No available transport protocol for the Pervasive Network Services Layer.
No transport protocol that is common to both the target server engine and clients is available. For example, Status Code 3105 could be caused by a client using SPX when the server engine only has TCP/IP available. To check this, use the Setup utility to examine the Supported Protocols setting of the client (under the Communications Requester section) and the Supported Protocols setting of the server (under the Btrieve Communications Manager and the MKDE Communications Manager sections). For more information on the Setup utility, refer to the Pervasive.SQL Users Guide.

3106: The Pervasive Network Services Layer encountered a connection failure.

The Pervasive Network Services Layer was able to establish a transport connection at the client side, but the connection attempt at the target side failed. Some possible causes are:

The Btrieve or the MKDE is not running on the server. The network is overloaded. The connection path is invalid.

Status Codes 1-89

You have more than one mapped drive to the same server. You are trying to access a Btrieve engine on a Windows NT server and the Accept Remote Requests setting of the Btrieve Communications Manager on that server is set to No. See the Pervasive.SQL Users Guide for more information.

Check the Pervasive Event Log (PVSW.LOG) for more information if you receive this status code.

3107: The Pervasive Network Services Layer is out of memory.

The Pervasive Network Services Layer has insufficient memory to continue.

3108: The Pervasive Network Services Layer detected an invalid session.

The application attempted to use a network session that was not recognized by the Pervasive Network Services Layer. If the error persists, contact Pervasive Software Customer Support.

3110: The network layer is not connected.

The application attempted to use a network connection that was no longer active. This happens when the session with the Pervasive Network Services Layer is still valid, but was dropped by the network. Stop and restart the application.

3111: Failure during send to the target server.

The Pervasive Network Services Layer attempted to send an application request to the target server and encountered a network specific error from the target. Check the Pervasive Event Log (PVSW.LOG) for more information. You can receive this error when the server's Btrieve Communication Manager or the MKDE Communication Managers Number of Sessions setting is too low. To resolve this, increase the Number of Sessions setting for these two components using the Setup utility. Refer to the Pervasive.SQL Users Guide for more information on the Number of Sessions setting and the Configuration utility.

1-90 Status Codes and Messages

3112: Failure during receive from the target server.

The Pervasive Network Services Layer attempted to receive data from the target server and encountered a network specific error. Check the Pervasive Event Log (PVSW.LOG) for more information.

3114: The routing table of the Pervasive Network Services Layer is full.
The Pervasive Network Services Layers Server Routing Table is full. This table normally grows dynamically as needed. Verify that you are not in a low memory condition.

3115: Pervasive Network Services Layer encountered a transport failure.

The Pervasive Network Services Layer encountered a WinSock (Win32, Win16) error while creating the local transport endpoint on the client side. Check the Pervasive Event Log (PVSW.LOG) for more information.

3119: 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 Users Guide.

Status Codes 1-91

3125: The Pervasive Network Services Layer was unable to resolve the Novell Directory Services name into a NetWare server name.
The Pervasive Network Services Layer was unable to resolve the Novell Directory Services name into a NetWare server name. This occurs on Windows 95 workstations with the Microsoft Service for Novell Directory Services in cases where the system is unable to load the Windows 95 Requester support modules. Ensure that the Requester Win95 support modules are installed and available, and that NWCALLS.DLL is available on the Windows 95 workstation.

3126: The Pervasive Network Services Layer was unable to resolve the given filename into a valid path.
Check that the given filename is a valid file format.

3127 : Failure during send to the IDS target server.

Failure during send to the IDS target server. The IDS client requester attempted to send data to the IDS target server and encountered a TCP/IP specific error. Stop and restart the application. If the problem persists, consult your network administrator.

3128 : Failure during receive from the IDS target server.

Failure during receive from the IDS target server. The IDS client requester attempted to receive data from the IDS target server and encountered a TCP/IP specific error. Stop and restart the application. If the problem persists, consult your network administrator.

1-92 Status Codes and Messages

7000 to 7099
User Count Manager Status Codes
This section lists the status codes you can receive when using the User Count Manager.

7002: The key number is invalid.

For a description of this status code, refer to the message UCMGR301: The key number used for increasing the user count is invalid. .

7003: The User Count Manager cannot write to the key file.
For a description of this status code, refer to the message UCMGR405: Error writing to user count key file, (errno=nn). .

7004: The User Count Manager cannot write to the specified file.
For a description of this status code, refer to the message UCMGR406: Error writing to file, file = filename, (errno=nn). .

7005: The User Count Manager cannot read the key file.
For a description of this status code, refer to the message UCMGR408: Error reading from user count key file, (errno=nn). .

7006: The User Count Manager cannot read the specified file.
For a description of this status code, refer to the message UCMGR409: Error reading from file, file = filename, (errno=nn). .

7007: The User Count Manager encountered a premature end of file.

For a description of this status code, refer to the message UCMGR410: Unexpected end-of-file found, file = filename, (errno=nn). .

Status Codes 1-93

7008: The User Count Manager cannot open the specified file.
For a description of this status code, refer to the message UCMGR404: File open error, file = filename, (errno=nn). .

7009: The User Count Manager cannot modify the specified file.
For a description of this status code, refer to the message UCMGR403: File change mode error, file = filename, (errno=nn). .

7010: The User Count Manager cannot find the specified file.
For a description of this status code, refer to the message UCMGR402: Invalid file pathname = path, file = filename, (errno = nn). .

7011: You cannot increase the user count with the same key number twice.
For a description of this status code, refer to the message UCMGR305: Duplicate key number error. You cannot increase the user count with the same key twice. .

7012: The key files integrity has been compromised.

For a description of this status code, refer to the message UCMGR302: Invalid key file check sequence. The integrity of the user count key file has been compromised. .

7013: The key type is invalid.

For a description of this status code, refer to the message UCMGR303: Invalid key number (key number is of the wrong type). .

7014: The User Count Manager is already in use. Try again later.
For a description of this status code, refer to the message UCMGR501: The User Count Manager is busy. Only one instance of the User Count Manager can be in use at one time. .

1-94 Status Codes and Messages

7016: The User Count Manager cannot read the specified file; the file may be corrupt.
For a description of this status code, refer to the message UCMGR411: File seek error, file = filename, (errno=nn). .

7017 7023: The component serial numbers do not match.

For a description of this status code, refer to the UCMGR messages 310 through 316, beginning with UCMGR310: Serial number synchronization error. Unable to find valid stamp area. on page 2-58. 7017: UCMGR310: Serial number synchronization error. Unable to find valid stamp area. on page 2-58 7018: UCMGR311: Serial number synchronization error. Invalid stamp area read. on page 2-58 7019: UCMGR312: Serial number synchronization error. One or more stamp numbers read do not match. on page 2-58 7020: UCMGR313: Serial number synchronization error. Could not write stamp number to one of the files. Make sure the database engine is not loaded and that you have access rights to the files. on page 2-58 7021: UCMGR314: Serial number synchronization error. Files have not been stamped and the user count key file exists. on page 2-58 7022: UCMGR315: Serial number synchronization error. The key file stamp number does not match the stamp number in the other files. on page 2-59 7023: UCMGR316: Serial number synchronization error. Files have been stamped but the user count key file does not exist. If you have made a backup copy of your user count key file (<plat>UCMGR.SYS), please restore it to the database engine directory. on page 2-59

7026: The User Count Manager cannot find the diskette key file: UCMGR.KEY.
For a description of this status code, refer to the message UCMGR401: Cannot find diskette key file, file = filename, (errno = nn). .

Status Codes 1-95

7028: The diskette key has already been applied.

For a description of this status code, refer to the message UCMGR306: The diskette key has already been applied. You cannot increase the user count with the same diskette key twice. .

7029: The User Count Manager cannot read the diskette key file.
For a description of this status code, refer to the message UCMGR307: The diskette key file is invalid, file = filename, (errno=nn) .

7030: DOS partition services are not present.

This status code applies to the NetWare platform only. For a description of this status code, refer to the message UCMGR415: DOS Partition Services are not present. .

7031: The User Count Manager cannot copy the diskette key file.
This status code applies to the NetWare platform only. For a description of this status code, refer to the message UCMGR416: DOS Copy error. The User Count Manager cannot copy the diskette key file, (errno=nn). .

7032: The User Count Manager cannot open the diskette key file.
This status code applies to the NetWare platform only. For a description of this status code, refer to the message UCMGR417: DOS Open error. The User Count Manager cannot open the diskette key file, (errno=nn). .

7033: The User Count Manager cannot write to the diskette key file.
This status code applies to the NetWare platform only. For a description of this status code, refer to the message UCMGR418: DOS Write error. The User Count Manager cannot write to the diskette key file (errno=nn). .

7035-7038: The serial numbers do not match.

For a description of these status codes, refer to UCMGR messages 317 through 319, beginning on page -59. Messages 7035-7038 share the same error messages as 7017-7023. The difference is that 7035-7038 occur only during a user count migration (such as a migration from a Btrieve v6.15 user count). 1-96 Status Codes and Messages

7039: The User Count Manager cannot delete the specified file.
For a description of this status code, refer to the message UCMGR412: File delete error, file = filename, (errno=nn). .

7040: The User Count Manager cannot rename the specified file.
For a description of this status code, refer to the message UCMGR413: File rename error, file = filename, (errno=nn). .

7041: The User Count Manager is not initialized.

For a description of this status code, refer to the message UCMGR500: The User Count Manager is not initialized. Unload or stop your database engine and run the User Count Initialization utility (UCINIT.EXE, NTUCINIT.EXE, or NWUCINIT.NLM). .

7042: The User Count Manager cannot determine the platform.

For a description of this status code, refer to the message UCMGR502: The User Count Manager cannot determine the platform. .

7046: The User Count Manager cannot migrate Btrieve user count.
An invalid Btrieve database engine was specified for migrating the Btrieve user count. On NetWare, only Btrieve v6.15 and Btrieve v6.10 user count licenses can be migrated to the MKDE v4.0. On Windows NT, only Btrieve v6.15 user count licenses can be migrated to the MKDE v4.0.

7048: The operation is invalid for Btrieve v6.1x migration.

This status code has the same meaning as the message UCMGR321: You have previously migrated xx users and have tried to migrate xx users at this time. This is an invalid operation because the migrated user count is less than the previously migrated user count. .

7049: User count license is already unlimited for this product.

You receive this status code when you attempt to add a diskette-based license key on top of a product that already is licensed for unlimited users. Since you already have an unlimited license, you do not need to increase your user count. Status Codes 1-97

7050: Incorrect user count resource DLL.

You receive this status code when the user count manager loads the wrong message file. Update your resource DLL to the version specified by the message.

7051: Incorrect major version of user count resource DLL.

You receive this status code when the user count manager loads an older major version of the message file. Update your resource DLL to the version specified by the message.

7052: Incorrect minor version of user count resource DLL.

You receive this status code when the user count manager loads an older minor version of the message file. Update your resource DLL to the version specified by the message.

7053: Incorrect patch number for user count resource DLL.

You receive this status code when the user count manager loads an older patch level of the message file. Update your resource DLL to the path number specified by the message.

7054: License key does not match product version.

You receive this status code when you attempt to add a key for an older version of the product. Obtain a user license key for the current product level and try again.

7061: Your Pervasive Database engine expired on <date>. Please contact Pervasive Software for more information.
You receive this status code when your temporary user license for the database engine is expired. Contact Pervasive Software to obtain a permanent user license key.

1-98 Status Codes and Messages

7062: Your Pervasive Database engine will expire on <date> because you have a temporary license key.
You receive this message when you start the MicroKernel and you have a temporary license key. This is an informational message only that reminds you when your license will expire. Contact Pervasive Software to obtain a permanent license key.

7063: Your user count license limit has been reached.

The maximum allowed users for the database engine has been reached. Please contact Pervasive Software if you need additional users for your license. To check the current setting for maximum users, run the User Count Administrator: 1. 2. Click Start, Point to Programs and then to Pervasive SQL 7.5 . Select the User Count Administrator.

The User count Administrator displays the current maximum user licenses and allows you to add additional licenses. Refer to Getting Started With Pervasive.SQL for more information.

7064: The license you tried to remove does not exist.

You receive this status code when the User Count Manager receives a request to remove a license for a product code, and the license does not exist.

7065: The product for which you requested the user count license does not exist.
You receive this status code when the User Count Manager receives a request to display a user count license for a product code, and that product code does not exist. Consult Getting Started with Pervasive Database for a list of valid product codes.

Status Codes 1-99

8000 to 8499
Component Management Status Codes
These status codes originate from the Smart Component Management and Event Logging interface of the MicroKernel.

8001: The Services DLL encountered an error while allocating memory.

Memory could not be allocated. Verify that your system resources are not exhausted.

8002: The component ID string was not found.

The Services DLL attempted to retrieve an ID from a component, and the component did not have an ID. This status code results from an error in the application.

8003: Thunk path is not accessible to the Services DLL.

Smart Component Management cannot find the address of the Win32 interfaces.

8005: interface not initialized.

You receive this status code when an error causes an interface to not initialize properly. Check the Pervasive Event Log (PVSW.LOG) for more information.

8006: The specified component was not found.

Smart Component Management cannot operate on the component because it was not found. Check the Pervasive Event Log (PVSW.LOG) for more information.

1-100 Status Codes and Messages

8007: Error retrieving Win32 version information.

An error occurred while retrieving the Win32 version information from the operating system. This error should not occur and it indicates a problem with your Windows environment. Contact Pervasive Software Customer Support.

8008: Information mismatch in component ID.

You receive this status code when an application has specified multiple platforms, types or versions in a component ID. The Services DLL therefore cannot bind to the correct component.

8009: Required information missing in component ID.

You receive this status code when a component ID string is missing required information such as:

Platform Type Major/minor functional level

8010: Error while opening a file to retrieve component ID.

The Services DLL attempted to open a file in order to retrieve a component ID, and the file did not exist.

8012: Required information for binding rule is missing.

You receive this status code when required information is missing, such as:

Platform type Major/minor functional level

8013: Error locating a component.

An error occurred while opening an operating system directory to search for a component. Check the Pervasive Event Log (PVSW.LOG) for more information.

Status Codes 1-101

8016: Invalid instance specified.

This error occurs when an application passes an instance handle to the Services DLL that is invalid.

8017: Invalid version information structure.

This error occurs when an application tries to free a version information structure and the Services DLL determines that the version structure is invalid.

8018: Item not found by Services DLL.

This error occurs when an application requests that the Services DLL free an item, and the Services DLL determines that the item did not originate from the Services DLL.

8019: Library not accepting interface requests.

This error occurs when the Services DLL cannot accept requests. In a multithreaded application, this can occur when one thread attempts to make a request while other threads are overloading the Services DLL. In this situation, subsequent retries should clear the error.

8020: Error loading component.

You receive this status code when the Services DLL receives an operating system error when trying to load a component. Check the Pervasive Event Log (PVSW.LOG) for more information. If there is no information in the Pervasive Event Log related to receiving a status code 8020, refer to "Diagnosing Load Errors" in the "Component Architecture" chapter of the User's Guide. Troubleshooting note: This code may also be returned when a space is used in the Data Source Name (DSN) or Database Name (DBN).

8022: Component not initialized.

You should not receive this status code except when using a multithreaded application where one thread has shut down a component and the others continue trying to use it.

1-102 Status Codes and Messages

8023: Invalid filename passed to Services DLL.

You receive this status code when the Services DLL receives a filename that does not exist.

8024: Invalid function name.

You receive this status code when an application asks to import a function that does not exist.

8027: Required attribute missing in component ID.

You receive this status code when an application program does not specify a required attribute in the component ID.

8030: Return buffer too small for information.

This error occurs when an application passes the Services DLL a buffer in which to return information, and that buffer is not large enough to contain the information.

8032: Component ID is invalid.

You receive this status code when a component ID string was found but it may be invalid because it is too short, too long, or contains invalid characters.

8035: Invalid interface for NetWare platform.

You receive this status code when an application makes a call to an interface that is not supported on the NetWare platform.

8039: Invalid operating system handle specified.

You receive this status code when an operating system handle to a component ID string is invalid. This can occur when an application erroneously modifies a handle obtained using the GetFileVersionByHandle or the GetFileSizeByHandle functions.

Status Codes 1-103

8040: CRC check on component ID failed.

A routine CRC check on the component ID failed. You receive this status code when an application erroneously alters a component ID.

1-104 Status Codes and Messages

8500 to 8589
ECAS Interface Status Codes
This section describes the status codes returned by the ECAS (Enhanced Common Address Space) interface. Most of the errors are system errors and cause an entry in the Pervasive event log. In many cases when you receive these errors, there may be some instability in the environment or memory allocation and you will need to restart the machine.

8500: An error occurred during the Smart Components initialization.

In its attempt to auto-load the workstation engine, the application failed to initialize the smart component library. See the Pervasive event log for more information. You may also get more information about the problem that caused this error by setting the PVSW_DISP_LOAD_ERRS=AIF environment variable and running the application. This enables the Services DLL to display on-screen module load errors. However, this environment variable should only be set to diagnose module load errors. In all other cases, it should not be set.

8502: An error occurred when trying to locate W3UPIxyy.DLL.

In its attempt to auto-load the workstation engine, the application failed to locate or load W3UPIxyy.DLL in the path specified by the PERVASIVE_PATH environment variable. See the Pervasive event log for more information.

8503: An invalid W3UPIxyy.DLL has been found.

In its attempt to auto-load the workstation engine, the application discovered an incorrect version of W3UPIxyy.DLL. This problem may have been caused by a corrupted version of W3UPIxyy.DLL.

8504: An error occurred when trying to create system semaphore.

In its attempt to auto-load the workstation engine, the application failed to create the system semaphore. This problem may have been caused by the operating system running out of resources. Check the Pervasive event log for more information. Status Codes 1-105

8505: An initialization error occurred when trying to establish a session with the workstation engine.
In its attempt to auto-load the workstation engine, the application failed to establish the session with the workstation engine. This is a system error. Check the Pervasive event log for more information.

8506: A fatal error occurred when loading the MicroKernel.

In its attempt to auto-load the workstation engine, the application failed to load the MicroKernel, W3MKDE.DLL. This may have been caused by a missing W3MKDE.DLL. Check the Pervasive event log for more information.

8507: No valid database utility session was found.

The application lost its session with the workstation engine. Check the Pervasive event log for more information.

8508: An error occurred when attempting to enable Btrieve access.

The application failed to enable the Btrieve access method in the workstation engine. Check the Pervasive event log for more information.

8509: A timeout occurred during the initialization of the MicroKernel.

The application timed out during the initialization of the MicroKernel. This may have been caused by a bad configuration option or a malfunction of the workstation engine. Check the Pervasive event log for more information.

8510: A fatal error occurred when loading the MKDE.

In its attempt to auto-load the workstation engine, the application failed to load the MKDE, W3SSQL.DLL. This may have been caused by a missing W3SSQL.DLL. Check the Pervasive event log for more information.

8511: An error occurred when attempting to enable SQL access.

The application failed to enable the SQL access method in the workstation engine. Check the Pervasive event log for more information.

1-106 Status Codes and Messages

8512: A timeout occurred during the initialization of the MKDE.

The application timed out during the initialization of the MKDE. This may have been caused by a bad the MKDE configuration option or a malfunction of the workstation engine. Check the Pervasive event log for more information.

8513: An error occurred when disabling Btrieve access.

The application failed to disable the Btrieve access method in the workstation engine. Check the Pervasive event log for more information.

8514: An error occurred when unloading the MicroKernel.

The application failed to unload the MicroKernel. Check the Pervasive event log for more information.

8515: An error occurred when disabling SQL access.

The application failed to disable the SQL access method in the workstation engine. Check the Pervasive event log for more information.

8516: An error occurred when unloading the MKDE.

The application failed to unload the MKDE. Check the Pervasive event log for more information.

8517: An error occurred when closing the session with the workstation engine.
The application could not close the session with the workstation engine. Check the Pervasive event log for more information.

8518: An error occurred when attempting to allocate system memory.

The application failed to allocate memory from the system. Possible ways to avoid this include closing all other applications and restarting the engine, decreasing the size of the cache, and changing the engine settings so that a smaller number of files and/or file handles are open.

Status Codes 1-107

8590 to 8599
W3DBSMGR Status Codes
This section describes the status codes returned by W3DBSMGR logic. These errors are in the range 8590 to 8599 and cause an entry in the event log. In many cases when you receive these errors, there may be some instability in the environment or memory allocation and you will need to restart the machine.

8590: An error occurred in the database manager while initializing Smart Components Manager.
This error occurs when W3DBSMGR (Pervasive.SQL workstation engine) failed to initialize the smart component library. See the Pervasive event log for more information. You may also get more information about the problem that caused this error by setting the PVSW_DISP_LOAD_ERRS=AIF environment variable and running the application. This enables the Services DLL to display on-screen module load errors. However, this environment variable should only be set to diagnose module load errors. In all other cases, it should not be set.

8591: The database manager is already loaded.

In its attempt to initialize, the workstation engine detected that another copy of the Pervasive.SQL workstation engine is already running in memory. To avoid this error, shut down the program that is already running as specified below:

If the program is autoloaded (i.e., loaded through a Btrieve or a Scalable application), then terminate the application If the program is preloaded, then shut down the application using the tray icon.

1-108 Status Codes and Messages

8592: Insufficient memory to load the database manager.

This error indicates that the system is out of resources. Close some of the applications and try again.

8593: An error occurred while the database manager was creating a system thread.
This error indicates that the system is out of resources. Close some of the applications and try again.

8594: Engine cannot be restarted.

The workstation engine has been previously stopped while there were active applications and cannot be restarted. Close all current applications and try again. If you receive this code once more, you will need to restart the computer.

Status Codes 1-109

1-110 Status Codes and Messages

chapter

Messages
This chapter describes the messages can be returned to Pervasive.SQL applications. The messages are listed in alphabetic order by category. Some of the messages listed in this chapter may be generated by utilities that are not part of your Pervasive.SQL distribution. Messages are not the same as status codes. (see Chapter 1, Status Codes); messages are returned to end users by utilities or specific components and generally begin with a prefix and a number. For example: MKDE16: There is insufficient memory to load the MicroKernel Database Engine. Some messages refer to status codes, as in the following example: Error Accessing INDEX.DDF. Status = nn The status code is tied to a particular component, and it varies depending on the nature and source of the error. The value for nn or xx refers to a softwaresupplied number (for example, a status code, operation code, or number of records) and xxxx refers to a software-supplied name (for example, a filename, a data type or key type, or a command).

Messages 2-1

The messages are arranged according to the originating component. Table 2-1 lists the prefixes for each type of message. Table 2-1 Message Groups
Prefix (none) BDROUTER BREQUEST BREQUTIL BROUTER BSPXCOM BTCPCOM BUTIL MKDE NWBSRVCM UCINIT UCMGR UCUTIL Type of Code Generic Messages Btrieve Remote Communications Manager Messages Btrieve Requester Messages Requester Utility Messages Btrieve Message Router Messages Btrieve SPX Communications Module Messages Btrieve TCP/IP Communications Module Messages Btrieve Maintenance Utility Messages MicroKernel Database Engine Messages NetWare Btrieve Server Communications Manager Messages User Count Initialization Utility Messages User Count Manager Messages User Count Utility Messages

2-2 Status Codes and Messages

(No prefix)
Generic Messages
The following messages may be returned by more than one utility or component. These messages are not preceded by a component prefix or number.

Bfloat and Float Fields Must Be 4 or 8 Bytes

You have defined a FLOAT or BFLOAT column with a size other than 4 or 8 bytes. Change the column size to 4 or 8 bytes.

First and Second Password Entries Do Not Match, Please Retype

The password you entered the second time is not the same as the first one you specified. Specify and verify your password again.

Incorrect Netware Version

The NetWare version loaded is incompatible with the version of BREQUEST that is loaded. The NetWare shell for NetWare v3.12 or above must be installed at the client machine.

Incorrect Parameter
The SQL or Btrieve Requester returns this message if it encounters an error while loading at a DOS client machine. You specified an invalid configuration option. For information about the Setup utility and specifying the configuration options, refer to the Pervasive.SQL 2000 Users Guide.

Insufficient Memory
The SQL or Btrieve Requester returns this message if it encounters an error while loading at a DOS client machine. The Requester cannot allocate enough memory for the configuration options specified. Ensure that the client machine has enough memory to load all the programs you want to run.

Messages 2-3

Invalid Load File Format. End of Record Marker Not Found

The Btrieve Maintenance utility (BUTIL) encountered an invalid record terminator in the sequential load file. The Btrieve Maintenance utility expects a carriage return/line feed at the end of each record in a load file. This error usually occurs because the length specified at the beginning of the sequential record is incorrect.

Load File Referenced Undefined Public Variable. Module xxxx Not Loaded
In the NetWare v3.12 or later environment, a module you attempted to load (such as the Setup utility) requires that the correct version of another module be loaded. All Pervasive.SQL utilities require that the following software is loaded:

NetWare v3.12 or later, including the AFTER311 NLM. Load AFTER311 from AUTOEXEC.NCF before calling BSTART. Pervasive.SQL MicroKernel Database Engine v7.x and the BSPXCOM NLM

Local Engine Is Already Loaded

The Pervasive.SQL Requester returns this message if it encounters an error while loading at a DOS client machine. A local engine (XQL v2.11 or earlier) is loaded at the machine. You cannot load the older local engine and the newer Requester at the same time.

Must Have DOS 3.1 or Greater

The SQL or Btrieve Requester returns this message if it encounters an error while loading at a DOS client machine. The Requesters require DOS v3.1 or later.

NetWare Shell Is Not Installed

The SQL Requester returns this message if the NetWare shell is not installed on the DOS client machine at which you want to load the Requester. You must install the NetWare shell on the client machine before an application can communicate with SQL.

2-4 Status Codes and Messages

Redirection List Not Large Enough

The SQL Requester returns this message if it encounters an error while loading at a DOS client machine, and it cannot store all the redirected devices in its internal redirection list. Increase the value for the /R configuration option.

SQL Requester Is Already Loaded

The SQL Requester returns this message if you try to load the Requester when it is already loaded at the DOS client machine.

SPX Is Not Loaded

The SQL or Btrieve Requester returns this message if it encounters an error while loading at a DOS client machine. You must load the NetWare SPX communications software before an application can access the server-based version of Pervasive.SQL or the MicroKernel. For more information about installation, refer to Getting Started With Pervasive.SQL 2000.

Messages 2-5

BDROUTER
Btrieve Remote Communications Manager Messages
The following messages are specific to the BDROUTER Remote Communications Manager. This component is obsolete in Pervasive.SQL 2000, so these messages are returned only by v6.x engines.

BDROUTER1: The server has insufficient memory to execute BDROUTER.

The server has insufficient memory to load the BDROUTER NLM. Free some memory by unloading other NLMs or reconfiguring the NLMs to use less memory.

BDROUTER2: The value specified for a configuration option is invalid.

The value specified for a configuration option is invalid. Reload BDROUTER.NLM using valid options.

BDROUTER3: An internal error has occurred; the SPXOpenSocket function failed.

An internal diagnostic error has occurred. The SPXOpenSocket function failed. Another NLM may be using the socket number reserved for BDROUTER. If you receive this message, unload all other NLMs and then load BTRIEVE.NLM and BDROUTER.NLM. Finally, reload the other NLMs. This process reveals the NLM that is using BDROUTERs socket number.

BDROUTER11: The value specified for Directory Services username and password is invalid.
Before an application can access the NetWare Directory Services database, the user must be authenticated to NDS. For the client requesters, it is assumed that you have already been authenticated; therefore, the Requesters do not explicitly perform an NDS login. However, BDROUTER must explicitly log in to NDS and therefore must provide an NDS username and password. For this purpose, BDROUTER has two command line options, as follows: 2-6 Status Codes and Messages

/U:<NDSusername> /P:<NDSpassword>

These options are required and have no default values.

Messages 2-7

BREQUEST
Btrieve Requester Messages
The following messages are specific to Btrieve Requesters.

BREQUEST1: The message file xxxx is invalid; BREQUEST cannot be loaded.

Install a valid message file so that the Requester can be loaded.

BREQUEST4: The value specified for the Data Message Length (/d) option is invalid.
Specify the /D option as /D:n, where n is a number between 532 and 57,000. For more information about DOS Requester options, refer to the Getting Started With Pervasive.SQL 2000.

BREQUEST5: The workstation has insufficient memory to load BREQUEST.

Unload unnecessary programs or try a smaller value for the /D parameter. For more information about DOS Requester options, refer to Getting Started With Pervasive.SQL 2000.

BREQUEST7: The Btrieve Requester must be loaded before the Client Engine or Requester.
The Pervasive.SQL workstation engine or Requester is already loaded; the Btrieve Requester for DOS must be loaded first. Unload the Pervasive.SQL workstation engine or Requester and then load the Btrieve Requester for DOS.

BREQUEST8: DOS 3.00 or greater is not loaded; load DOS 3.00 or greater.
Load DOS 3.x or later to proceed.

2-8 Status Codes and Messages

BREQUEST9: SPX is not available on the workstation.

Load SPX.COM on your client machine.

BREQUEST10: The function SPXInitialize returned an error.

Ensure that the file IPX.COM is loaded.

BREQUEST11: The IPX socket table is full.

The Btrieve Requester for DOS returns this message when the IPX socket table is full.

BREQUEST12: The value specified for the NetWare Runtime Server support (/C) option is invalid.
Specify this option in one of these forms: /C:0 /C:1 Disables NetWare Runtime server support. Enables NetWare Runtime server support. To authenticate requests on the NetWare Runtime server, provide a username and password, separating them with commas, as follows: /C:1,username,password

For more information about DOS Requester options, refer to the Getting Started With Pervasive.SQL 2000.

BREQUEST13: The value specified for the Number of Servers (/S) is invalid.
Specify the /S option as /S:n, where n is a number between 1 and 8. For more information about DOS Requester options, refer to Getting Started With Pervasive.SQL 2000.

BREQUEST-14: Btrieve has been removed from memory.

This is an informational message that displays when you use the BREQUEST or BREQNT requester programs with the /u (unload) parameter. See Getting Started With Pervasive.SQL 2000 for more information on the command-line parameters of BREQUEST and BREQNT. Messages 2-9

BREQUEST-15: Btrieve is not loaded.

You used the BREQUEST or BREQNT requester programs with the /u parameter that unloads Btrieve from memory, and Btrieve was not running at the time.

2-10 Status Codes and Messages

BREQUTIL
Requester Utility Messages
This section lists the messages that the SQL and Btrieve Requester utilities generate.

BREQUTIL8: MicroKernel or Btrieve Requester is not loaded.

You must load the MicroKernel or a Btrieve Requester before you can perform a Btrieve operation.

BREQUTIL9: Btrieve operation nn was unsuccessful. The number of the applicable Btrieve status code is nn.
Refer to Chapter 1, Status Codes for a description of Status Code nn.

BREQUTIL16: MicroKernel or Btrieve Requester cannot be removed from memory while the MKDE is loaded.
If you want to unload the MicroKernel or Btrieve Requester, unload the MKDE first.

Messages 2-11

BROUTER
Btrieve Message Router Messages
The following messages are specific to the BROUTER Remote Communications Manager.

BROUTER2: The value specified for a configuration option is invalid.

Reload BROUTER.NLM using valid configuration options.

BROUTER3: An internal error has occurred; the SPXOpenSocket function failed.

An internal diagnostic error occurred. The SPXOpenSocket function failed. Another NLM may be using the socket number reserved for BROUTER. If you receive this message, unload all other NLMs and then load BTRIEVE.NLM and BROUTER.NLM. Finally, reload the other NLMs. This process reveals the NLM that is using BROUTERs socket number.

BROUTER7: The server has insufficient memory to execute BROUTER.

Free some memory by unloading NLMs or reconfiguring NLMs to use less memory.

2-12 Status Codes and Messages

BSPXCOM
Btrieve SPX Communications Module Messages
The following messages are specific to the Btrieve Communications Manager.

BSPXCOM2: The server has insufficient memory to execute BSPXCOM.NLM

An error occurred during a memory allocation operation. Free memory by unloading NLMs or reconfiguring NLMs to use less memory. Retry the operation. If the error persists, contact Pervasive Software Customer Support.

BSPXCOM3: An internal error has occurred. BSPXCOM detected a semaphore allocation failure.
An internal error occurred during a semaphore allocation operation. Retry the operation. If the error persists, contact Pervasive Software Customer Support.

BSPXCOM4: The Service Request Block (SRB) function code nn contains invalid data. Check for an incompatible version of the file BSPXCOM.NLM.
Ensure that BSPXCOMs version is compatible with the version number of the workstations Btrieve Requester.

BSPXCOM6: Another NLM is using the socket number reserved for BSPXCOM.NLM.
To solve this condition, unload all other NLMs. Load BTRIEVE.NLM and NWBSRVCM.NLM, and then reload the other NLMs. This process reveals the NLM that is using BSPXCOM.NLMs socket number.

Messages 2-13

BSPXCOM7: An SPX receive I/O error (nn) has occurred. The connection has been lost.
An error occurred during an SPX-level receive operation. Refer to your operating system documentation for the definition of the error number. Retry the operation. If the error persists, contact Pervasive Software Customer Support for more information.

BSPXCOM8: An SPX send I/O error (nn) has occurred. The connection has been lost.
An error occurred during an SPX-level send operation. Refer to your operating system documentation for the definition of the error number. Retry the operation. If the error persists, contact Pervasive Software Customer Support for more information.

BSPXCOM10: Bad connection ID detected on receive. The SPX connection was lost after the initial request began.
If this message appears frequently, increase your requesters SPX Timeout parameter, which is controlled with the Configuration (Setup) utility. Also, check for NLMs that are monopolizing the CPU time.

BSPXCOM11: Bad connection ID detected on send. The SPX connection was lost after the initial request began.
If this message appears frequently, increase your requesters SPX Timeout parameter, which is controlled with the Configuration (Setup) utility. Also, check for NLMs that are monopolizing the CPU time.

BSPXCOM12: An error (nn) was detected while trying to establish an SPX session requested by a remote workstation.
An error occurred during an SPX-level session establishment operation. Refer to your operating system documentation for the definition of the error number value. Retry the operation. If the error persists, contact Pervasive Software Customer Support for more information.

2-14 Status Codes and Messages

BSPXCOM13: The session was rejected because the session limit was reached. Increase the value specified for the Number of Remote Sessions option.
Increase the value specified for the Number of Remote Sessions configuration option, as described in the Pervasive.SQL 2000 Users Guide.

BSPXCOM14: The request for statistics from the Monitor utility was not recognized. Check for an incompatible version of the utility or BSPXCOM.NLM.
Ensure that your BSPXCOM.NLM version is compatible with the version number of the Monitor utility.

BSPXCOM15: An internal error has occurred. BSPXCOM did not recognize the GET_EIM_STATS function.
Ensure that the version of BSPXCOM.NLM is compatible with the version number of the Monitor utility.

BSPXCOM18: A thread initialization error has occurred.

An error occurred during BSPXCOM.NLM thread initialization. Refer to the Pervasive Software Event Log (PVSW.LOG) for error messages preceding this one. Correct the problem and retry the operation.

BSPXCOM19: A BeginThread() error (nn) has occurred.

An error occurred during a BeginThread operation. Refer to your operating system documentation for the definition of the error number value. Retry the operation. If the error persists, contact Pervasive Software Customer Support for more information.

Messages 2-15

BTCPCOM
Btrieve TCP/IP Communications Module Messages
BTCPCOM-1: The option specified is not a valid option.
Specify a valid option.

BTCPCOM-2: The server has insufficient memory to execute BTCPCOM.NLM.

An error occurred during a memory allocation operation. Free memory by unloading NLMs or reconfiguring NLMs to use less memory. Retry the operation. If the error persists, contact Pervasive Software Customer Support for more information.

BTCPCOM-3: An internal error has occurred. BTCPCOM.NLM detected a semaphore allocation failure.
An error occurred during a semaphore allocation operation. Retry the operation. If the error persists, contact Pervasive Software Customer Support for more information.

BTCPCOM-4: The Service Request Block (SRB) function code nn contains invalid data. Check for an incompatible version of the file BTCPCOM.NLM.
Ensure that BTCPCOMs version is compatible with the version number of the workstations Btrieve Requester.

BTCPCOM-5: A TCP/IP level receive I/O error nn has occurred. The connection has been lost.
An error occurred during a TCP/IP level receive operation. Refer to your operating system documentation for the definition of the error number value. Retry the operation. If the error persists, contact Pervasive Software Customer Support for more information.

2-16 Status Codes and Messages

BTCPCOM-6: A TCP/IP level send I/O error nn has occurred. The connection has been lost.
An error occurred during a TCP/IP level send operation. Refer to your operating system documentation for the definition of the error number. Retry the operation. If the error persists, contact Pervasive Software Customer Support for more information.

BTCPCOM-7: A TCP/IP accept error (nn) has occurred.

An error occurred during a TCP/IP level accept session establishment operation. Refer to your operating system documentation for the definition of the error number. Retry the operation. If the error persists, contact Pervasive Software Customer Support for more information.

BTCPCOM-8: The session was rejected because the session limit was reached. Increase the value specified for the Number of Remote Sessions option.
Increase the value specified for the Number of Remote Sessions option. This option is described in the Pervasive Users Guide.

BTCPCOM-9: The request for statistics from the Monitor utility was not recognized. Check for an incompatible version of the utility or BTCPCOM.NLM.
Ensure that the BTCPCOM.NLM version is compatible with the version number of the Monitor utility.

BTCPCOM-10: An internal error has occurred. BTCPCOM did not recognize the GET_EIM_STATS function.
Ensure that the BTCPCOM.NLM version is compatible with the version number of the Monitor utility.

BTCPCOM-12: A TCP/IP select() error (nn) has occurred while trying to establish a session requested by a remote workstation.
An error occurred during a TCP/IP-level select session establishment operation. Refer to your operating system documentation for the definition

Messages 2-17

of the error number. Retry the operation again. If the error persists, call Pervasive Software technical support for more information.

BTCPCOM-13: A thread initialization error has occurred.

An error occurred during BTCPCOM.NLM thread initialization. Refer to the Pervasive Software event log (PVSW.LOG) for error messages preceding this one. Correct the problem and retry the operation.

BTCPCOM-15: A TCP/IP socket() error (nn) has occurred.

An error occurred during a TCP/IP-level socket operation. Refer to your operating system documentation for the definition of the error value. Retry the operation again. If the error persists, call Pervasive Software technical support for more information.

BTCPCOM-16: A TCP/IP setsockopt() error (nn) has occurred.

An error occurred during a TCP/IP-level setsockopt operation. Refer to your operating system documentation for the definition of the error value. Retry the operation again. If the error persists, call Pervasive Software technical support for more information.

BTCPCOM-17: A TCP/IP bind() error (nn) has occurred.

An error occurred during a TCP/IP-level bind operation. Refer to your operating system documentation for the definition of the error value. Retry the operation again. If the error persists, call Pervasive Software technical support for more information.

BTCPCOM-18: A TCP/IP listen() error (nn) has occurred.

An error occurred during a TCP/IP-level listen operation. Refer to your operating system documentation for the definition of the error value. Retry the operation again. If the error persists, call Pervasive //Software technical support for more information.

BTCPCOM-19: A TCP/IP gethostname() error (nn) has occurred.

An error occurred during a TCP/IP-level gethostname operation. Refer to your operating system documentation for the definition of the error value.

2-18 Status Codes and Messages

Retry the operation again. If the error persists, call Pervasive Software technical support for more information.

BTCPCOM-20: A TCP/IP NWgethostbyname() error (nn) has occurred.

An error occurred during a TCP/IP-level NWgethostbyname operation. Refer to your operating system documentation for the definition of the error value. Retry the operation again. If the error persists, call Pervasive Software technical support for more information.

BTCPCOM-21: A TCP/IP NetDBgethostbyname() error (nn) has occurred.

An error occurred during a TCP/IP-level NetDBgethostbyname operation. Refer to your operating system documentation for the definition of the error value. Retry the operation again. If the error persists, call Pervasive Software technical support for more information.

BTCPCOM-22: A BeginThread() error (nn) has occurred.

An error occurred during a BeginThread operation. Refer to your operating system documentation for the definition of the error value. Retry the operation again. If the error persists, call Pervasive Software technical support for more information.

Messages 2-19

BUTIL
Btrieve Maintenance Utility Messages
The following messages are specific to the Btrieve Maintenance utility.

BUTIL1: Message file initialization failed.

Only BUTIL.EXE in DOS returns this message. The utility could not find the BUTILDOS.MSG file, which contains messages that the utility uses. Ensure that you installed NetWare Communication Services correctly.

BUTIL2: Message file initialization failed. BUTIL was unable to access BTIUTILD.MSG.
Only BUTIL.EXE in DOS returns this message. The utility could not find the BTIUTILD.MSG file, which contains messages that the utility uses. Ensure that you installed Btrieve for DOS correctly.

BUTIL6: The BUTIL command is invalid.

The syntax of the command you entered is incorrect. Verify the syntax before re-entering the command.

BUTIL8: The command completed, but one or more errors occurred.

An error occurred when you executed a command that performed a number of MicroKernel operations. These commands include COPY, LOAD, or CLONE. This message is accompanied by additional messages that can help you identify the problem.

BUTIL9: The command did not complete due to an unrecoverable error.

Verify that the syntax you entered is correct before re-entering the command. This message is accompanied by additional messages that can help you identify the problem.

2-20 Status Codes and Messages

BUTIL10: The command line contains a syntax error.

The syntax of the command you entered is incorrect. Verify the syntax before re-entering the command.

BUTIL11: The command line requires the index file.

If you specify the BUTIL INDEX or SAVE command (modified by the Y parameter) to the Btrieve Maintenance utility, you must specify the full pathname of an external index file.

BUTIL12: The command line requires the key number.

If you specify the DROP command or the SAVE command (modified by the N parameter) to the Btrieve Maintenance utility, you must specify the key number of the key you want to drop or by which you want to save the data file.

BUTIL13: The key size for key of type xxxx is invalid.

In a description file, the specified value of the Key Length element for a particular key is incorrect. Ensure that the value of each Key Length element is appropriate for the matching Key Type element.

BUTIL15: Error occurred on key segment descriptor xxx of description file.

An error occurred when the Maintenance utility attempted to read the key segment descriptor portion of the description file. Ensure that the elements that describe the specified key segment are valid.

BUTIL16: BUTIL could not open the description file.

Before attempting to re-enter the CREATE, INDEX, or SINDEX commands, ensure that the file exists and that you specify the correct full pathname.

BUTIL18: An error occurred during access of the sequential file.

Ensure that the source file is valid.

Messages 2-21

BUTIL19: BUTIL could not open the alternate collating sequence file.
Ensure that you assigned a valid pathname to the Alternate Collating Sequence filename element in the description file.

BUTIL20: An error occurred during access of the alternate collating sequence file.
Ensure that the information in the alternate collating sequence file is formatted correctly.

BUTIL21: The file version is earlier than 6.0.

The RECOVER command cannot recover data from a Btrieve v5.x file.

BUTIL23: The /D parameter specified to the Requester was too small for BUTIL to receive the entire record. BUTIL is writing only nn bytes.
The Maintenance utility is writing only as many bytes as the value of the /D option allows. If you want the utility to write all the bytes in the record, specify a value for the /D option that is at least as large as the affected record.

BUTIL25: The /D parameter specified to BUTIL was too small for BUTIL to receive any part of the record.
You specified an invalid value for the Requesters /D option. Use the Setup utility to increase the value specified.

BUTIL26: The data buffer is too small to hold any part of the record.
The MicroKernel cannot return any data in the data buffer because the data buffer is too small to hold it. Use the Setup utility to increase the value specified for the Largest Record Size configuration option.

BUTIL27: An error occurred during the access of the variable page. BUTIL is writing the obtainable portion of the variable page.
An error occurred during the recovery of a file with variable-length records. The file is corrupt.

2-22 Status Codes and Messages

BUTIL30: The key position cannot exceed the record length.

The range of the specified key position is invalid. The key position you specify on a Btrieve call must be within the range of the records length. For example, for a record that is 100 bytes long, a key position of 50 is within the correct range. However, a key position of 150 is not.

BUTIL31: The key position plus key length cannot exceed the record length.
The range of the key position you specified is invalid. The key position of a key plus its length cannot be larger than the record length. Verify that the key is defined so that its position plus its length does not exceed the record length.

BUTIL32: The key length must be an even number for key type xxxx.
You specified an invalid key length for the key type. Some key types must contain an even number of bytes. Specify a valid Key Length element.

BUTIL36: The page size must be a multiple of 512, from 512 to 4,096.
The page size you specified is not a multiple of 512, from 512 to 4096. Specify an appropriate page size.

BUTIL37: The record length cannot exceed the page size.

The record length you specified is invalid. In the description file, the record length you specified for the Record Length element is larger than the page size you specified for the Page Size element. Specify a record length that is smaller than the page size or increase the page size.

BUTIL38: The record length must be at least 4 and no greater than 4,096.
Specify a record length between 4 and 4096 (inclusive) for Btrieve v5.x, or between 4 and 4088 for Btrieve v6.x.

BUTIL41: The alternate collating sequence cannot be found.

The Maintenance utility cannot find the alternate collating sequence file you specified in the definition file. Verify that the alternate collating sequence file exists and that the name is correct in the definition file. Messages 2-23

BUTIL43: The file exists, but the Replace option was not specified.
The Maintenance utility did not create a file when you specified the BUTIL CREATE command because the file already exists. To recreate this file, specify the Replace Existing File element in the description file as Y.

BUTIL44: The file access error nn occurred for file filename.

The Maintenance utility returns the appropriate status code and filename for a file on which a file access error occurred during the beginning or end of continuous operation. The corrective measure depends on the status code received. Refer to Chapter 1, Status Codes for a description of Status Code nn.

BUTIL45: The number of duplicate keys must be between 1 and 119.

Check the value specified for the Duplicate Key element in the description file.

BUTIL47: BUTIL cannot open the command file.

Ensure that the command file exists and that you specified the command file location and filename correctly.

BUTIL48: The command file is empty.

Specify the desired commands in the command file before attempting to use the command file again. In addition, ensure you specified the correct command filename.

BUTIL49: The command file exceeds 1,000 bytes.

A command file cannot contain more than 1,000 bytes. Verify that the command file adheres to this requirement.

BUTIL50: An internal error caused BUTIL to terminate.

The Maintenance utility detected an internal diagnostic error that caused it to terminate.

BUTIL52: Btrieve cannot be stopped when SQL is loaded.

Unload the MKDE before attempting to unload the MicroKernel. 2-24 Status Codes and Messages

BUTIL53: Btrieve error nn occurred for file or command xxxx.

The Maintenance utility returns a status code related to a particular file or command. The corrective measure depends on the status code received. Refer to Chapter 1, Status Codes for a description of Status Code nn.

BUTIL60: The end of the file occurred while BUTIL was expecting keyword xxxx on key segment descriptor nn.
Check the syntax of the description file.

BUTIL61: The end of the file occurred while BUTIL was expecting keyword xxxx.
Check the syntax of the description file.

BUTIL62: BUTIL was expecting keyword xxxx on key segment descriptor nn.
Check the syntax of the description file.

BUTIL63: BUTIL was expecting keyword xxxx.

Check the syntax of the description file.

BUTIL65: BUTIL has loaded no records.

Verify that you specified the command correctly and that the input file is in the correct format.

BUTIL70: The Btrieve error nn occurred on closing a file.

The Maintenance utility returns this status code while closing a file. The corrective measure depends on the status code received. Refer to Chapter 1, Status Codes for a description of Status Code nn.

BUTIL74: Btrieve error nn was returned for the Stop Command.

This message applies only to the DOS environment. The Maintenance utility returns this status code after you issue the BUTIL STOP command. The corrective measure depends on the status code received. Refer to Chapter 1, Status Codes for a description of Status Code nn.

Messages 2-25

BUTIL76: When BUTIL wrote the Page Allocation Table at page #nn, an error occurred.
The Maintenance utility returns this message while salvaging a file if the file is corrupt, or when a hardware error occurs.

BUTIL77: When BUTIL wrote a mirror copy of the Page Allocation Table at page #nn, an error occurred.
The Maintenance utility returns this message while salvaging a file if the file is corrupted, or when a hardware error occurs.

BUTIL82: Error occurred on file specification of the description file.

An error occurred when the Maintenance utility attempted to read the file specification portion of the description file. Ensure that the elements that describe the file specification are valid.

BUTIL84: BUTIL internal error.

The Maintenance utility encountered an internal error, such as an invalid pointer. Try to run the Maintenance utility again.

BUTIL90: BUTIL could not allocate enough memory.

Free some memory at the server by unloading unused applications.

BUTIL91: BUTIL could not determine the size of the file.

Try to recover the file using the BUTIL RECOVER command.

BUTIL101: The list of files that were not processed is: list.
The Maintenance utility returns this error during the ROLLFWD operation if the utility encounters a file that cannot be rolled forward. The utility stops rolling forward and lists the remaining files not processed. If you receive this message in conjunction with the Maintenance utility message number 103, restore the missing log segment and any log segments created after it to the log directory. If you cannot restore all missing log segments, restore as many as possible. Then, perform the ROLLFWD operation and specify the segment_number parameter of the earliest log segment you could restore.

2-26 Status Codes and Messages

BUTIL102: A Roll Forward error occurred.

An internal error occurred while the MicroKernel was rolling forward files.

BUTIL103: Log segment number nn is missing.

The Maintenance utility returns this error during ROLLFWD operation if you do not specify a segment_number parameter and one of the files to be rolled forward has a Restore Segment Number that indicates a log segment number that the MicroKernel cannot find.

BUTIL131: BUTIL was unable to create or open the sequential file.

The Maintenance utility returns this message when it is unable to create or open the specified file. Check the sequential file to make sure it exists and has the read-only attribute set.

BUTIL132: The disk volume is full.

You must have more disk space to create or enlarge any data files.

BUTIL134: BUTIL was unable to create or open the new file.

Check the file specified for the BUTIL SAVE or RECOVER command. The file may already exist.

BUTIL136: BUTIL was unable to write the new backup file.

Verify that you specified the correct path and filename for the backup file. Also, ensure you have enough disk space for the file to be written.

BUTIL141: File xx has an invalid extension. This extension is reserved for extended unformatted files.
Specify a valid extension. For more information, see the Pervasive.SQL 2000 Users Guide.

BUTIL-142: File xx exists.

For more information about extended files, see the Pervasive.SQL 2000 Users Guide.

Messages 2-27

BUTIL-143: File xx exists. This file is a potential extension of file yy. Remove this file and other potential extension files in this directory.
For more information about extended files, see the Pervasive.SQL 2000 Users Guide.

BUTIL-144: File xx has reached the size limit. The utility created one or more extension files. The last extension file is yy.
For more information about extended files, see the Pervasive.SQL 2000 Users Guide.

BUTIL-145: The utility found file xx. Remove this file before loading data from file yy.
For more information about extended files, see the Pervasive.SQL 2000 Users Guide.

BUTIL152: There was an error opening file filename.

Check the data file attributes, path, and filename.

BUTIL155: BUTIL cannot open the Btrieve file filename.

Check the path, filename, and file attributes.

2-28 Status Codes and Messages

MKDE
MicroKernel Database Engine Messages
This section lists the messages that the MicroKernel Database Engine generates.

MKDE12: The value specified for the option option is invalid.

Enter the correct value in the BSTART.NCF, BTI.INI, or BTI.CFG file.

MKDE13: The option specified is not a valid option.

Remove the invalid option from the BSTART.NCF, BTI.INI, or BTI.CFG file.

MKDE16: There is insufficient memory to load the MicroKernel Database Engine.

The system has insufficient memory to allow the MicroKernel to load as it is configured. Use the Setup utility to reconfigure the MicroKernel to use less memory, or unload any unnecessary applications.

MKDE20: The log file filename cannot be written. Check disk space.
If the disk is full, free some space by deleting any unnecessary files. When an error occurs while writing to the transaction log file, the MicroKernel attempts to resume transaction logging after every update to a data file containing system data. Therefore, when the condition causing the error is corrected (for example, when more disk space is made available), the MicroKernel automatically resumes transaction logging.

MKDE25: The file filename is rolling back.

Rolling back is the procedure the MicroKernel uses to restore a file to a consistent state after a system crash. This procedure undoes the most recent changes to the file (changes in the most recent system transaction).

Messages 2-29

MKDE51: Program initialization failed; the program was not loaded.

This is an informative message that the MicroKernel returns when an error prevents the MicroKernel from loading. Another message accompanies this one and provides more specific information about the nature of the error.

MKDE57: The file filename cannot be created in the log segment directory xxxx.
While initializing, the MicroKernel could not find the specified transaction log segment directory, so it did not load. Ensure that the directory exists and that the MicroKernel has rights to it. (This is not a problem for the NetWare NLM version of the MicroKernel, because it has rights to all directories and files.) Use the Setup utility to specify the transaction log directory.

MKDE58: The file filename cannot be opened in the log segment directory xxxx.
While initializing, the MicroKernel could not open the specified file in the transaction log segment directory, so it did not load. Ensure that the directory and file exist and that the MicroKernel has rights to it. (This is not a problem for the NetWare NLM version of the MicroKernel, because it has rights to all directories and files.) Another possibility is that someone has opened the file with an exclusive lock. Use the Monitor utility to see if another user has locked the file.

MKDE59: The log segment file filename cannot be created.

The MicroKernel could not create the specified transaction log segment file. Ensure that you have enough disk space and that the MicroKernel has rights to the file. (This is not a problem for the NetWare NLM version of the MicroKernel, because it has rights to all directories and files.) Another possibility is that someone has opened the file with an exclusive lock. Use the Monitor utility to see if another user has locked the file. This error can occur while the MicroKernel is loading, or later, during normal operations. If it occurs while the MicroKernel is loading, the loading fails and no operations are possible until the problem is corrected. If the error occurs later, during normal operations, there are some additional issues to consider. If the MicroKernel is already loaded when an error occurs creating the transaction log file, it ceases transaction logging; however, the MicroKernel attempts to resume transaction logging after every update to a data file 2-30 Status Codes and Messages

containing system data. Therefore, when the condition causing the error is corrected (for example, when more disk space is made available), the MicroKernel automatically resumes transaction logging.

MKDE75: The log file format is invalid.

The MicroKernel returns this message when the log segment file format is incompatible. Ensure that the version of the MicroKernel doing the roll forward is the same as the version of the MicroKernel that created the log file.

MKDE76: An Open operation failed on xxxx with Btrieve error nn.

The MicroKernel returns this message during roll forward operations when a Btrieve error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, Status Codes for a description of Status Code nn.

MKDE77: An unexpected Btrieve error nn occurred on INSERT to xxxx.

The MicroKernel returns this message during roll forward operations when a Btrieve Insert error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, Status Codes for a description of Status Code nn.

MKDE78: An unexpected Btrieve error nn occurred on UPDATE in xxxx.

The MicroKernel returns this message during roll forward operations when a Btrieve Update error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, Status Codes for a description of Status Code nn.

MKDE79: An unexpected Btrieve error nn occurred on DELETE from xxxx.

The MicroKernel returns this message during roll forward operations when a Btrieve Delete error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, Status Codes for a description of Status Code nn.

Messages 2-31

MKDE80: The system is out of memory.

The MicroKernel returns this message when the server has insufficient memory to allow the program to operate. Unload any unnecessary applications and retry the roll forward operation.

MKDE81: An internal error nn occurred.

The MicroKernel returns this message when an internal error occurs. Try to perform the operation again.

MKDE82: An unexpected Btrieve error nn occurred on GET EQUAL in xxxx.

The MicroKernel returns this message during roll forward operations when a Btrieve Get Equal error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, Status Codes for a description of Status Code nn.

MKDE83: The log file is corrupt.

The MicroKernel returns this message when the log segment file is damaged and unreadable. The Log Segment Manager cannot perform roll forward operations using this log segment.

MKDE84: An error occurred while reading the log file.

The MicroKernel returns this message when an error prevents the program from reading the log segment file. The MicroKernel cannot perform roll forward operations using this log segment.

MKDE85: An unexpected Btrieve error nn occurred on CREATE INDEX to filename.

The MicroKernel returns this message during roll forward operations when an error occurs on a CREATE INDEX operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, Status Codes.

2-32 Status Codes and Messages

MKDE86: An unexpected Btrieve error nn occurred on DROP INDEX to filename.

The MicroKernel returns this message during roll forward operations when an error occurs on a DROP INDEX operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, Status Codes.

MKDE87: An unexpected Btrieve error nn occurred on BEGIN TRANSACTION to filename.

The MicroKernel returns this message during roll forward operations when an error occurs on a BEGIN TRANSACTION operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, Status Codes.

MKDE88: An unexpected Btrieve error nn occurred on END TRANSACTION to filename.

The MicroKernel returns this message during roll forward operations when an error occurs on an END TRANSACTION operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, Status Codes.

MKDE89: An unexpected Btrieve error nn occurred on ABORT TRANSACTION to filename.

The MicroKernel returns this message during roll forward operations when an error occurs on an ABORT TRANSACTION operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, Status Codes.

MKDE90: An unexpected Btrieve error nn occurred on CLOSE to filename.

The MicroKernel returns this message during roll forward operations when an error occurs on a CLOSE operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, Status Codes.

Messages 2-33

MKDE91: An unexpected Btrieve error nn occurred on GET POSITION to filename.

The MicroKernel returns this message during roll forward operations when an error occurs on a GET POSITION operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, Status Codes.

MKDE92: An unexpected Btrieve error nn occurred on BEGIN TRANSACTION.

The MicroKernel returns this message during roll forward operations when an error occurs on a BEGIN TRANSACTION operation. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, Status Codes.

MKDE93: An unexpected Btrieve error nn occurred on END TRANSACTION.

The MicroKernel returns this message during roll forward operations when an error occurs on an END TRANSACTION operation. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, Status Codes.

MKDE94: An unexpected Btrieve error nn occurred on ABORT TRANSACTION.

The MicroKernel returns this message during roll forward operations when an error occurs on an ABORT TRANSACTION operation. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, Status Codes.

MKDE1001: The value specified for Cache Allocation is invalid.

Specify a valid value.

MKDE1002: The value specified for Longest Compressed Record Size is invalid.
Specify a valid value.

2-34 Status Codes and Messages

MKDE1003: The value specified for Extended Operation Buffer Size is invalid.
Specify a valid value.

MKDE1004: The value specified for Open Files is invalid.

Specify a valid value.

MKDE1005: The value specified for Operation Bundle Limit is invalid.

Specify a valid value.

MKDE1007: The value specified for Number of Handles is invalid.

Specify a valid value.

MKDE1008: The value specified for I/O Threads is invalid.

Specify a valid value.

MKDE1009: The value specified for Maximum Sort Buffer is invalid.

Specify a valid value.

MKDE1010: The path specified for Temporary Sorting Files is invalid.

Specify a valid path.

MKDE1011: Info: The Number of Handles cannot be less than the Number of Open Files.
Either specify a higher value for the Handles or specify a lower value for the Open Files option.

MKDE1015: The value specified for Maximum Record Size is invalid.

Specify a valid value for this option. For more information about valid values, refer to the Pervasive.SQL 2000 Users Guide.

Messages 2-35

MKDE1017: The value specified for System Transaction Hold Limit is invalid.
Specify a valid value for this option. For more information about valid values, refer to the Pervasive.SQL 2000 Users Guide.

MKDE1019: The value specified for Maximum Active Clients is invalid.

Specify a valid value for this option. For more information about valid values, refer to the Pervasive.SQL 2000 Users Guide.

MKDE1020: The value specified for Worker Threads is invalid.

Specify a valid value for this option. For more information about valid values, refer to the Pervasive.SQL 2000 Users Guide.

MKDE1021: The value specified for Thread Priority Delta is invalid.

Specify a valid value. For more information about valid values, refer to the Pervasive.SQL 2000 Users Guide.

MKDE1022: The value specified for Initiation Time Limit is invalid.

Specify a valid value.

MKDE1023: The value specified for Disk I/O Wait Time is invalid.
Specify a valid value.

MKDE1024: The value specified for Page Write Group Size is invalid.
Specify a valid value.

MKDE1025: The value specified for Auto-Terminate Delay is invalid.

Specify a valid value.

MKDE1026: The value specified for Number of Lines Allocated is invalid.

Specify a valid value. 2-36 Status Codes and Messages

MKDE1027: The value specified for Message Log File Limit is invalid.
Specify a valid value.

MKDE1028: The path specified for Home Directory is invalid.

Specify a valid path.

MKDE1030: The value specified for the option_name option is invalid.

The MicroKernel Database Engine returns this message when the value specified for the option_name option is invalid. Specify a valid value.

MKDE1032: The option specified is not a valid option.

The MicroKernel Database Engine returns this message when the option you specified is not valid. Specify a valid configuration option.

MKDE1152: Btrieve cannot get sufficient memory to complete the operation.

The computer has insufficient memory to allow the MicroKernel to load as it is configured. Configure the MicroKernel to use less memory or unload any unnecessary applications.

MKDE1156: The log file filename cannot be written. Check disk space.
The transaction log file filename cannot be written. Check the disk space. If the disk is full, free some space by deleting any unnecessary files. When an error occurs while writing to the transaction log file, the MicroKernel attempts to resume transaction logging after every update to a data file containing system data. Therefore, when the condition causing the error is corrected (for example, when more disk space is made available), the MicroKernel automatically resumes transaction logging.

MKDE1161: The file filename is rolling back.

Rolling back is the procedure the MicroKernel uses to restore a file to a consistent state after a system crash. This procedure undoes the most recent changes to the file (changes in the most recent system transaction).

Messages 2-37

MKDE1164: Error creating/accessing semaphore.

The MicroKernel returns this message if an internal error occurs.

MKDE1165: Error creating execution thread.

Decrease the values for either the Number of Worker Threads or the I/O Threads configuration option.

MKDE1166: Could not open Pervasive Event Log file. This file is created in the home directory. Verify that the directory is present and sufficient space is available.
The MicroKernel returns this message when it cannot create the Pervasive Event Log (PVSW.LOG) in the directory. Make sure that the disk on your computer is not full. The home directory is defined as \WINNT\SYSTEM32 (Windows NT), \WINDOWS\SYSTEM (Windows 95) or SYS:\SYSTEM (NetWare server).

MKDE1167: Could not create IPC queue.

The MicroKernel returns this message if an internal error occurs.

MKDE1168: Clients(s) active - Shutdown anyway?

The MicroKernel returns this message when you attempt to shut down the MicroKernel while at least one application is still using the MicroKernel. If you choose to shut down anyway, you could lose data.

MKDE1169: Could not open BTI.INI.

The MicroKernel returns this message when it cannot open the BTI.INI file. Make sure that the file is in the home directory.

MKDE1171: The file BTI.INI is flagged as read only. Btrieve can temporarily override this attribute to save the current settings. Do you wish to continue?
The MicroKernel returns this message if the BTI.INI file is flagged as read only and you attempt to save changes to the Btrieve configuration settings, 2-38 Status Codes and Messages

which are stored in the BTI.INI file. If you choose to continue, the MicroKernel updates the BTI.INI file but maintains its read only status. If you choose not to continue, the MicroKernel does not update the BTI.INI file. You can still change the configuration settings, but they are only in effect for the current Btrieve session.

MKDE1172: Error writing to BTI.INI.

Make sure that your computers disk is not full and that you have the appropriate rights to the file.

MKDE1175: I/O error - filename.

The MicroKernel returns this message when it encounters an I/O error while reading from or writing to a file. This message typically accompanies Status Code 2.

MKDE1176: Variable page error - filename.

The MicroKernel returns this message when it encounters an error on a variable page. This message typically accompanies Status Code 2.

MKDE1177: Help is not available.

The MicroKernel returns this message when it cannot find the Btrieve help file (BTRIEVE.HLP). Make sure that the file is located in the home directory.

MKDE1178: Resources allocated.

This is an informative message from the MicroKernel Database Engine. No action is required.

MKDE1179: Resources released.

This is an informative message from the MicroKernel Database Engine. No action is required.

MKDE1180: System Error: nn.nn.nn.

The MicroKernel Database Engine returns this message when a system error occurs. Messages 2-39

MKDE1183: Not enough available cache to complete an operation.

Configure the MicroKernel to use more cache memory or reduce the files page size.

MKDE1184: Unable to set number of file handles to requested value. Maximum open files reduced to nn.
The MicroKernel is unable to set the Maximum Open Files to the value you specified; instead the MicroKernel uses the value indicated in the message. To avoid receiving this message, run fewer applications at the same time.

MKDE1192: Settings read from NOVDB.INI - To change to BTI.INI, save current settings.
The MicroKernel returns this message when it loads and finds a NOVDB.INI file where it expects to find the BTI.INI file. To use the BTI.INI file, open the Settings notebook and click the Save button.

MKDE1193: Btrieve is using default settings.

The MicroKernel returns this message when it loads and cannot find values for one or more configuration options. The BTI.INI file is incomplete or missing. You may update the configuration options using the Settings notebook.

MKDE1194: Additional worker thread spawned.

The MicroKernel returns this message when it must create more worker threads than the number specified by the Number of Worker Threads configuration option. To avoid receiving this message, increase the value for the Number of Worker Threads option.

MKDE1207: The log file format is invalid.

The MicroKernel returns this message when the log segment file format is incompatible. Ensure that the version of the MicroKernel doing the roll forward is the same as the version of the MicroKernel that created the log file.

2-40 Status Codes and Messages

MKDE1208: An Open operation failed on xxxx with Btrieve error nn.

The MicroKernel returns this message during roll forward operations when a Btrieve error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, Status Codes for a description of Status Code nn.

MKDE1209: An unexpected Btrieve error nn occurred on INSERT to xxxx.

The MicroKernel returns this message during roll forward operations when a Btrieve Insert error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, Status Codes for a description of Status Code nn.

MKDE1210: An unexpected Btrieve error nn occurred on UPDATE in xxxx.

The MicroKernel returns this message during roll forward operations when a Btrieve Update error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, Status Codes for a description of Status Code nn.

MKDE1211: An unexpected Btrieve error nn occurred on DELETE from xxxx.

The MicroKernel returns this message during roll forward operations when a Btrieve Delete error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, Status Codes for a description of Status Code nn.

MKDE1212: The system is out of memory.

The MicroKernel returns this message when the server has insufficient memory to allow the program to operate. Unload any unnecessary applications and retry the roll forward operation.

MKDE1213: An internal error nn occurred.

The MicroKernel returns this message when an internal error occurs. Try to perform the operation again.

Messages 2-41

MKDE1214: An unexpected Btrieve error nn occurred on GET EQUAL in xxxx.

The MicroKernel returns this message during roll forward operations when a Btrieve Get Equal error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, Status Codes for a description of Status Code nn.

MKDE1215: The log file is corrupt.

The MicroKernel returns this message when the log segment file is damaged and unreadable. The Log Segment Manager cannot perform roll forward operations using this log segment.

MKDE1216: An error occurred while reading the log file.

The MicroKernel returns this message when an error prevents the program from reading the log segment file. The MicroKernel cannot perform roll forward operations using this log segment.

MKDE1217: An unexpected Btrieve error nn occurred on CREATE INDEX to filename.

The MicroKernel returns this message during roll forward operations when an error occurs on a CREATE INDEX operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, Status Codes.

MKDE1218: An unexpected Btrieve error nn occurred on DROP INDEX to filename.

The MicroKernel returns this message during roll forward operations when an error occurs on a DROP INDEX operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, Status Codes.

MKDE1219: An unexpected Btrieve error nn occurred on BEGIN TRANSACTION to filename.

The MicroKernel returns this message during roll forward operations when an error occurs on a BEGIN TRANSACTION operation for the specified file.

2-42 Status Codes and Messages

You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, Status Codes.

MKDE1220: An unexpected Btrieve error nn occurred on END TRANSACTION to filename.

The MicroKernel returns this message during roll forward operations when an error occurs on an END TRANSACTION operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, Status Codes.

MKDE1221: An unexpected Btrieve error nn occurred on ABORT TRANSACTION to filename.

The MicroKernel returns this message during roll forward operations when an error occurs on an ABORT TRANSACTION operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, Status Codes.

MKDE1222: An unexpected Btrieve error nn occurred on CLOSE to filename.

The MicroKernel returns this message during roll forward operations when an error occurs on a CLOSE operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, Status Codes.

MKDE1223: An unexpected Btrieve error nn occurred on GET POSITION to filename.

The MicroKernel returns this message during roll forward operations when an error occurs on a GET POSITION operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, Status Codes.

MKDE1224: An unexpected Btrieve error nn occurred on BEGIN TRANSACTION.

The MicroKernel returns this message during roll forward operations when an error occurs on a BEGIN TRANSACTION operation. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, Status Codes. Messages 2-43

MKDE1225: An unexpected Btrieve error nn occurred on END TRANSACTION.

The MicroKernel returns this message during roll forward operations when an error occurs on an END TRANSACTION operation. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, Status Codes.

MKDE1226: An unexpected Btrieve error nn occurred on ABORT TRANSACTION.

The MicroKernel returns this message during roll forward operations when an error occurs on an ABORT TRANSACTION operation. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, Status Codes.

MKDE2001: The value specified for the Cache Allocation option is invalid.
The MicroKernel returns this message when the value specified for the Cache Allocation option is invalid. Use the Setup utility and specify a valid value for this option.

MKDE2002: The value specified for the Largest Compressed Record Size option is invalid.
The MicroKernel returns this message when the value specified for the Largest Compressed Record Size option is invalid. Use the Setup utility to specify a valid value for the Largest Compressed Record Size option.

MKDE2004: The value specified for the Number of Open Files option is invalid.
The MicroKernel returns this message when the value specified for the Number of Open Files option is invalid. Use the Setup utility and specify a valid value for this option.

2-44 Status Codes and Messages

MKDE2005: The value specified for the Operation Bundle Limit option is invalid.
The MicroKernel returns this message when the value specified for the Operation Bundle Limit option is invalid. Use the Setup utility and specify a valid value for this option.

MKDE2007: The value specified for the Number of Handles option is invalid.
The MicroKernel returns this message when the value specified for the Handles option is invalid. Use the Setup utility and specify a valid value for this option.

MKDE2008: The value specified for the I/O Threads option is invalid.
The MicroKernel returns this message when the value specified for the number of I/O threads option is invalid. Use the Setup utility and specify a valid value for this option.

MKDE2009: The value specified for the Active Clients option is invalid.
The MicroKernel returns this message when the value specified for the Active Clients option is invalid. Use the Setup utility and specify a valid value for this option.

MKDE2010: The value specified for the Sort Buffer Size option is invalid.
The MicroKernel returns this message when the value specified for the Sort Buffer Size option is invalid. Use the Setup utility and specify a valid value for this option.

MKDE2011: The path specified for the Temporary Directory option is invalid.
The MicroKernel returns this message when the value specified for the Temporary Work Directory option is invalid. Use the Setup utility and specify a valid path.

Messages 2-45

MKDE2012: The value specified for the option option is invalid.

The MicroKernel returns this message when the value for an option is not valid. Return to the Setup utility and enter the correct value.

MKDE2013: The option specified is not a valid option.

The MicroKernel Database Engine returns this message when the option specified is not a valid option. Return to the Setup utility and remove the invalid option.

MKDE2015: MKDE cannot get sufficient memory to complete the operation.

The MicroKernel returns this message when the server has insufficient memory to allow the MicroKernel to load as it is configured. Use the Setup utility to reconfigure the MicroKernel to use less memory, or unload any unnecessary applications.

MKDE2019: The log file filename cannot be written. Check disk space.
The MicroKernel returns this message when log file filename cannot be written. Check the disk space. If the disk is full, free some space by deleting any unnecessary files. When an error occurs while writing to the transaction log file, the MicroKernel attempts to resume transaction logging after every update to a data file containing system data. Therefore, when the condition causing the error is corrected (for example, when more disk space is made available), the MicroKernel automatically resumes transaction logging.

MKDE2024: The file filename is rolling back.

The MicroKernel returns this message when the file filename is rolling back. Rolling back is the procedure the MicroKernel uses to restore a file to a consistent state after a system crash. This procedure undoes the most recent changes to the file (changes in the most recent system transaction).

MKDE2027: Error creating/accessing semaphore.

The MicroKernel returns this message if an internal error occurs.

2-46 Status Codes and Messages

MKDE2028: Error creating execution thread.

The MicroKernel returns this message when it cannot create additional threads. Decrease the values for either the Worker Threads or the I/O Threads option.

MKDE2029: Could not open Event Log file.

The MicroKernel returns this message when it cannot create the Pervasive Event Log (PVSW.LOG) in the home directory. Make sure that the home directory exists and that the disk on your computer is not full. Also, ensure that the MicroKernel has rights to the home directory and event log file. The Home directory is defined as \WINNT\SYSTEM32 (Windows NT), \WINDOWS\SYSTEM (Windows 95), and SYS:\SYSTEM (NetWare servers).

MKDE2039: System Error: nn.nn.nn.

The MicroKernel returns this message when a system error occurs.

MKDE2053: Additional worker thread spawned.

This is an informative message the MicroKernel returns when it must create more worker threads than the number specified by the Number of Worker Threads configuration option. To avoid receiving this message, increase the value for the Number of Worker Threads option.

MKDE2055: Error creating named pipe.

The MicroKernel returns this message when it is unable to create a named pipe for the pipe-manager thread.

MKDE2060: Error reading the registry. Error code: nn.

The MicroKernel returns this message when it is unable to find a predefined setting in the registry. Use the REGINSTALL startup parameter next time you start the MicroKernel. This parameter forces the MicroKernel to recreate its section in the registry with the default values for each configuration option.

Messages 2-47

MKDE2061: Error writing the registry. Error code: nn.

The MicroKernel returns this message when it encounters an error while trying to write into the registry. Use the REGINSTALL startup parameter next time you start the MicroKernel. This parameter forces the MicroKernel to recreate its section in the registry with the default values for each configuration option.

MKDE2065: Error calling Service Control dispatcher.

The MicroKernel returns this message when it encounters an error during the service initialization.

MKDE2067: There is no suitable protocol available on this computer.

The MicroKernel returns this message when none of the supported protocols are installed on the computer. The Communications Server cannot initialize.

MKDE2068: The communications server is not available.

The MicroKernel returns this message when it encounters an error loading the Communications Server. Make sure the system path includes the directory where the Communications Server that was shipped with this version of the MicroKernel.

MKDE2075: The transaction log file LAST_SEG.LOG cannot be opened.

The MicroKernel returns this message when the log file format is invalid or the Transaction Log Directory does not exist. Ensure that the version of the MicroKernel that returns this message is the same as the version of the MicroKernel that created the log file.

MKDE2076: An Open operation failed on xxxx with Btrieve error nn.

The MicroKernel returns this message during roll forward operations when a Btrieve error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, Status Codes for a description of Status Code nn.

2-48 Status Codes and Messages

MKDE2077: The log file format is invalid.

The MicroKernel returns this message when the log segment file format is incompatible. Ensure that the version of the MicroKernel doing the roll forward is the same as the version of the MicroKernel that created the log file.

MKDE2078: An Open operation failed on xxxx with Btrieve error nn.

The MicroKernel returns this message during roll forward operations when a Btrieve error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, Status Codes for a description of Status Code nn.

MKDE2079: An unexpected Btrieve error nn occurred on INSERT to xxxx.

The MicroKernel returns this message during roll forward operations when a Btrieve Insert error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, Status Codes for a description of Status Code nn.

MKDE2080: An unexpected Btrieve error nn occurred on UPDATE in xxxx.

The MicroKernel returns this message during roll forward operations when a Btrieve Update error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, Status Codes for a description of Status Code nn.

MKDE2081: An unexpected Btrieve error nn occurred on DELETE from xxxx.

The MicroKernel returns this message during roll forward operations when a Btrieve Delete error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, Status Codes for a description of Status Code nn.

MKDE2082: The system is out of memory.

The MicroKernel returns this message when the server has insufficient memory to allow the program to operate. Unload any unnecessary applications and retry the roll forward operation. Messages 2-49

MKDE2083: An internal error nn occurred.

The MicroKernel returns this message when an internal error occurs. Try to perform the operation again.

MKDE2084: An unexpected Btrieve error nn occurred on GET EQUAL in xxxx.

The MicroKernel returns this message during roll forward operations when a Btrieve Get Equal error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, Status Codes for a description of Status Code nn.

MKDE2085: The log file is corrupt.

The MicroKernel returns this message when the log segment file is damaged and unreadable. The Log Segment Manager cannot perform roll forward operations using this log segment.

MKDE2086: An error occurred while reading the log file.

The MicroKernel returns this message when an error prevents the program from reading the log segment file. The MicroKernel cannot perform roll forward operations using this log segment.

MKDE2087: An unexpected Btrieve error nn occurred on CREATE INDEX to filename.

The MicroKernel returns this message during roll forward operations when an error occurs on a CREATE INDEX operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, Status Codes.

MKDE2088: An unexpected Btrieve error nn occurred on DROP INDEX to filename.

The MicroKernel returns this message during roll forward operations when an error occurs on a DROP INDEX operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, Status Codes.

2-50 Status Codes and Messages

MKDE2089: An unexpected Btrieve error nn occurred on BEGIN TRANSACTION to filename.

The MicroKernel returns this message during roll forward operations when an error occurs on a BEGIN TRANSACTION operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, Status Codes.

MKDE2090: An unexpected Btrieve error nn occurred on END TRANSACTION to filename.

The MicroKernel returns this message during roll forward operations when an error occurs on an END TRANSACTION operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, Status Codes.

MKDE2091: An unexpected Btrieve error nn occurred on ABORT TRANSACTION to filename.

The MicroKernel returns this message during roll forward operations when an error occurs on an ABORT TRANSACTION operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, Status Codes.

MKDE2092: An unexpected Btrieve error nn occurred on CLOSE to filename.

The MicroKernel returns this message during roll forward operations when an error occurs on a CLOSE operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, Status Codes.

MKDE2093: An unexpected Btrieve error nn occurred on GET POSITION to filename.

The MicroKernel returns this message during roll forward operations when an error occurs on a GET POSITION operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, Status Codes.

Messages 2-51

MKDE2094: An unexpected Btrieve error nn occurred on BEGIN TRANSACTION.

The MicroKernel returns this message during roll forward operations when an error occurs on a BEGIN TRANSACTION operation. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, Status Codes.

MKDE2095: An unexpected Btrieve error nn occurred on END TRANSACTION.

The MicroKernel returns this message during roll forward operations when an error occurs on an END TRANSACTION operation. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, Status Codes.

MKDE2096: An unexpected Btrieve error nn occurred on ABORT TRANSACTION.

The MicroKernel returns this message during roll forward operations when an error occurs on an ABORT TRANSACTION operation. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, Status Codes.

2-52 Status Codes and Messages

NWBSRVCM
NetWare Btrieve Server Communications Manager Messages
NWBSRVCM-4: Btrieve Communication Manager is using default settings.
The Btrieve Communications Manager displays this message when it cannot find the configuration file (BTI.CFG). It will use the default configuration settings.

NWBSRVCM-5: Btrieve Communication Manager detected an invalid command line option.

Specify a valid option.

NWBSRVCM-6: Btrieve Communication Manager terminating - could not initialize properly.

The Btrieve Communications Manager could not load the TCP/IP or SPX communication module. Verify that the configuration file (BTI.CFG) entry for Supported Protocols is correct.

NWBSRVCM-7: Btrieve Communication Manager terminating insufficient memory to execute.

An error occurred during a memory allocation operation. Free memory by unloading NLMs or reconfiguring NLMs to use less memory. Retry the operation. If the error persists, contact Pervasive Software Customer Support for more information.

NWBSRVCM-8: Btrieve Communication Manager could not load/initialize BTCPCOM.NLM.

An error occurred during the loading or initialization of BTCPCOM.NLM. The operating system error number is displayed as errno. Refer to your operating system documentation for the definition of the errno value. Messages 2-53

NWBSRVCM-9: Btrieve Communication Manager could not load/initialize BSPXCOM.NLM.

An error occurred during the loading or initialization of BSPXCOM.NLM. The operating system error number is displayed as errno. Refer to your operating system documentation for the definition of the errno value.

NWBSRVCM-10: Btrieve Communication Manager terminating - invalid Supported Protocols specified in configuration file (BTI.CFG).
Verify that the configuration file (BTI.CFG) entry for Supported Protocols is correct.

2-54 Status Codes and Messages

UCINIT
User Count Initialization Utility Messages
The following messages apply to the User Count Initialization utility.

UCINIT100: Abnormal completion, status = nn.

The User Count Initialization utility returns this message when an operating system or User Count Manager error occurs. If the specified status is -1, the error relates to the operating system. A message reflecting the system error number is displayed just above this one on the terminal. Refer to your operating system documentation for the definition of the error number value. If the specified status is in the range of 7000 to 7099, the error relates to the User Count Manager. A message with the User Count Manager error is displayed just above this one on the terminal. Refer to the User Count Manager error messages for the definition of the error.

UCINIT203: Keyboard input error.

The User Count Initialization utility displays this message when an operating system error is reported during keyboard input. Retry the keyboard input operation.

UCINIT308: The User Count Manager cannot migrate the Btrieve user count because the Btrieve file is invalid, file = %s.
The User Count Initialization utility displays this message when you try to migrate a Btrieve user count with an invalid Btrieve v6.10 database engine file (BTRIEVE.NLM).

UCINIT309: Error adding license key while migrating Btrieve v6.1x user count (UCMGR status code = nn).
The User Count Initialization utility displays this message when attempting to migrate a Btrieve v6.1x user count. For NetWare server engines, ensure that the Btrieve file is v6.10 or later. For Windows NT server engines, ensure that the Btrieve file is v6.15 or later.

Messages 2-55

UCINIT400: File does not exist, file = filename, (errno = nn).

The User Count Initialization utility displays this message when trying to access a file that does not exist. Ensure that the specified file exists and retry the operation.

UCINIT404: File open error, file = filename, (errno = nn).

The User Count Initialization utility displays this message when it cannot open the specified file. The operating system error number is displayed as errno=nn. Refer to your operating system documentation for the definition of the errno value. Ensure that your disk is not full and that you have appropriate access rights to the specified file.

UCINIT407: File read error, file = filename, (errno = nn).

The User Count Initialization utility displays this message when it cannot read from the specified file. The operating system error number is displayed as errno=nn. Refer to your operating system documentation for the definition of the errno value. Ensure that the specified file is not damaged. If the file is damaged, delete it and re-execute the utility.

UCINIT411: File seek error, file = filename, (errno = nn).

The User Count Initialization utility displays this message when it cannot seek in the specified file. The operating system error number is displayed as errno=nn. Refer to your operating system documentation for the definition of the errno value. Ensure that your disk is not full and that you have appropriate access rights to the specified file.

UCINIT503: Terminating, cannot access internal message table.

The User Count Initialization utility displays this message when it cannot access its internal message table. This message is only returned on NetWare systems. Ensure that the utility is either installed in the SYS:SYSTEM directory, or that the directory from which you loaded the utility is in your path.

2-56 Status Codes and Messages

UCMGR
User Count Manager Messages
The following messages apply to the User Count Manager.

UCMGR301: The key number used for increasing the user count is invalid.
The User Count Manager returns this message when the key number used for increasing the user count is invalid. Provide a valid key number.

UCMGR302: Invalid key file check sequence. The integrity of the user count key file has been compromised.
The User Count Manager returns this message when the integrity of UCMGR.SYS has been compromised. Reinstall SQL.

UCMGR303: Invalid key number (key number is of the wrong type).

The User Count Manager returns this message when you attempt to provide a key number that is of the wrong type. Ensure that you entered the key number correctly.

UCMGR305: Duplicate key number error. You cannot increase the user count with the same key twice.
The User Count Manager returns this message when you attempt to provide a key number that has already been used to increase the user count. Ensure that you entered the key number correctly.

UCMGR306: The diskette key has already been applied. You cannot increase the user count with the same diskette key twice.
The User Count Manager returns this message when you attempt to apply a diskette-based key that has already been applied. Ensure that you use a diskette-based key that has not been previously applied.

Messages 2-57

UCMGR307: The diskette key file is invalid, file = filename, (errno=nn)

The User Count Manager returns this message when an invalid diskette key file has been detected. Retry the operation using another diskette key file.

UCMGR310: Serial number synchronization error. Unable to find valid stamp area.
The User Count Manager returns this message when the serial numbers in SQL components do not match. Ensure that you installed SQL correctly.

UCMGR311: Serial number synchronization error. Invalid stamp area read.

The User Count Manager returns this message when the serial numbers in SQL components do not match. Ensure that you installed SQL correctly.

UCMGR312: Serial number synchronization error. One or more stamp numbers read do not match.
The User Count Manager returns this message when the serial numbers in SQL components do not match. Ensure that you installed SQL correctly.

UCMGR313: Serial number synchronization error. Could not write stamp number to one of the files. Make sure the database engine is not loaded and that you have access rights to the files.
The User Count Manager returns this message when the serial numbers in SQL components do not match. Ensure that you installed SQL correctly.

UCMGR314: Serial number synchronization error. Files have not been stamped and the user count key file exists.
The User Count Manager returns this message when the serial numbers in SQL components do not match. Ensure that you installed SQL correctly.

2-58 Status Codes and Messages

UCMGR315: Serial number synchronization error. The key file stamp number does not match the stamp number in the other files.
The User Count Manager returns this message when the serial numbers in SQL components do not match. Ensure that you installed SQL correctly.

UCMGR316: Serial number synchronization error. Files have been stamped but the user count key file does not exist. If you have made a backup copy of your user count key file (<plat>UCMGR.SYS), please restore it to the database engine directory.
The User Count Manager returns this message when the serial numbers in SQL components do not match. Ensure that you installed SQL correctly.

UCMGR317: Serial number synchronization error. During a user count migration update, could not find a valid stamp area.
The User Count Manager returns this message when the serial numbers in SQL components do not match. Ensure that you installed SQL correctly.

UCMGR318: Serial number synchronization error. During a user count migration update, an invalid stamp number was found.
The User Count Manager returns this message when the serial numbers in SQL components do not match. Ensure that you installed SQL correctly.

UCMGR319: Serial number synchronization error. During a user count migration update, one or more stamp numbers do not match.
The User Count Manager returns this message when the serial numbers in SQL components do not match. Ensure that you installed SQL correctly.

UCMGR320: Serial number synchronization error.

The User Count Manager returns this message when the serial numbers in SQL components do not match. Ensure that you installed SQL correctly.

UCMGR321: You have previously migrated xx users and have tried to migrate xx users at this time. This is an invalid operation because
Messages 2-59

the migrated user count is less than the previously migrated user count.
The User Count Manager returns this message when you attempt to migrate a number of users that is different from the number of users you previously migrated.

UCMGR401: Cannot find diskette key file, file = filename, (errno = nn).
The User Count Manager returns this message when you attempt to access a diskette-based key file that does not exist. Ensure you have a diskette-based key file and retry the operation.

UCMGR402: Invalid file pathname = path, file = filename, (errno = nn).

The User Count Manager returns this message when it determines that a file pathname is invalid. The operating system error number is specified by errno. Refer to your operating system documentation for more information about the errno number. Ensure that the pathname is correct and that you have appropriate access rights.

UCMGR403: File change mode error, file = filename, (errno=nn).

The User Count Manager returns this message when trying to change the file attributes of the specified file. The operating system error number is specified by errno. Refer to your operating system documentation for more information about the errno number. Ensure that the specified file is not already open and that you have appropriate access rights to the specified file.

UCMGR404: File open error, file = filename, (errno=nn).

The User Count Manager returns this message when trying to open the specified file. The operating system error number is specified by errno. Refer to your operating system documentation for more information about the errno number. Ensure that your disk is not full and that you have appropriate access rights to the specified file. When this error occurs, ensure that the database engine is not loaded.

In Netware, enter the following commands at the server console: mgrstop bstop

In Windows NT, enter the following command at the MKDE console:

2-60 Status Codes and Messages

SSQL_v4.0> quit

UCMGR405: Error writing to user count key file, (errno=nn).

The User Count Manager returns this message when trying to write to the user count key file (UCMGR.SYS). The operating system error number is specified by errno. Refer to your operating system documentation for more information about the errno number.

UCMGR406: Error writing to file, file = filename, (errno=nn).

The User Count Manager returns this message when trying to write to the specified file. The operating system error number is specified by errno. Refer to your operating system documentation for more information about the errno number. Ensure that your disk is not full and that you have appropriate access rights to the specified file.

UCMGR408: Error reading from user count key file, (errno=nn).

The User Count Manager returns this message when trying to read the user count key file (UCMGR.SYS). The operating system error number is specified by errno. Refer to your operating system documentation for more information about the errno number. Ensure that your disk is not damaged. If the disk is damaged, reinstall SQL.

UCMGR409: Error reading from file, file = filename, (errno=nn).

The User Count Manager returns this message when trying to read from the specified file. The operating system error number is specified by errno. Refer to your operating system documentation for more information about the errno number. Ensure that the specified file is not damaged. If the file is damaged, reinstall SQL.

UCMGR410: Unexpected end-of-file found, file = filename, (errno=nn).

The User Count Manager returns this message when trying to read the specified file. The operating system error number is specified by errno. Refer to your operating system documentation for more information about the errno number. Ensure that the specified file is not damaged. If the file is damaged, reinstall SQL.

Messages 2-61

UCMGR411: File seek error, file = filename, (errno=nn).

The User Count Manager returns this message when trying to seek in the specified file. The operating system error number is specified by errno. Refer to your operating system documentation for more information about the errno number. Ensure that your disk is not full and that you have appropriate access rights to the specified file.

UCMGR412: File delete error, file = filename, (errno=nn).

The User Count Manager returns this message when trying to unlink the specified file. The operating system error number is displayed as errno. Refer to your operating system documentation for the definition of the errno value. Ensure that you have appropriate access rights to the specified file.

UCMGR413: File rename error, file = filename, (errno=nn).

The User Count Manager returns this message when trying to rename the specified file. The operating system error number is displayed as errno. Refer to your operating system documentation for the definition of the errno value. Ensure that you have appropriate access rights to the specified file.

UCMGR415: DOS Partition Services are not present.

This message is returned only on the NetWare platform. The User Count Manager returns this message when trying to access the User Count diskette key file (UCMGR.KEY) and the DOS partition services are not present in NetWare. Reboot your NetWare server and ensure that the DOS partition services are present.

UCMGR416: DOS Copy error. The User Count Manager cannot copy the diskette key file, (errno=nn).
This message is returned only on the NetWare platform. The User Count Manager returns this message when it cannot access the User Count diskette key file (UCMGR.KEY) on NetWare. The operating system error number is displayed as errno. Refer to your operating system documentation for the definition of the errno value. Ensure you have a valid diskette-based key file and retry the operation.

2-62 Status Codes and Messages

UCMGR417: DOS Open error. The User Count Manager cannot open the diskette key file, (errno=nn).
This message is only returned on the NetWare platform. The User Count Manager returns this message when it cannot access the User Count diskette key file (UCMGR.KEY) on NetWare. The operating system error number is displayed as errno. Refer to your operating system documentation for the definition of the errno value. Ensure you have a valid diskette-based key file and retry the operation.

UCMGR418: DOS Write error. The User Count Manager cannot write to the diskette key file (errno=nn).
This message is only returned on the NetWare platform. The User Count Manager returns this message when it cannot access the User Count diskette key file (UCMGR.KEY) on NetWare. The operating system error number is displayed as errno. Refer to your operating system documentation for the definition of the errno value. Ensure you have a valid diskette-based key file and retry the operation.

UCMGR500: The User Count Manager is not initialized. Unload or stop your database engine and run the User Count Initialization utility (UCINIT.EXE, NTUCINIT.EXE, or NWUCINIT.NLM).
The User Count Manager returns this message when the manager has not been initialized prior to issuing requests for its services.

UCMGR501: The User Count Manager is busy. Only one instance of the User Count Manager can be in use at one time.
The User Count Manager returns this message when the Manager is already in use. Try to use the User Count Manager later.

UCMGR502: The User Count Manager cannot determine the platform.

The User Count Manager returns this message when it cannot determine the correct platform during an open operation. Ensure that the MicroKernel is in the target directory and retry the operation.

Messages 2-63

UCMGR503: Terminating, cannot access internal message table.

This message is returned only on the NetWare platform. The User Count Manager returns this message when it cannot access its internal message table. Ensure that the utility is either installed in the SYS:SYSTEM directory, or that the directory from which you loaded the utility is in your path.

2-64 Status Codes and Messages

UCUTIL
User Count Utility Messages
The User Count utility generates the following messages.

UCUTIL100: Abnormal completion, status = nn.

The User Count utility returns this message when an operating system or User Count Manager error occurs. To recover from this error, use the specified status number, as follows:

If the specified status code is in the range of 7000 through 7099, the error relates to the User Count Manager. A message reflecting the User Count Manager error is displayed just above this one at the console. Refer to the UCMGR messages for more information. If the specified status code is -1, the error relates to the operating system. A message reflecting the operating system error number (errno) is displayed just above this one at the console. Refer to your operating system documentation for more information about the errno number.

UCUTIL201: Invalid key number length.

The User Count utility returns this message when you enter a key number that is not 16 characters long. Ensure that you have entered the key exactly as Pervasive Software provides it.

UCUTIL203: Keyboard input error.

The User Count utility returns this message when an operating system error is reported during keyboard input. Retry the keyboard input operation.

UCUTIL204: Invalid product code.

The User Count utility returns this message when you enter an invalid product code. The product code for Btrieve is 1, and the product code for SQL is 2.

Messages 2-65

UCUTIL205: Invalid diskette drive specification.

The User Count utility returns this message when you specify an invalid diskette drive. The valid diskette drives are a: and b:.

UCUTIL400: File does not exist, file = filename, (errno = nn).

The User Count utility displays this message when trying to access a file that does not exist. Ensure that the specified file exists and retry the operation.

UCUTIL404: File open error, file = filename, (errno = nn).

The User Count utility displays this message when it cannot open the specified file. The operating system error number is displayed as errno=nn. Refer to your operating system documentation for the definition of the errno value. Ensure that your disk is not full and that you have appropriate access rights to the specified file.

UCUTIL407: File read error, file = filename, (errno = nn).

The User Count utility displays this message when it cannot read from the specified file. The operating system error number is displayed as errno=nn. Refer to your operating system documentation for the definition of the errno value. Ensure that the specified file is not damaged. If the file is damaged, delete it and re-execute the utility.

UCUTIL411: File seek error, file = filename, (errno = nn).

The User Count utility displays this message when it cannot seek in the specified file. The operating system error number is displayed as errno=nn. Refer to your operating system documentation for the definition of the errno value. Ensure that your disk is not full and that you have appropriate access rights to the specified file.

UCUTIL503: Terminating, cannot access internal message table.

This message is returned only on the NetWare platform. The User Count utility returns this message when it cannot access its internal message table. Ensure that the utility is either installed in the SYS:SYSTEM directory, or that the directory from which you loaded the utility is in your path.

2-66 Status Codes and Messages

Index
B
BDROUTER messages 2-6 BREQUEST messages 2-8 BREQUTIL messages 2-11 BROUTER messages 2-12 BSPXCOM messages 2-13 BTCPCOM messages 2-16 Btrieve Maintenance Utility Messages 2-20 Btrieve Message Router Messages 2-12 Btrieve Remote Communications Manager Messages 2-6 Btrieve Requester messages 2-8 status codes 1-67 Btrieve Router messages 2-6 Btrieve SPX Communications Module Messages 2-13 Btrieve TCP/IP Communications Manager messages 2-16 BUTIL Messages 2-20

BROUTER 2-12 BSPXCOM 2-13 BTCPCOM 2-16 BUTIL 2-20 MicroKernel Database Engine 2-29 MKDE 2-29 NWBSRVCM 2-53 Requester utility 2-11 UCINIT 2-55 UCMGR 2-57 UCUTIL 2-65 User Count Manager 2-57 utility 2-65 MicroKernel Database Engine messages 2-29 status codes 1-16, 1-62 MicroKernel Router status codes 1-81 MKDE Messages 2-29

N
NetWare Btrieve Server Communications Manager Messages 2-53 Network Services Layer status codes 1-88 NWBSRVCM messages 2-53

C
Component Management status codes 1-100

E
ECAS API status codes 1-105 Event log status codes 1-100

R
Ranges status codes 1-2 Requester Utility Messages 2-11

G
Groups, message 2-2

S
Scalable SQL status codes informative 1-3 Status Codes 0 1-15 1 to 199 1-16 1000 to 1999 1-62 -199 to -100 1-3 2000 to 2099 1-67 3000 to 3099 1-81 3100 to 3199 1-88 7000 to 7099 1-93 8000 to 8099 1-100

I
I*net Data Server MicroKernel Router status codes 1-86 PNSL status codes 1-92

M
Maintenance utility messages for Btrieve 2-20 Message Groups 2-2 Messages BDROUTER 2-6 BREQUEST 2-8, 2-11

Index 1

8500 to 8589 1-105 8590 to 8599 1-108 Btrieve Requester 1-67 Component Management 1-100 ECAS API status codes 1-105 event log 1-100 MicroKernel Database Engine 1-16, 1-62 MicroKernel Router 1-81 Network Services Layer 1-88 ranges 1-2 Scalable SQL informative 1-3 successful completion 1-15 User Count Manager 1-93 W3DBSMGR status codes 1-108 Status Codes returned by SQL engine. 1-3 Successful completion status code 1-15

U
UCINIT messages 2-55 UCMGR Messages 2-57 UCUTIL Messages 2-65 User Count Initialization Utility Messages 2-55 Manager messages 2-57 status codes 1-93 utility messages 2-65

W
W3DBSMGR status codes 1-108

2 Status Codes and Messages