Pervasive PSQL v11 Status Codes and Messages Reference for Status Codes and Messages Pervasive Software Inc. 12365 Riata Trace Parkway Building B Austin, TX 78727 USA Telephone: 512 231 6000 or 800 287 4383 Fax: 512 231 6010 Email: database@pervasive.com Web: http://www.pervasivedb.
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.
Contents About This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v Who Should Read This Manual?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manual Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Status Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables 1-1 1-2 1-3 1-4 1-5 Status Code Ranges . . SET Statements . . . . . CREATE Statements . . DROP Statements . . . DECLARE Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About This Manual This manual describes the status codes and messages you may encounter while using components of Pervasive PSQL v11. 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.
Who Should Read This Manual? This manual provides information for developers, testers, and support personnel who install and run Pervasive PSQL Server and Workgroup products. Status codes may be displayed during product installation, while using the utilities, or while using an application.
Manual Organization The following list briefly describes each chapter in the manual: Chapter 1 — Status 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.
Conventions Unless otherwise noted, command syntax, code, and examples use the following conventions: viii 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. Bold Words appearing in bold include the following: menu names, dialog box names, commands, options, buttons, statements, etc.
chapter 1 Status Codes A Reference to Pervasive PSQL Status Codes This chapter describes the status codes and messages generated by any of the components of Pervasive PSQL. 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: MKDE-16: There is insufficient memory to load the MicroKernel Database Engine.
Status Codes Table 1-1 Status Code Ranges 2000 to 2099 Btrieve Requester Status Codes 2200 to 2299 XLT Status Codes 2300 to 2399 Named Database Status Codes 3000 to 3099 MicroKernel Router Status Codes 3100 to 3199 Network Services Layer Status Codes 4000 to 4099 Database Utilities Status Codes 5000 to 5999 Encryption Status Codes 6000 to 6050 Data Dictionary Status Codes 7000 to 7050 Distributed Tuning Interface Status Codes 7064 to 7140 License Administrator Status Codes 7200 to 7499
-1000 to -5300 -1000 to -5300 SQL Relational Database Engine Status Codes This section lists status codes returned by the SQL Relational Database Engine (SRDE). Should you encounter an error code that is not listed in this section, be sure to record the steps taken to get the particular error you received and notify Technical Support at Pervasive Software. -1003: Invalid API parameter A parameter was passed to an invalid internal API.
Status Codes -1032: File access denied There was an attempt to open a file that is read only or the specified user does not have the proper rights to open the file. Record the steps taken to get this error and notify Technical Support at Pervasive Software. -1040: Too many columns defined The maximum number of columns that can be defined is 1600 in a select statement; and 1536 elsewhere. Reduce the number of columns to within a valid range and try again. -1113: Too many active sessions For Pervasive.
-1000 to -5300 -1251: Multiple columns may not be renamed to the same name When you rename multiple columns, each new name must be unique. You cannot rename two different columns to the same name. For example, the following statement causes an error because columns c1 and c3 cannot both be named c2: ALTER TABLE t1 (RENAME COLUMN c1 to c2, RENAME COLUMN c3 to c2). -1252: Column may not be renamed multiple times When you rename multiple columns, you can rename the same column only once.
Status Codes -1312: View already exists The name that you specified for a view already exists in the dictionary. Select another name or remove the current view definition and try the operation again. -1313: Trigger already exists The name that you specified for a trigger already exists in the dictionary. Select another name or remove the current view definition and try the operation again. -1314: No such table exists The name you specified for a table does not exists in the dictionary.
-1000 to -5300 -1404: No such index You tried to access an index that does not exist. Check the name and path and try again. -1504: Null not valid Null is not a valid parameter in the operation performed. -1507: No such column The column specified does not exist. Specify a correct column name. -1508: Field is already defined The field specified for this table has already been defined. -1513: Index column type not supported You cannot create an index on column types BIT, LONGVARCHAR, or LONGVARBINARY.
Status Codes You attempted to add a unique index to a column which already contains non-unique values. -1809: Permission denied The user does not have the appropriate rights for that action. Check the user permissions and try again. If this problem persists, check with your system administrator. -1810: You are not authorized to perform this operation The user does not have the appropriate rights for that action. Check the user permissions and try again.
-1000 to -5300 -1903: Invalid account name Either a user with the specified user name or a group with the specified group name does not exist. Check your user/group name and try again. If you continue to have problems, check with your system administrator. -1905: Invalid password The password specified was not correct. Check your password and try again. If you continue to have problems, check with your system administrator.
Status Codes -3005: Cannot alter a COBOL fake table. Invalid operation COBOL applications that include OCCURS, partial REDEFINES, or variable record layout can enable SQL access to the Btrieve data files by using the Cobolschemaexec utility. (The utility describes the application’s understanding of data to the Pervasive PSQL relational interface.) You cannot perform an ALTER TABLE operation on such data files. -3006: Cannot create triggers on COBOL tables.
-1000 to -5300 by using the Cobolschemaexec utility. (The utility describes the application’s understanding of data to the Pervasive PSQL relational interface.) If a main table contains any REDEFINES layouts, you must delete the REDEFINES tables before you can delete the main table. -3010: An OCCURS table with a mapping index to this index exists.
Status Codes -3014: Trigger already exists You are trying to create a trigger, but a trigger with the specified name already exists. Either use a different name, or drop the existing trigger before creating the new one. -3015: Procedure already exists You are trying to create a stored procedure, but a stored procedure with the specified name already exists. Either use a different name, or drop the existing stored procedure before creating the new one.
-1000 to -5300 -3018: Invalid data type conversion to an identity column An attempt was made to alter a data type to an identity column. -3019: Cannot drop a system table An attempt was made to drop a system table. -3020: Invalid USING path/filename The path/filename that you have specified is invalid. Specify a simple, relative path between 1-64 characters. -3021: Invalid IN DICTIONARY IN DICTIONARY is not allowed on bound databases.
Status Codes -3027: Invalid foreign key constraint name The foreign key constraint name that you have specified is invalid. Specify a name between 1-20 characters, using numerals and letters only. It must start with a letter. -3028: Invalid password The password that you have specified is invalid. See the “password” entry in the table Identifier Restrictions by Identifier Type in Advanced Operations Guide for maximum length of a password and the characters allowed.
-1000 to -5300 -3034: Type cannot be null The requested operation cannot be performed on a column definition that is nullable. -3035: Length of the foreign key is incompatible You cannot define a foreign key if the column it references has a different type or attribute. -3036: Scale of the foreign key is incompatible You cannot define a foreign key if the column it references has a different type or attribute.
Status Codes If you just tried to create the specified user, but you tried again because you are not sure if it was created, this error indicates that the user was in fact created with the first attempt. -3043: Table referenced by foreign key Cannot drop the table because it is referenced by a foreign key. -3044: Too many levels of trigger recursion A trigger cannot be recursively called more than 30 times. -3045: Index in use by foreign key Cannot drop the index because it is referred to by a foreign key.
-1000 to -5300 -3052: Dictionary already exists A dictionary with the specified name already exists in that directory. Use a different dictionary name or path. -3053: RI table does not exist There was an attempt to define referential integrity upon a table that does not exist. Check the table name and try again. -3054: Duplicate savepoint name error The specified savepoint name already exists. -3055: Only one Alternate Collating Sequence per index There can be only one ACS on a given index.
Status Codes -3062: Database has no security You tried to set security privileges on a database that was not marked secure. First, enable security on the database. -3063: Database already secured You cannot secure a database that has already been secured. -3064: Alter legacy table Cannot perform an alter table on a legacy table. -3065: Invalid login Either an invalid user name was used or the password failed. Make sure you are using the proper login information.
-1000 to -5300 -3071: Cannot revoke synonym privileges You cannot revoke privileges to a synonym; you must revoke privileges to the group the synonym refers to. -3072: Cannot grant synonym privileges You cannot grant privileges to a synonym; you must grant privileges to the group to which the synonym refers. -3073: Privileges cannot be revoked from Administrator Administrator is a default user and you cannot revoke privileges from the Administrator user name.
Status Codes -3082: DDF already bound You cannot bind a Data Dictionary File that is already bound. -3083: DDF not bound You cannot unbind a Data Dictionary File that is not bound. -3084: Shared DDF You cannot bind a database that uses shared Data Dictionary Files. -3085: Shared data file You cannot bind a database that uses shared data files. -3086: Index in use by primary key You cannot drop the index because it is referenced by a primary key.
-1000 to -5300 -3092: RI synchronization The binding information in the Data Dictionary File and data files does not match. -3093: Trigger RI conflict If a delete trigger exists on the table, a delete cascade in a foreign key is not allowed. -3094: Invalid delete rule Delete name rules or attributes are not valid. -3095: Invalid update rule Update name rules or attributes are not valid. -3096: Object in use Cannot delete a stored procedure, trigger or view while in use.
Status Codes -3359: Not allowed to bind database and change data locations at the same time See 2341: Not allowed to bind database and change data locations at the same time. -3360: Not allowed to create data dictionary and unbind database at the same time See 2340: Not allowed to create data dictionary and unbind database at the same time.
-1000 to -5300 -3367: Not allowed to unbind database and change name at the same time See 2333: Not allowed to unbind database and change name at the same time. -3368: Not allowed to bind database and change name at the same time See 2332: Not allowed to bind database and change name at the same time. -3369: Not allowed to change data dictionary location and change name at the same time See 2331: Not allowed to change data dictionary location and change name at the same time.
Status Codes -3385: Cannot create DBNAMES.CFG file See 2314: Cannot create DBNAMES.CFG file. -3386: The bound database cannot share data dictionary files See 2313: The bound database cannot share data dictionary files. -3387: The bound database cannot share table data files See 2312: The bound database cannot share table data files. -3390: The database is in use See 2309: The database is in use. -3391: The specified RI flag is invalid See 2308: The specified RI flag is invalid. -3392: Cannot open DBNAMES.
-1000 to -5300 -3397: Invalid buffer length See 2302: Invalid buffer length. -3398: The database name is invalid See 2301: The database name is invalid. -3399: No more database names are defined See 2300: No more database names are defined. -3401: Invalid column-level GRANT statement You receive this status code when you attempt to make a columnlevel GRANT statement for a right that is not supported. Only SELECT, INSERT and UPDATE are valid column level rights.
Status Codes -3485: The routing table of the Pervasive Network Services Layer is full See 3114: The routing table of the Pervasive Network Services Layer is full. -3487: Failure during receive from the target server See 3112: Failure during receive from the target server. -3488: Failure during send to the target server See 3111: Failure during send to the target server. -3489: The network layer is not connected See 3110: The network layer is not connected.
-1000 to -5300 -3495: The Pervasive Network Services Layer encountered a permission error See 3104: The Pervasive Network Services Layer encountered a permission error. -3496: Server name not found by Pervasive Network Services Layer See 3103: Server name not found by Pervasive Network Services Layer.
Status Codes -3783: The MicroKernel router encountered an internal error See 3016: The MicroKernel router encountered an internal error. -3784: The MicroKernel router encountered an initialization error See 3015: The MicroKernel router encountered an initialization error. -3785: The MicroKernel router cannot find an engine See 3014: The MicroKernel router cannot find an engine.
-1000 to -5300 -3795: The MicroKernel is not responding to the MicroKernel router See 3004: The MicroKernel is not responding to the MicroKernel router. -3796: The MicroKernel router detected an incompatible network component See 3003: The MicroKernel router detected an incompatible network component. -3797: The MicroKernel router resource DLL is unavailable See 3002: The MicroKernel router resource DLL is unavailable.
Status Codes -4002: Specified push-down filter field not found in the table COBOL applications that include OCCURS, partial REDEFINES, or variable record layout can enable SQL access to the Btrieve data files by using the Cobolschemaexec utility. (The utility describes the application’s understanding of data to the Pervasive PSQL relational interface.) A table can contain a logical expression associated with the table. Such a table filter is referred to as a “push-down filter.
-1000 to -5300 -4851: A roll forward error occurred See 148: A roll forward error occurred. -4852: The log segment is missing See 147: The log segment is missing. -4853: Duplicate sys key See 146: Duplicate system key. -4856: The MicroKernel cannot allow unauthorized access to files in a secure MicroKernel database See 143: The MicroKernel cannot allow unauthorized access to files in a secure MicroKernel database.
Status Codes -4866: More than 5 concurrent users attempted to access the same data file See 133: More than 5 concurrent users attempted to access the same data file. -4867: The file has reached its size limit See 132: The file has reached its size limit. -4869: The MicroKernel ran out of system locks See 130: The MicroKernel ran out of system locks. -4884: The file is owned by another MicroKernel engine acting as a Gateway See 116: The file is owned by another MicroKernel engine acting as a Gateway.
-1000 to -5300 -4890: The MicroKernel cannot access the archival logging configuration file See 110: The MicroKernel cannot access the archival logging configuration file. -4891: An unknown error was encountered either creating or accessing a semaphore See 109: An unknown error was encountered either creating or accessing a semaphore. -4892: The application attempted to perform a chunk operation on a pre-v6.0 file See 107: The application attempted to perform a chunk operation on a pre-v6.0 file.
Status Codes -4899: No cache buffers are available See 100: No cache buffers are available. -4902: The data buffer is too small See 97: The data buffer is too small. -4903: A communications environment error occurred See 96: A communications environment error occurred. -4904: The session is no longer valid See 95: The session is no longer valid. -4905: The application encountered a permission error See 94: The application encountered a permission error.
-1000 to -5300 -4912: The handle table is full See 87: The handle table is full. -4913: The file table is full See 86: The file table is full. -4914: File is locked See 85: The file is locked. -4915: Record is locked See 84: The record or page is locked. -4916: The MicroKernel attempted to update or delete a record that was read outside the transaction See 83: The MicroKernel attempted to update or delete a record that was read outside the transaction.
Status Codes -4923: There is a conflict on the referenced file See 76: There is a conflict on the referenced file. -4926: The RI definition is out of sync See 73: The RI definition is out of sync. -4927: The MicroKernel cannot open the RI referenced file See 72: The MicroKernel cannot open the RI referenced file. -4928: There is a violation of the RI definitions See 71: There is a violation of the RI definitions.
-1000 to -5300 -4936: The data buffer parameter specified on an Insert Extended operation is invalid See 63: The data buffer parameter specified on an Insert Extended operation is invalid. -4937: The descriptor is incorrect See 62: The descriptor is incorrect. -4938: The work space is too small See 61: The work space is too small. -4939: The specified reject count has been reached See 60: The specified reject count has been reached.
Status Codes -4946: The language interface version is invalid See 53: The language interface version is invalid. -4947: An error occurred while writing to the cache See 52: An error occurred while writing to the cache. -4948: The owner name is invalid See 51: The owner name is invalid. -4949: The file owner is already set See 50: The file owner is already set. -4950: The extended key type is invalid See 49: The extended key type is invalid.
-1000 to -5300 -4957: A file previously opened in Accelerated mode was not closed See 42: A file previously opened in Accelerated mode was not closed. -4958: The MicroKernel does not allow the attempted operation See 41: The MicroKernel does not allow the attempted operation. -4959: The file access request exceeds the maximum number of files allowed See 40: The file access request exceeds the maximum number of files allowed.
Status Codes -4967: The file cannot be extended See 32: The file cannot be extended. -4968: The file is already extended See 31: The file is already extended. -4969: The file specified is not a MicroKernel file See 30: The file specified is not a MicroKernel file. -4970: The key length is invalid See 29: The key length is invalid. -4971: The record length is invalid See 28: The record length is invalid. -4972: The key position is invalid See 27: The key position is invalid.
-1000 to -5300 -4978: The key buffer parameter is too short See 21: The key buffer parameter is too short. -4979: The MicroKernel or Btrieve Requester is inactive See 20: The MicroKernel or Btrieve Requester is inactive. -4980: The application encountered an unrecoverable error See 19: The application encountered an unrecoverable error. -4981: The disk is full See 18: The disk is full. -4983: The application encountered an expansion error See 16: The application encountered an expansion error.
Status Codes -4989: The key field is not modifiable See 10: The key field is not modifiable. -4990: The operation encountered the end-of-file See 9: The operation encountered the end-of-file. -4991: The current positioning is invalid See 8: The current positioning is invalid. -4992: The key number has changed See 7: The key number has changed. -4993: The key number parameter is invalid See 6: The key number parameter is invalid.
-1000 to -5300 -4998: The operation parameter is invalid See 1: The operation parameter is invalid. -5022: Columns in the selection list and the returns clause do not match The number and type of columns specified in the selection list must match the number and type of columns in the RETURNS clause.
Status Codes CREATE FUNCTION myfunc(:a INT DEFAULT myfunc(1)) RETURNS INTEGER AS BEGIN RETURN :a; END; -5032: RETURN statements in a UDF must have an argument The RETURN statement within a user-defined function (UDF) must specify an argument because a UDF always returns a value.
-1000 to -5300 -5202: Record is locked An attempt was made to access a record that is locked by another user. Wait until the record is unlocked and try again. -5204: Table is not open The MicroKernel was unable to open the table. Make sure you have the proper access rights and table privileges. -5208: Invalid date The format used for the date is incorrect. Check for the correct ODBC date format and try again.
Status Codes -5225: Cannot drop an in-built function or an aggregate function You cannot delete an aggregate function or a pre-defined scalar function. The aggregate functions include COUNT, AVG, SUM, MAX, MIN, and DISTINCT. For a discussion of the scalar functions, see Scalar Functions in SQL Engine Reference. -5226: Cannot invoke a user-defined function using CALL statement You cannot invoke a user-defined function (UDF) with a CALL statement. You must use a SELECT statement to invoke a UDF.
-1000 to -5300 index name: ALTER INDEX RENAME database1:table1:index1 TO index2. However, the following statement causes an error because a view name can be qualified only with a database name: ALTER VIEW RENAME database1:table1:view1 to view2. A permissible statement is ALTER VIEW RENAME database1:view1 to view2 or ALTER VIEW RENAME view1 to view2.
Status Codes -100 to -199 Informative Status Codes This section lists the informative status codes that the MicroKernel can return. The MicroKernel returns these codes as negative values. -101: The SET statement completed successfully The following statements return this status code when they execute successfully: Table 1-2 SET Statements SET SECURITY SET OWNER SET VARIABLE SET ROWCOUNT SET TIME ZONE SET DECIMALSEPAR ATORCOMMA SET TRUENULLCREATE The MicroKernel made the requested change.
-100 to -199 -105: The CREATE statement completed successfully The following statements return this status code when they execute successfully: Table 1-3 CREATE Statements CREATE PROCEDURE CREATE TABLE CREATE GROUP CREATE TRIGGER CREATE INDEX CREATE VIEW The MicroKernel successfully added the group, index, stored procedure, table, trigger, or view to the data dictionary.
Status Codes application allows substitution variables, refer to the documentation included with the application to determine how to use them. -109: The view contains no more records The beginning or the end of the view has been reached. -110: The GRANT statement completed successfully The MicroKernel assigned the specified rights to the user or group. -111: The REVOKE statement completed successfully The MicroKernel revoked the specified rights from the user or group.
-100 to -199 Operations that create or change dictionary definitions. Therefore, you cannot roll back the results of the following statements: ALTER TABLE, 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 GROUP, DROP INDEX, DROP PROCEDURE, DROP TABLE, DROP TRIGGER, and DROP VIEW. Operations that grant or revoke security rights.
Status Codes If you issued a DECLARE statement, the MicroKernel successfully created the cursor, variable, or condition you defined. -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.
0 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 nonzero status code is returned.
Status Codes 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 operation does not exist or is not valid. You may receive this error if you are running a general-release version of the V8 client software against a pre-release version of the V8 database engine. If this is the case, you must uninstall your database engine and install the general release version.
1 to 199 Note Please see the Pervasive PSQL Knowledge Base for new and updated articles on troubleshooting this status code. You can access the Knowledge Base at the Pervasive Software website. 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.
Status Codes 6: The key number parameter is invalid The value stored in the key number parameter is not valid for the file being accessed. The key number must correspond to one of the keys defined for the file. Valid key numbers are 0 through 118. 7: The key number has changed The key number parameter changed before a Get Next, Get Next Extended, Get Previous, or Get Previous Extended operation.
1 to 199 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.
Status Codes 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 client configuration settings for Local MicroKernel Engine and Use Remote MicroKernel Engine are incorrectly set to On and Off, respectively.
1 to 199 LSL.COM LAN Card Driver IPXODI.COM IFSHLP.SYS NET START FULL These can be loaded high, using emm386. NET START FULL will load in upper memory. You attempted to open a file with a long filename on NSS volumes. The MicroKernel queries the volumes using OS calls and then loads the appropriate drivers for the associated name spaces it find for the volumes.
Status Codes 1-60 When accessing a file on a server, ensure that you have FILE SCAN rights to the directory in which the file resides. Occasionally, a corrupt key can cause this status code. Drop the key, then add it again. This error code may also be returned when the file DBNames.CFG has been removed (for example, by the Pervasive PSQL cleanup utility) and old Data Source Names (DSNs) which reference that file are not removed from the ODBC configuration.
1 to 199 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. An extended file can consist of a base file and up to 31 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.
Status Codes 16: The application encountered an expansion error This status code is obsolete in MicroKernel versions 6.0 and later. The MicroKernel encountered 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.
1 to 199 20: The MicroKernel or Btrieve Requester is inactive Note For an expanded list of possible recovery solutions, consult the Pervasive PSQL Knowledge Base at the Pervasive Software website. If you are running an application in a client/server environment: Make sure the Btrieve requester is loaded. Verify that the IPX/SPX or TCP/IP protocol is properly installed at the client machine and that no two machines on the network have the same Internal Network Number.
Status Codes Make sure the Windows DLLs are in your path. Make sure 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.
1 to 199 A corrupt file may be indicated if the file allows variable-length records and you receive this status code on a Get or Step operation. In such a corrupt file, you can receive Status Code 54 when you use Get or Step operations to read other records. Recover the file according to the instructions in Pervasive PSQL User's Guide. 23: The position block parameter is not 128 bytes long This status code is obsolete in Btrieve language interface versions 6.0 and later.
Status Codes Note This happens when the Operating system returns an unusual status code to the engine. Normally, the engine expects either a success or the file already exists. In one situation, the error code was being returned because the file handle that the engine was using was not functional; however, the OS call that the engine makes is supposed to return a file handle. One solution is to disable the Antivirus software.
1 to 199 Page Size (bytes) 16,384 1 Maximum Key Segments by File Version 8.x and prior 9.0 9.5 n/a1 n/a1 119 or 4203 ”n/a” stands for “not applicable” 2”rounded up” means that the page size is rounded up to the next size supported by the file version. For example, 512 is rounded up to 1,024, 2,560 is rounded up to 4,096, and so forth. 3 The maximum number of index segments that can be used with the relational interface is 119.
Status Codes Nullable Columns Note that nullable columns must also be considered. For example, in a data files with 4096 byte page size you are limited to 119 index segments per file. Because each indexed nullable column with true null support requires an index consisting of 2 segments, you cannot have more than 59 indexed nullable columns in a table (or indexed nullable true null fields in a Btrieve file). This limit is smaller for smaller page sizes. Any file created with file version set to 7.
1 to 199 The length of the entire key (all segments) is so large that less than 4 keys fit on a key page. For example, a 200 byte key on a 512 byte page. A key segment length is 0 or greater than 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 four keys.
Status Codes 30: The file specified is not a MicroKernel file This status code is returned in one of the following situations: The MicroKernel did not create the file, or a pre-v3.x MicroKernel created it. While using an earlier version of Btrieve, you opened a file created by a later version that has a format incompatible with the earlier version. The first page of the file may be damaged. Use a backup copy of your data file.
1 to 199 33: The MicroKernel cannot unload In the DOS environment, The MicroKernel returns this status code for the following 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.
Status Codes 39: A Begin Transaction operation must precede an End/ Abort Transaction operation The application issued an End Transaction (20),or Abort Transaction (21) operation without a corresponding Begin Transaction (19 or 1019) 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.
1 to 199 Either the application tried to open a v5.x data file that was previously accessed in Accelerated mode by a v5.x MicroKernel and never successfully closed, or the application tried to open a file for which a v6.0 or later MicroKernel encountered an unrecoverable error during a Set or Clear Owner operation. The file integrity cannot be ensured. Refer to Advanced Operations Guide for information about recovering damaged files. Your application tried to open a file in MicroKernel v5.
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 Alternate Collating Sequence (ACS) for two or more segments of a segmented key.
1 to 199 48: The alternate collating sequence definition is invalid The MicroKernel returns this status code for the following reasons: The first byte of an Alternate Collating Sequence (ACS) definition (the identification byte) does not contain the hexadecimal value AC (for user-defined ACSs), AD (for localespecific ACSs), or AE (for international sorting rules support). Make sure that the first byte contains the appropriate value. You set the Create File Version option to v5.
Status Codes ³ To change the Create File Version setting: 1 Start Pervasive PSQL Control Center (see Starting PCC on Windows in Pervasive PSQL User's Guide). 2 Expand Engines and find the desired engine name. 3 Right-click on the engine name and click Properties. 4 Click Compatibility. 5 In the right hand frame, adjust the Create File Version. 50: The file owner is already set The application tried to perform a Set Owner operation on a file that already has an owner.
1 to 199 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. 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.
Status Codes 58: The compression buffer length is too short This status code is obsolete in Pervasive.SQL 2000i and later versions. 59: The specified file already exists During a Create operation, 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.
1 to 199 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 Pervasive PSQL Explorer 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 is inconsistent either internally or with respect to the data buffer length. ActiveX control's buffers are not cleared and reallocated.
Status Codes 64: The filter limit has been reached The MicroKernel returns this status code for 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.
1 to 199 67: The MicroKernel cannot open the SQL data dictionary files The MicroKernel returns this status code for the following reasons: An application attempted to use a data file that is bound to a the MicroKernel database, but the MicroKernel could not open one of the MicroKernel data dictionary files (FILE.DDF or, if the file has RI definitions, RELATE.DDF) or the configuration file (DBNAMES.CFG).
Status Codes 71: There is a violation of the RI definitions If you attempted an Insert operation on a file under RI control, 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.
1 to 199 You attempted to modify a bound file, and the RI definition for that file disagrees with the definition in the RELATE.DDF file. You attempted an Insert, Delete, or 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 MicroKernel data file with the same name and location already exists.
Status Codes The application is currently processing a wait transaction and tried to access a file that another user has locked. When you are using the Btrieve Requester to access the MicroKernel, the Requester waits and retries if a requested resource is locked. When a server-based application is accessing the MicroKernel and the requested resource is locked, a wait is also required. In this case, the MicroKernel is expected to perform the wait.
1 to 199 81: The MicroKernel encountered a lock error The MicroKernel returns this status code in one of the following situations: The application tried to unlock a record that is locked with a multiple record lock, but the record position stored in the data buffer does not correspond to any record locked in the associated file. The application tried to unlock a single-record lock with a multiple-record lock or vice-versa.
Status Codes 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. Note Applications should limit the number of retry attempts when status 84 is received inside a concurrent transaction. Otherwise, the application might enter a deadlock situation with another transaction.
1 to 199 Without any pattern of occurrence, you may receive a status 85 when the file is closed because Anti-Virus software opens and locks the file to scan causing the next database operation to fail. To resolve, set the Anti-Virus software to not scan Pervasive PSQL data files. Consult your Anti-Virus software manual for instructions on how to exclude files. A delete action was attempted on a data file that is in continuous operations.
Status Codes To configure your operating system to allow more handles, refer to your operating system documentation. It is helpful to know the following details regarding the MicroKernel 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.
1 to 199 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. The files were previously in continuous operation and the server crashed.
Status Codes 90: The redirected device table is full This status code is obsolete in MicroKernel versions 6.0 and later. The DOS Requester 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.
1 to 199 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. ³ To adjust the Receive Packet Size: 1 Access the server properties in PCC (see To access configuration settings in PCC for a local client in Advanced Operations Guide. 2 Click Communication Buffer Size in the properties tree.
Status Codes 95: The session is no longer valid Note Please see our Pervasive PSQL Knowledge Base for new and updated articles on troubleshooting this status code. You can access the Knowledge Base at the Pervasive Software website. The server MicroKernel returns this status code for one of the following reasons: The previously established session is no longer active due to an error at the client machine, at the server, or on the network.
1 to 199 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 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.
Status Codes An application that calls the MicroKernel can return this status code if the DBNAMES.CFG file contains a named database definition specifying a data location on a different server.
1 to 199 If you are a developer, you can modify your application to commit transactions more frequently, so that fewer modified pages remain in cache. The more common approach to this problem is to increase Cache Allocation Size in the configuration options and then reload the MicroKernel. On Windows, the first time the database engine starts it initializes the cache allocation size to 20% of physical memory and writes that value to the Windows Registry.
Status Codes 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.
1 to 199 106: The MicroKernel cannot perform a Get Next Chunk operation An application called the Get Direct/Chunk operation to retrieve a chunk from a record and used the next-in-record bias on the descriptor subfunction. However, after the application established its positioning in the record (and prior to this call), the target record was deleted. 107: The application attempted to perform a chunk operation on a pre-v6.
Status Codes 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. 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.
1 to 199 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.
Status Codes You may have attempted to open a file with two different Workgroup engines that are mapped to the files using different share names. The MicroKernel attempts to correct this, but cannot do so in all cases. Make sure each computer is mapping to the same share name. 120: Maximum number of B-Tree index levels reached This status code may result if you use a large key size for an index and small page sizes.
1 to 199 132: The file has reached its size limit The MicroKernel returns this status code in one of the following situations: The MicroKernel returns this status code in one of the following situations: The file size reached its maximum limit. This limit depends on the file version, the page size, and the number of records per page. See File Size in Advanced Operations Guide for a complete discussion.
Status Codes 135: The specified ISR table is corrupt or otherwise invalid The MicroKernel 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 Alternate Collating Sequence (ACS), but the MicroKernel cannot locate an ACS with the specified name in the file.
1 to 199 You issued a Start Extended operation with an invalid key number. 143: The MicroKernel cannot allow unauthorized access to files in a secure MicroKernel database You attempted to open a data file bound to a MicroKernel database that has security enabled. The MicroKernel does not allow access to such files, except through the MicroKernel.
Status Codes 149: SQL Trigger While using the Btrieve API to alter database tables or entries, the system encountered SQL restrictions placed on the database by the SQL layer. 151: Chunk Offset Too Small You cannot insert or delete chunks within the fixed portion of a record.
1 to 199 For more information about purchasing and installing additional user counts, refer to Getting Started With Pervasive PSQL. You can use Monitor to determine which users currently have connections to Pervasive PSQL. For information about Monitor, refer to Advanced Operations Guide. You may also receive this status code if your machine configuration changed since you authorized Pervasive PSQL.
Status Codes 171: Database login failed Authentication to the database failed due to a wrong or missing password. 172: Database name not found Specify a valid database name for the machine. 173: Already logged in A Btrieve login request failed because the client is already logged into the specified database. 174: Logout failed A logout can fail if you are not logged in to a database or there are remaining open file handles to the database when the logout is attempted.
1000 to 1999 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.
Status Codes 1006: The pre-image buffer parameter is out of range In Pervasive.SQL 2000i and later versions, the setting Extended Operation Buffer Size is obsolete. This resource is managed dynamically by the MicroKernel. The Extended Operation Buffer Size configuration option must be between 0 and 64,000, inclusive. 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.
1000 to 1999 1011: The compression buffer parameter is out of range This status code is obsolete in MicroKernel versions 7.0 and later. Ensure that Compression Buffer Size option is set to a valid range. Check the target server configuration settings. Refer to Advanced Operations 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.
Status Codes 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.
1000 to 1999 1021: The MicroKernel failed to initialize The MicroKernel could not complete its initialization tasks. Check the MicroKernel console or error log for a message that specifies the problem that prevented the MicroKernel from initializing. 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.
Status Codes 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.
2000 to 2099 2012: The Btrieve requester encountered an operating system error Check the Pervasive Event Log (PVSW.LOG) for more information.
Status Codes 2200 to 2299 XLT Status Codes This section lists the XLT status codes you can receive. 2200: XLT Winsock Error This status code is returned when a Windows Socket initialization error occurs. 2201: XLT RPC Error This status code is returned when the MicroKernel cannot establish a Remote Procedure Call (RPC) to the SQL Relational Database Engine (SRDE).
2300 to 2399 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 PSQL v11 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.
Status Codes 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 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.
2300 to 2399 Administrator and specifying a data path to the DDF directory. Deleting the MicroKernel Router key resolved the problem. 2308: The specified RI flag is invalid While creating a database, you specified a RI flag that is not valid. Specify a database type of either integrity or non-integrity. 2309: The database is in use You cannot modify the definition of a named database if another user is modifying the definition or if a user is connected to it.
Status Codes before creating the bound, named database. For more information about bound databases, refer to Advanced Operations Guide. 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.
2300 to 2399 being bound. Make sure that you restore your data from a backup that is consistent with the bound state of the database. 2330: Data file for a table is bound, but does not need to be bound An unbound, named database was 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.
Status Codes 2335: Not allowed to change data locations and change name at the same time These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately. 2336: Not allowed to change data dictionary location and bind database at the same time These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.
2300 to 2399 2342: Not allowed to unbind database and change data locations at the same time These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately. 2343: Named database general error Unspecified error.
Status Codes 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.
3000 to 3099 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.
Status Codes access a local file on a client and you do not have a Workgroup engine installed or if you try to access a local file on a server and the 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 (for clients and workstations only): 1 Start Pervasive PSQL Control Center (see Starting PCC on Windows in Pervasive PSQL User's Guide).
3000 to 3099 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.
Status Codes 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 machine 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.
3000 to 3099 To use the Linux requester to connect to a Pervasive.SQL V8 server, you must have Service Pack 1 or higher. 3032: Failed to initialize shared memory to local engine This status code results if a second user attempts to access another user's database engine through the transactional interface. The application is unable to connect to the local engine. Possibly a database engine has been started by another user on the machine in a non-elevated mode.
Status Codes 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.
3100 to 3199 Communication protocols option for both the client and server. For more information on Communication protocols, refer to Advanced Operations 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 MicroKernel is not running on the server. The network is overloaded.
Status Codes 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. Note If there is a problem with AutoReconnect, a further status code 3131 will be issued.
3100 to 3199 3115: Pervasive Network Services Layer encountered a transport failure The Pervasive Network Services Layer encountered a socket error while creating the local transport endpoint on the client side. Check the Pervasive Event Log (PVSW.LOG) for more information. 3119: No authentication context is available NSL was unable to return the access context on the specified session for the supplied object.
Status Codes 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 and path. 3131: Pervasive Network Services Layer encountered an error while reconnecting This status code means that AutoReconnect was unsuccessful. The following messages will appear in PVSW.LOG: “3131: Reconnect failed. Client and Server Message IDs out of synchronization.
3100 to 3199 for and uninstall Scalable SQL (or Pervasive.SQL 7), and/or all if its components.
Status Codes 4000 to 4099 Database Utilities Status Codes This section lists the status codes you can receive when using the Database Utilities (DBU). 4083: Component not loaded If you receive this status code while attempting to start the Pervasive PSQL Transactional or Relational Services, you are missing a key file. To resolve this problem, uninstall Pervasive PSQL v11 and reinstall it.
4000 to 4099 5 In the right hand frame, adjust the Supported Protocols list as appropriate to your network environment. 6 Restart the engines for the new settings to take effect. 7 Ensure that each client workstation that accesses the database server has at least one Supported Protocol in common with the server, or else the clients cannot communicate with the server.
Status Codes 5000 to 5999 Encryption Status Codes This section lists status codes you can receive when using the Wire Encryption feature. In Advanced Operations Guide, see Pervasive PSQL Security for more information about the Wire Encryption feature and other Pervasive PSQL security topics.
5000 to 5999 You can also use the bcfg command-line utility (see Configuration Through CLI Utility in Advanced Operations Guide).
Status Codes 6000 to 6050 Data Dictionary This section lists the status codes that pertain to the data dictionary files. These codes often relate to errors involving referential integrity. Status Codes 6002: Invalid Column The column name cannot be used. The name may contain invalid characters or the name may be a duplicate name. See Naming Conventions in the online Pervasive PSQL Programmer's Guide, which is part of the Pervasive PSQL Software Developer’s Kit (SDK).
6000 to 6050 The number of index segments that you may use depends on the file’s page size. Page Size (bytes) Maximum Key Segments by File Version 8.x and prior 512 9.0 9.
Status Codes Programmer's Guide, which is part of the Pervasive PSQL Software Developer’s Kit (SDK).
7000 to 7050 7000 to 7050 Distributed This section lists the status codes you can receive when using the Distributed Tuning Interface. See Btrieve API Guide for more Tuning Interface Status information on this interface. Codes 7001: Invalid connection handle specified Specify a valid connection handle with the API call. 7002: NULL pointer specified Specify a valid pointer with the API call. 7003: Buffer was too small Increase the buffer size. Some APIs report the required size in an out parameter.
Status Codes 7008: Invalid sequence number Specify a valid sequence number for the operation. 7009: Data on open files is not available Data related to open files is not currently available. 7010: Client ID is invalid The client ID needed for this operation is invalid. Specify a valid client ID. 7011: Insufficient access rights You have insufficient access rights to perform the operation requested. Many DTI functions require administrative rights on the server.
7000 to 7050 7017: Dictionary path in use Another process has the dictionary files in use. Close all other running applications and retry the operation. 7018: Invalid DSN name The DSN you are trying to create contains invalid characters or is too long. DSN names cannot be longer than 20 characters and cannot contain the following symbols: []{}() ?*=!@,; 7019: DSN already exists The DSN you are trying to create already exists. Specify a different name for the DSN.
Status Codes 7025: Server name not found The server you specified cannot be found. Check the server name and try again. 7026: Requester not loaded The connection could not be established because the client requester is not loaded. 7027: Server table full The connection could not be established because the internal server name table is full. 7028: Client connections limit exceeded The number of client connections for DTI is limited to 100.
7000 to 7050 7033: Connection was lost The remote connection to the server was lost. If this error persists, check your network configuration. 7034: Database name is too long The database name you specified exceeds the length limit. In Advanced Operations Guide, see Pervasive PSQL Database Concepts for information on valid database names. 7035: Insufficient number of data paths When copying a database, you specified a smaller number of data paths than the original database contained.
Status Codes 7041:Cannot perform operation because database entries in FILE.DDF contain absolute paths You cannot perform the requested function because the database contains absolute paths in FILE.DDF. To resolve this issue, remove the absolute paths from the database and try again. 7042: Bound database requires data dictionary files The creation of a bound database requires data dictionary files (DDFs).
7000 to 7050 the Create Database dialog within Pervasive PSQL Control Center. See New Database GUI Reference in Pervasive PSQL User's Guide.
Status Codes 7064 to 7140 License Administrator Status Codes This section lists the status codes you can receive when using the License Administrator. 7064: No license obtained for the product This means that the Pervasive PSQL client tried to release a license (one user count, in this instance) but the client either had not acquired a license (one user count) from the server or had acquired a license for a different product.
7064 to 7140 7108: License key length is too long The length of the license key you attempted to apply exceeds the maximum length allowed for a key (24 characters). Ensure that the license key contains 24 characters. 7109: No such license exists The license key you are trying to remove does not exist. The license key may have already been removed. If you are using the License Administrator GUI to remove the key, press F5 or click Refresh to redisplay the list of applied licenses.
Status Codes still does not appear in the list, exit then restart License Administrator. 7113: Invalid license key. Verify the provided key The license key you attempted to apply is not a valid license. Ensure that you have a valid license key issued by Pervasive Software or by your application vendor if the Pervasive PSQL database engine is embedded in an application.
7064 to 7140 You may have started the License Administrator on a client where a database engine is not installed. Click OK to establish a connection to a server. The server is not running. Follow the steps in Verifying Database Engine is Running in Getting Started With Pervasive PSQL to ensure the server is running. Network communications are preventing connection to the server. Use the ping command to the server to verify that network communications are working.
Status Codes 7124: A User Count Increase cannot be applied without a permanent license The machine on which you are attempting to apply a user count increase does not contain a permanent license key. You may not apply a user count increase without a permanent license. Apply a permanent license key prior to applying a user count increase.
7064 to 7140 Make sure that the key you are using is correct and that you have the correct Pervasive PSQL product installed. 7131: The OS platform for this key does not match the installed PSQL engine The operating system associated with the key you are trying to apply does not match the Pervasive PSQL product currently installed. Make sure that the key you are using is correct and that you have the correct Pervasive PSQL product installed.
Status Codes 7200 to 7499 Authorization Status Codes This section lists the status codes you can receive when authorizing your product. 7201: An error in one of the authorization libraries prevents further processing One of the authorization libraries has produced an error that prevents further processing. Try restarting the services or reinstalling Pervasive PSQL and try authorization again. If this error persists, check the log file to determine the library name reported and contact Pervasive Support.
7200 to 7499 7218: An error occurred acquiring the machine configuration The system encountered an error while trying to acquire the machine configuration. Ensure that you are logged on as an Administrator with full access rights and try again to apply or delete the key. If you are using the Vista operating system, turn off UAC. If you are trying to apply or delete a key remotely, try the operation locally.
Status Codes 7224: User lacks the appropriate rights to apply or delete a key The target engine tests for appropriate permissions prior to apply or delete a key. Target engine testing failed due to inappropriate permissions. Ensure that you are logged on as a user with Administrator permissions and try again to apply or delete the key. If authorizing on terminal services check the registry key under HKLM\Software\Pervasive Software that restricts WTS usage.
7200 to 7499 The registry information for the authorization server may be corrupt or missing on your machine. A network problem is preventing connection to the authorization server. Security issues, such as firewall protection, are preventing connection to the authorization server. If the problem persists, contact Pervasive PSQL Customer Support. 7241: Authorization service support files not found This status code applies only to Linux.
Status Codes 7262: Error encountered while loading the offline authorization key data file An internal error occurred while loading the offline file of authorization key data. Make sure that the directory has appropriate permissions and the target folder exists. Try loading the offline file again. 7264: Product key is invalid The product key entered is invalid. Type or paste a valid product key and try again.
7200 to 7499 7305: Product key not found in authorization database The product key appears to be valid and has a valid checksum but cannot be found in the authorization database on the remote authorization server. Ensure that the product key is valid. If it is, and this problem persists, contact Pervasive PSQL Customer Support. 7306: Product key is not in a valid state The system is unable to decrypt the key because the key state is invalid.
Status Codes 7317: Deleting a key requires an applied key Deletion cannot occur because no key is available. A product key must be applied before it can be deleted. Ensure that the product key you want to delete has been applied. The key may have been removed without first being deleted. With License Administrator, verify the key that you want to delete. See To Refresh the License Information List and To Display All Applied Licenses, both in Pervasive PSQL User's Guide.
7200 to 7499 7341: Product key cannot be applied because maximum authorizations have been reached The product key has already been applied the maximum number of times allowed. Product keys have limited number of times they can can applied and deleted. Contact Pervasive PSQL Customer Support if you need to apply the product key again. 7342: Product key cannot be deleted because maximum deauthorizations have been reached The product key has already been deleted the maximum number of times allowed.
Status Codes 7347: Maximum number of offline authorizations has been reached The maximum number of offline authorizations allowed for the product key has been met. Product keys have limited number of recoveries allowed. Contact Pervasive PSQL Customer Support if you need to recover the product key again. 7348: Temporary License key cannot be deleted Temporary (non-removable) license keys may be applied only once and cannot be deleted.
7200 to 7499 7369: The server is currently unavailable. Please try again later. The requested server is inaccessible at this time. Try accessing the server again in 20-30 minutes. 7380: The Country or City is in the embargo list The system detected an IP address from a country or city that is on the restricted embargo list. Please contact Pervasive Software Customer Support if you feel you reached this message in error. 7422: Login failed. The user credentials are invalid.
Status Codes 7456: Invalid OEM user ID for the requested record The record you are trying to access has a different OEM user ID associated with it than the OEM user ID currently logged in. Make sure that you are accessing the correct record, or that the OEM user ID logged in is correct. 7457: OEM product (Workgroup/Server) is not an authorized product Products are authorized to OEMs based on their contractual agreement with Pervasive Software. The requested product is not authorized for the current OEM.
7200 to 7499 7473: Maximum number of seats for this OEM account has been reached The total maximum number of seats has been met. Accounts within an OEM have a limited number of seats based on their contract with Pervasive Software. Contact Pervasive Software if you need to add seats to the account. 7474: Maximum number of licenses for this OEM account has been reached The total maximum number of licenses has been met.
Status Codes 8000 to 8499 Component Management Status Codes These status codes originate from the Component Management and Event Logging interface of the MicroKernel. 8005: Interface not initialized An interface was not initialized properly. Check the Pervasive Event Log (PVSW.LOG) for more information. 8006: The specified component was not found The component could not be found. Check the Pervasive Event Log (PVSW.LOG) for more information.
8500 to 8589 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.
Status Codes 8505: An initialization error occurred when trying to establish a session with the Workgroup engine In its attempt to auto-load the Workgroup engine, the application failed to establish the session with the Workgroup engine. This is a system error. Some customers who have only Server engines in their environment have reported frequent pairs of Status Code 8505 and 8517 in the PVSW.LOG file on one or more client workstations.
8500 to 8589 8508: An error occurred when attempting to enable Btrieve access The application failed to enable the Btrieve access method in the Workgroup engine. 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 Workgroup engine. Check the Pervasive Event Log (PVSW.log) for more information.
Status Codes 8514: An error occurred when unloading the MicroKernel The application failed to unload the MicroKernel. 8515: An error occurred when disabling SQL access The application failed to disable the SQL access method. 8516: An error occurred when unloading the Scalable SQL engine This status code is obsolete in Pervasive.SQL 2000 and later versions. The application failed to unload Scalable SQL.
8500 to 8589 5 Restart the engines for the new settings to take effect. 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 8590 to 8599 W3DBSMGR Status Codes This section describes the status codes returned by the W3DBSMGR component. 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 Components Manager This error occurs when W3DBSMGR.
8590 to 8599 8594: Engine cannot be restarted The Workgroup 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 10000 to 10100 SQL This section lists status codes returned by the SQL Connection Manager. Connection Manager Codes 10000 through 10064: You have been unexpectedly disconnected from the server Re-start your application, then access the data source again. Contact your system administrator if you continue to have problems. 10065: Connection attempt timed out The SQL Connection Manager may be inactive or using a different transport protocol from the client.
chapter 2 Messages A Reference to Pervasive PSQL Messages This chapter describes the messages that can be returned to Pervasive PSQL users. 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 PSQL distribution. Messages are not the same as status codes (see Chapter 1—Status Codes.).
Messages Table 2-1 Message Groups 2-2 MKDE MicroKernel Database Engine Messages REBUILD Rebuild Utility Messages
(No prefix) (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. Column level permissions not allowed on views Permissions for individual columns of a view are not supported.
Messages Invalid Load File Format. End of Record Marker Not Found The Maintenance utility (BUTIL) encountered an invalid record terminator in the sequential load file. The 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. Local Engine Is Already Loaded The Pervasive.
(No prefix) Specifying SELECT, INSERT, UPDATE, DELETE or REFERENCES privilege for a Procedure is illegal Stored procedures permissions do not include SELECT, INSERT, UPDATE, DELETE or REFERENCES. 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.
Messages BREQUTIL Requester Utility Messages This section lists the messages that the SQL and MKDE Requester utilities generate. BREQUTIL-8: MicroKernel or MKDE Requester is not loaded You must load the MicroKernel or a MKDE Requester before you can perform a MKDE operation. BREQUTIL-9: MKDE operation nn was unsuccessful. The number of the applicable MKDE status code is nn Refer to Chapter 1, Status Codes for a description of Status Code nn, where nn is the number of the status code.
BROUTER BROUTER Message Router Messages The following messages are specific to the BROUTER Remote Communications Manager. BROUTER-2: The value specified for a configuration option is invalid Reload BROUTER.NLM using valid configuration options. BROUTER-3: 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.
Messages BUTIL Maintenance Utility Messages The following messages are specific to the Maintenance utility. BUTIL-1: 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. BUTIL-2: 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.
BUTIL BUTIL-11: The command line requires the index file If you specify the BUTIL -INDEX or -SAVE command (modified by the Y parameter) to the Maintenance utility, you must specify the full pathname of an external index file. BUTIL-12: The command line requires the key number If you specify the DROP command or the SAVE command (modified by the N parameter) to the 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.
Messages BUTIL-19: 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. BUTIL-20: An error occurred during access of the alternate collating sequence file Ensure that the information in the alternate collating sequence file is formatted correctly. BUTIL-21: The file version is earlier than 6.0 The RECOVER command cannot recover data from a Btrieve v5.x file.
BUTIL BUTIL-27: 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. BUTIL-30: The key position cannot exceed the record length The range of the specified key position is invalid. The key position you specify on a MKDE call must be within the range of the record’s length.
Messages Page Size (bytes) File Version prior to 9.0 9.0 9.5 or newer 1536 2048 2560 3072 3584 4096 8192 16384 BUTIL-37: 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.
BUTIL The internal overhead in bytes is as follows: Pre 8.x file format = 8 8.x file format = 10 (4096 - 10 = 4086) 9.0 file format = 10 (8192 - 10 = 8182) 9.5 file format = 12 (16384 - 12 = 16372) Note that it is advisable to leave some margin and not to use every available byte because the amount of overhead may increase in future file formats.
Messages BUTIL-47: BUTIL cannot open the command file Ensure that the command file exists and that you specified the command file location and filename correctly. BUTIL-48: 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. BUTIL-49: The command file exceeds 1,000 bytes A command file cannot contain more than 1,000 bytes.
BUTIL BUTIL-62: BUTIL was expecting keyword xxxx on key segment descriptor nn Check the syntax of the description file. BUTIL-63: BUTIL was expecting keyword xxxx Check the syntax of the description file. BUTIL-65: BUTIL has loaded no records Verify that you specified the command correctly and that the input file is in the correct format. BUTIL-66: BUTIL has loaded nn records so far The utility loaded the stated number of records since you issued the BUTIL -LOAD command.
Messages BUTIL-77: 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. BUTIL-82: 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.
BUTIL the ROLLFWD operation and specify the segment_number parameter of the earliest log segment you could restore. BUTIL-102: A Roll Forward error occurred An internal error occurred while the MicroKernel was rolling forward files.
Messages BUTIL-142: File xx exists For more information about extended files, see Advanced Operations Guide. 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 Advanced Operations Guide. BUTIL-144: File xx has reached the size limit. The utility created one or more extension files.
BUTIL BUTIL-152: There was an error opening file filename Check the data file attributes, path, and filename. BUTIL-155: BUTIL cannot open the file filename Check the path, filename, and file attributes. BUTIL-156: Failed to login to database. MicroKernel status xx is returned Reference the documentation for the specific status code to resolve this condition BUTIL-157: Failed to logout from database.
Messages MKDE MicroKernel Database Engine Messages This section lists the messages that the MicroKernel Database Engine generates. MKDE-12: The value specified for the –option is invalid Specify with PCC the correct value for the configuration properties setting. For versions prior to Pervasive PSQL 9, enter the correct value in the BSTART.NCF, BTI.INI, or BTI.CFG file.
MKDE MKDE-25: 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). MKDE-51: 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.
Messages 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 containing system data.
MKDE MKDE-79: An unexpected MKDE error nn occurred on DELETE from “xxxx” The MicroKernel returns this message during roll forward operations when a 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. MKDE-80: The system is out of memory The MicroKernel returns this message when the server has insufficient memory to allow the program to operate.
Messages the specified file. You may have a corrupted file, or your log file may be corrupt. Refer to Chapter 1, Status Codes for a description of Status Code nn. MKDE-86: An unexpected MKDE 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. Refer to Chapter 1, Status Codes for a description of Status Code nn.
MKDE MKDE-90: An unexpected MKDE 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. Refer to Chapter 1, Status Codes for a description of Status Code nn.
Messages MKDE-98: The log segment file SYS:SYSTEM/MKDE/LOG/ 0000XXX.LOG cannot be created. There was an error on the console or in the PVSW.LOG 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. 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.
MKDE MKDE-1003: The value specified for Extended Operation Buffer Size is invalid This message is obsolete in Pervasive.SQL 2000i and later versions. This setting is managed dynamically by the engine. MKDE-1004: The value specified for Open Files is invalid This message is obsolete in Pervasive.SQL 2000i and later versions. This setting is managed dynamically by the engine. MKDE-1005: The value specified for Operation Bundle Limit is invalid Specify a valid value.
Messages MKDE-1015: The value specified for Maximum Record Size is invalid This message is obsolete in Pervasive.SQL 2000i and later versions. MKDE-1017: The value specified for System Transaction Hold Limit is invalid This message is obsolete in Pervasive.SQL 2000i and later versions. MKDE-1019: The value specified for Maximum Active Clients is invalid This message is obsolete in Pervasive.SQL 2000i and later versions. This setting is managed dynamically by the engine.
MKDE MKDE-1025: The value specified for Auto-Terminate Delay is invalid Obsolete in Pervasive.SQL 2000 and later versions. MKDE-1026: The value specified for Number of Lines Allocated is invalid Obsolete in Pervasive.SQL 2000 and later versions. MKDE-1027: The value specified for Message Log File Limit is invalid Obsolete in Pervasive.SQL 2000 and later versions. MKDE-1028: The path specified for Home Directory is invalid Obsolete in Pervasive.SQL 2000 and later versions.
Messages 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. MKDE-1157: System Error: nn.nn.nn The MicroKernel Database Engine returns this message when a system error occurs.
MKDE MKDE-1167: Could not create IPC queue The MicroKernel returns this message if an internal error occurs. MKDE-1168: Client(s) active - Shutdown anyway? The MicroKernel returns this message when you attempt to shut down the Workgroup engine while at least one application is still using the engine. If you choose to shut down anyway, you could lose data. MKDE-1169: Could not open BTI.INI The MicroKernel returns this message when it cannot open the file BTI.INI.
Messages MKDE-1175: 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. MKDE-1176: 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. MKDE-1177: Help is not available This message is obsolete in Pervasive.SQL 2000 and later versions.
MKDE MKDE-1184: Unable to set number of file handles to requested value. Maximum open files reduced to nn. This message is obsolete in Pervasive.SQL 2000i and later versions. This setting is managed dynamically by the engine. 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. MKDE-1192: Settings read from NOVDB.INI - To change to BTI.
Messages doing the roll forward is the same as the version of the MicroKernel that created the log file. MKDE-1208: An Open operation failed on “xxxx” with MKDE error nn The MicroKernel returns this message during roll forward operations when an 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.
MKDE MKDE-1213: An internal error nn occurred The MicroKernel returns this message when an internal error occurs. Try to perform the operation again. MKDE-1214: An unexpected MKDE error nn occurred on GET EQUAL in “xxxx” The MicroKernel returns this message during roll forward operations when a 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.
Messages MKDE-1219: An unexpected MKDE 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.
MKDE MKDE-1224: An unexpected MKDE 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 MKDE-2004: The value specified for the Number of Open Files option is invalid This message is obsolete in Pervasive.SQL 2000i and later versions. This setting is managed dynamically by the engine. The MicroKernel returns this message when the value specified for the Number of Open Files option is invalid. Use the configuration properties and specify a valid value for this option.
MKDE MKDE-2010: The value specified for the Sort Buffer Size option is invalid This message is obsolete in Pervasive.SQL 2000i and later versions. This setting is managed dynamically by the engine. The MicroKernel returns this message when the value specified for the Sort Buffer Size option is invalid. Use the configuration properties and specify a valid value for this option.
Messages 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. MKDE-2024: 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.
MKDE The format of a system error is id.op.rc where: Table 2-2 System Error Explanation id Unique System Error identifier op Btrieve operation being performed at the time rc any unexpected return code from the operating system. The id corresponds to a section of code in the MKDE where the OS call took place.
Messages successfully, but the data returned by the call is not what was expected. In many cases, the appearance of an occasional System Error does not indicate a problem. It is likely that the operation being performed was retried without an error and processing continued normally. If there is a problem that would cause an interruption in normal operation, the System Error would correspond to a Pervasive status code returned to the application.
MKDE MKDE-2061: 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.
Messages MKDE-2077: 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. MKDE-2078: An Open operation failed on “xxxx” with MKDE error nn The MicroKernel returns this message during roll forward operations when an error occurs. The MicroKernel returns the specified status code for the specified file.
MKDE MKDE-2083: An internal error nn occurred The MicroKernel returns this message when an internal error occurs. Try to perform the operation again. MKDE-2084: An unexpected MKDE error nn occurred on GET EQUAL in “xxxx” The MicroKernel returns this message during roll forward operations when a 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.
Messages MKDE-2089: An unexpected MKDE 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.
MKDE MKDE-2094: An unexpected MKDE 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 REBUILD Rebuild Utility Messages This section lists the messages that the Rebuild utility generates. REBUILD-2: The utility could not allocate memory Check the amount of available memory and exit any applications or processes not needed to provide more memory. REBUILD-3: The utility could not rename file_name to file_name. The MicroKernel Database Engine status code was code_number. Check the meaning of the status code to help determine why the file could not be renamed.
REBUILD REBUILD-9: The utility could not create the new file or files with the MicroKernel Database Engine 6.x advanced features Ensure that the correct version of the database engine is loaded and the file format option is not prior to 6.0. REBUILD-10: An invalid parameter or value was specified, or the command line was invalid Check the parameters and values passed to the utility.
Messages REBUILD-19: The utility could not access the output directory specified. Directory_name might not exist or did not allow write access. Verify that the directory exists and that the person running the rebuild utility has read/write permissions to the directory. REBUILD-20: The utility is processing file_name For a successful rebuild, the utility reports “The file was rebuilt successfully.” REBUILD-24: An error occurred accessing file_name. Make sure you specified a valid file name.
REBUILD REBUILD-31: The utility could not create file_name. The MicroKernel Database Engine status code was code_number. The rebuild utility also outputs the following information to help you troubleshoot the operation: REBUILD copied a total of number records. The rebuild operation start time is time. REBUILD-34: Key number code_number is invalid Verify that the keys in the file to be rebuilt are valid. REBUILD-35: Page size page_size is invalid. The page size will be changed to page_size.
Messages REBUILD-48: The utility could not initialize the user interface library Close other applications to free up memory. REBUILD-63: The utility could not initialize the localized message table Close other applications to free up memory. REBUILD-65: The utility could not open file file_name for the following reason: Take corrective action based on the reason provided and try the rebuild operation again. REBUILD-66: Operation(s) complete. See file_name for results.
REBUILD REBUILD-71: The file file_name is already in a later format than the current MicroKernel Database Engine setting Configure the MicroKernel to create files using the file format version to which you want the specified file to be converted. See Create File Version in Advanced Operations Guide. REBUILD-72: The utility only converts files to file_format or later Verify the file format to which you want to convert the file.
Messages REBUILD-80: Password specified is longer than the maximum limit of length bytes Verify the password name and try the rebuild operation again. REBUILD-81: User ID specified is longer than the maximum limit of length bytes Verify the user name and try the rebuild operation again. REBUILD-82: Login to database failed. MicroKernel status code_number was returned. Check the meaning of the status code to help determine the result of the rebuild operation.
Index Numerics 0 1-53 1 1-54 10 1-57 100 1-94 10000 1-174 10001 1-174 10002 1-174 10003 1-174 10004 1-174 10005 1-174 10006 1-174 10007 1-174 10008 1-174 10009 1-174 1001 1-107 10010 1-174 10011 1-174 10012 1-174 10013 1-174 10014 1-174 10015 1-174 10016 1-174 10017 1-174 10018 1-174 10019 1-174 10020 1-174 10021 1-174 10022 1-174 10023 1-174 10024 1-174 10025 1-174 10026 1-174 10027 1-174 10028 1-174 10029 1-174 -1003 1-3 1003 1-107 10030 1-174 10031 1-174 10032 1-174 10033 1-174 10034 1-174 10035 1-174 1
1012 1-109 1013 1-109 1015 1-109 1016 1-109 1017 1-110 1018 1-110 1019 1-110 -102 1-48 102 1-95 -1020 1-3 1020 1-110 1021 1-111 1022 1-111 -1024 1-3 -1026 1-3 -103 1-48 103 1-96 -1032 1-4 -104 1-48 104 1-96 -1040 1-4 -105 1-49 105 1-96 -1051 1-4 -106 1-49 106 1-97 -107 1-49 107 1-97 -108 1-49 -109 1-50 109 1-97 11 1-57 -110 1-50 110 1-97 -111 1-50 111 1-98 -1113 1-4 -112 1-50 112 1-98 -113 1-50 113 1-98 -114 1-50 114 1-98 -115 1-51 115 1-99 -116 1-51 Index-2 116 1-99 -118 1-51 -119 1-52 12 1-59 -120 1-52
-1504 1-7 -1507 1-7 -1508 1-7 151 1-104 -1513 1-7 -1520 1-7 16 1-62 160 1-104 -1603 1-7 -1605 1-7 161 1-104 162 1-105 163 1-105 169 1-105 170 1-105 171 1-106 172 1-106 173 1-106 174 1-106 175 1-106 176 1-106 177 1-106 178 1-106 18 1-62 -1809 1-8 -1810 1-8 19 1-62 -1902 1-8 -1903 1-9 -1905 1-9 -1907 1-9 2 1-54 20 1-63 2000 1-112 2001 1-112 2003 1-112 2007 1-112 2008 1-112 2009 1-112 2011 1-112 2012 1-113 21 1-64 22 1-64 2200 1-114 2201 1-114 23 1-65 2300 1-115 2301 1-115 2302 1-115 2303 1-115 2304 1-115 230
3003 1-122 3004 1-122 -3005 1-10 3005 1-123 -3006 1-10 3006 1-123 -3007 1-10 -3008 1-10 3008 1-123 -3009 1-10 3009 1-123 -3010 1-11 -3011 1-11 -3012 1-11 3012 1-123 3013 1-124 -3014 1-12 3014 1-124 -3015 1-12 3015 1-125 -3016 1-12 3016 1-125 -3017 1-12 3017 1-125 -3018 1-13 3018 1-125 -3019 1-13 3019 1-125 -3020 1-13 3020 1-126 -3021 1-13 3021 1-126 -3022 1-13 3022 1-126 -3023 1-13 -3024 1-13 -3025 1-13 -3026 1-13 -3027 1-14 -3028 1-14 -3029 1-14 -3030 1-14 3030 1-126 -3031 1-14 3031 1-126 -3032 1-14 Index
-3080 1-19 -3081 1-19 -3082 1-20 -3083 1-20 -3084 1-20 -3085 1-20 -3086 1-20 -3087 1-20 -3088 1-20 -3089 1-20 -3090 1-20 -3091 1-20 -3092 1-21 -3093 1-21 -3094 1-21 -3095 1-21 -3096 1-21 -3097 1-21 -3098 1-21 -3099 1-21 31 1-70 3103 1-128 3104 1-128 3105 1-128 3106 1-129 3107 1-129 3108 1-129 3110 1-129 3111 1-130 3112 1-130 3114 1-130 3115 1-131 3119 1-131 3124 1-131 3126 1-132 3131 1-132 3132 1-132 32 1-70 33 1-71 -3358 1-21 -3359 1-22 -3360 1-22 -3362 1-22 -3363 1-22 -3364 1-22 -3365 1-22 -3366 1-22 -33
-3779 1-27 -3780 1-27 -3781 1-27 -3782 1-27 -3783 1-28 -3784 1-28 -3785 1-28 -3786 1-28 -3787 1-28 -3790 1-28 -3791 1-28 -3793 1-28 -3794 1-28 -3795 1-29 -3796 1-29 -3797 1-29 -3798 1-29 -3799 1-29 38 1-71 39 1-72 4 1-55 40 1-72 -4001 1-29 -4002 1-30 -4003 1-30 4083 1-134 4086 1-134 41 1-72 42 1-72 43 1-73 44 1-73 45 1-74 46 1-74 47 1-74 48 1-75 -4837 1-30 -4838 1-30 -4848 1-30 -4850 1-30 -4851 1-31 -4852 1-31 -4853 1-31 -4856 1-31 -4860 1-31 -4861 1-31 -4863 1-31 Index-6 -4864 1-31 -4865 1-31 -4866 1-32
-4928 -4930 -4931 -4932 -4933 -4934 -4935 -4936 -4937 -4938 -4939 -4940 -4941 -4942 -4943 -4944 -4945 -4946 -4947 -4948 -4949 -4950 -4951 -4952 -4953 -4954 -4955 -4956 -4957 -4958 -4959 -4960 -4961 -4962 -4963 -4964 -4965 -4966 -4967 -4968 -4969 -4970 -4971 -4972 -4973 -4974 1-36 1-36 1-36 1-36 1-36 1-36 1-36 1-37 1-37 1-37 1-37 1-37 1-37 1-37 1-37 1-37 1-37 1-38 1-38 1-38 1-38 1-38 1-38 1-38 1-38 1-38 1-38 1-38 1-39 1-39 1-39 1-39 1-39 1-39 1-39 1-39 1-39 1-39 1-40 1-40 1-40 1-40 1-40 1-40 1-40 1-40 -497
-5226 1-46 -5229 1-46 -5230 1-46 -5231 1-46 -5232 1-46 -5233 1-46 -5243 1-47 -5245 1-47 -5247 1-47 -5248 1-47 53 1-77 54 1-77 55 1-77 56 1-77 57 1-77 58 1-78 59 1-78 6 1-56 60 1-78 6000 1-138 6002 1-138 6003 1-138 6005 1-138 6006 1-138 6007 1-138 6008 1-138 6009 1-139 61 1-78 62 1-78 63 1-79 64 1-80 65 1-80 66 1-80 67 1-81 68 1-81 69 1-81 7 1-56 7001 1-141 7002 1-141 7003 1-141 7004 1-141 7005 1-141 7006 1-141 7007 1-141 7008 1-142 7009 1-142 Index-8 7010 1-142 7011 1-142 7012 1-142 7013 1-142 7014 1-142
7111 1-149 7112 1-149 7113 1-150 7115 1-150 7117 1-150 7118 1-150 7119 1-151 7120 1-151 7122 1-151 7124 1-152 7125 1-152 7126 1-152 7130 1-152 7131 1-153 7132 1-153 72 1-82 7201 1-154 7212 1-154 7213 1-154 7215 1-154 7218 1-155 7221 1-155 7222 1-155 7223 1-155 7224 1-156 7226 1-156 7235 1-156 7239 1-156 7241 1-157 7252 1-157 7260 1-157 7261 1-157 7262 1-158 7264 1-158 7265 1-158 7267 1-158 7268 1-158 7269 1-158 73 1-82 7305 1-159 7306 1-159 7310 1-159 7311 1-159 7313 1-159 7315 1-159 7317 1-160 7335 1-160
82 1-85 83 1-85 84 1-85 85 1-86 8500 1-167 8502 1-167 8503 1-167 8504 1-167 8505 1-168 8506 1-168 8507 1-168 8508 1-169 8509 1-169 8510 1-169 8511 1-169 8512 1-169 8513 1-169 8514 1-170 8515 1-170 8516 1-170 8517 1-170 8518 1-171 8519 1-171 8520 1-171 8521 1-171 8590 1-172 8591 1-172 8592 1-172 8593 1-172 8594 1-173 86 1-87 87 1-87 88 1-88 89 1-89 9 1-56 90 1-90 91 1-90 92 1-91 93 1-91 94 1-91 95 1-92 96 1-93 97 1-94 A Authorization status codes 1-154 Index-10 B BDREQUTIL-16 2-6 BDREQUTIL-8 2-6 BDREQUTIL
BUTIL-2 2-8 BUTIL-20 2-10 BUTIL-21 2-10 BUTIL-23 2-10 BUTIL-25 2-10 BUTIL-26 2-10 BUTIL-27 2-11 BUTIL-30 2-11 BUTIL-31 2-11 BUTIL-32 2-11 BUTIL-36 2-11 BUTIL-37 2-12 BUTIL-38 2-12 BUTIL-41 2-13 BUTIL-43 2-13 BUTIL-44 2-13 BUTIL-45 2-13 BUTIL-47 2-14 BUTIL-48 2-14 BUTIL-49 2-14 BUTIL-50 2-14 BUTIL-52 2-14 BUTIL-53 2-14 BUTIL-6 2-8 BUTIL-60 2-14 BUTIL-61 2-14 BUTIL-62 2-15 BUTIL-63 2-15 BUTIL-65 2-15 BUTIL-66 2-15 BUTIL-70 2-15 BUTIL-74 2-15 BUTIL-76 2-15 BUTIL-77 2-16 BUTIL-8 2-8 BUTIL-82 2-16 BUTIL-84 2-16
Message Router messages 2-7 Messages BREQUTIL 2-6 BROUTER 2-7 Btrieve Message Router 2-7 BUTIL 2-8 Generic 2-3 Maintenance utility 2-8 Message Router 2-7 message router 2-7 MicroKernel Database Engine 2-20 MKDE 2-20 Requester utility 2-6 Router 2-7 MicroKernel Database Engine messages 2-20 status codes 1 to 199 1-54 DOS workstations 1-107 Windows workstations 1-107 MicroKernel Router status codes 1-122 MKDE-1001 2-26 MKDE-1002 2-26 MKDE-1003 2-27 MKDE-1004 2-27 MKDE-1005 2-27 MKDE-1007 2-27 MKDE-1008 2-27 M
MKDE-16 2-20 MKDE-20 2-20 MKDE-2001 2-37 MKDE-2002 2-37 MKDE-2004 2-38 MKDE-2005 2-38 MKDE-2007 2-38 MKDE-2008 2-38 MKDE-2009 2-38 MKDE-2010 2-39 MKDE-2011 2-39 MKDE-2012 2-39 MKDE-2013 2-39 MKDE-2015 2-39 MKDE-2019 2-39 MKDE-2024 2-40 MKDE-2027 2-40 MKDE-2028 2-40 MKDE-2029 2-40 MKDE-2039 2-40 MKDE-2053 2-42 MKDE-2055 2-42 MKDE-2060 2-42 MKDE-2061 2-43 MKDE-2065 2-43 MKDE-2067 2-43 MKDE-2068 2-43 MKDE-2075 2-43 MKDE-2076 2-43 MKDE-2077 2-44 MKDE-2078 2-44 MKDE-2079 2-44 MKDE-2080 2-44 MKDE-2081 2-44 MKDE-2
messages 2-48 REBUILD-10 2-49 REBUILD-14 2-49 REBUILD-15 2-49 REBUILD-16 2-49 REBUILD-17 2-49 REBUILD-18 2-49 REBUILD-19 2-50 REBUILD-2 2-48 REBUILD-20 2-50 REBUILD-24 2-50 REBUILD-25 2-50 REBUILD-26 2-50 REBUILD-27 2-50 REBUILD-3 2-48 REBUILD-31 2-51 REBUILD-34 2-51 REBUILD-35 2-51 REBUILD-38 2-51 REBUILD-39 2-51 REBUILD-4 2-48 REBUILD-44 2-51 REBUILD-45 2-51 REBUILD-48 2-52 REBUILD-5 2-48 REBUILD-63 2-52 REBUILD-65 2-52 REBUILD-66 2-52 REBUILD-67 2-52 REBUILD-68 2-52 REBUILD-69 2-52 REBUILD-7 2-48 REBUILD
Windows workstations 1-107 MicroKernel Router 1-122 Named Database 1-115 Network Services Layer 1-128 ranges 1-2 SQL Relational Database Engine 1-3 successful completion 1-53 W3DBSMGR 1-172 XLT 1-114 Successful completion status code 1-53 System Error xx.xx.
Index-16
