Microframe Corporation 3007 Series Uživatelská příručka

Pervasive PSQL v11Status Codes and MessagesReference for Status Codes and MessagesPervasive Software Inc.12365 Riata Trace ParkwayBuilding BAustin, TX

1-2Status CodesNote This chapter may refer to utilities, products, or platforms that are not part of your product distribution.2000 to 2099 Btrieve Re

1-92Status Codes95: The session is no longer validNote Please see our Pervasive PSQL Knowledge Base for new and updated articles on troubleshooting th

1-931 to 199These 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

1-94Status Codes An application that calls the MicroKernel can return this status code if the DBNAMES.CFG file contains a named database definition s

1-951 to 199If you are a developer, you can modify your application to commit transactions more frequently, so that fewer modified pages remain in cac

1-96Status CodesMicroKernel returns this status code only to Windows-based applications that call WBTRCALL.DLL, or applications that call the Btrieve

1-971 to 199106: The MicroKernel cannot perform a Get Next Chunk operationAn application called the Get Direct/Chunk operation to retrieve a chunk fro

1-98Status Codes111: The specified filename was not found in the archival logging configuration fileThe MicroKernel cannot find the specified file in

1-991 to 199115: The MicroKernel cannot access the archival logging dump fileThe MicroKernel cannot access the archival logging dump file for one of t

1-100Status Codes You may have attempted to open a file with two different Workgroup engines that are mapped to the files using different share names

1-1011 to 199132: The file has reached its size limitThe MicroKernel returns this status code in one of the following situations:The MicroKernel retur

1-3-1000 to -5300-1000 to -5300SQL Relational Database Engine Status CodesThis section lists status codes returned by the SQL Relational Database Engi

1-102Status Codes135: The specified ISR table is corrupt or otherwise invalidThe MicroKernel found a readable COLLATE.CFG file, but the specific Inter

1-1031 to 199 You issued a Start Extended operation with an invalid key number.143: The MicroKernel cannot allow unauthorized access to files in a se

1-104Status Codes149: SQL TriggerWhile using the Btrieve API to alter database tables or entries, the system encountered SQL restrictions placed on th

1-1051 to 199For more information about purchasing and installing additional user counts, refer to Getting Started With Pervasive PSQL. You can use Mo

1-106Status Codes171: Database login failedAuthentication to the database failed due to a wrong or missing password.172: Database name not foundSpecif

1-1071000 to 19991000 to 1999MicroKernel Status Codes for Windows and DOS WorkstationsThe workstation MicroKernel engine returns the following status

1-108Status Codes1006: The pre-image buffer parameter is out of rangeIn Pervasive.SQL 2000i and later versions, the setting Extended Operation Buffer

1-1091000 to 19991011: The compression buffer parameter is out of rangeThis status code is obsolete in MicroKernel versions 7.0 and later.Ensure that

1-110Status Codesall transactions, and issue Btrieve operation 25, using the BTRV interface before calling the initialization function.1017: The Btrie

1-1111000 to 19991021: The MicroKernel failed to initialize The MicroKernel could not complete its initialization tasks. Check the MicroKernel consol

1-4Status Codes-1032: File access deniedThere was an attempt to open a file that is read only or the specified user does not have the proper rights to

1-112Status Codes2000 to 2099Btrieve Requester Status CodesThis section lists the status codes that the Btrieve Requesters generate.2000: Internal err

1-1132000 to 20992012: The Btrieve requester encountered an operating system errorCheck the Pervasive Event Log (PVSW.LOG) for more information.

1-114Status Codes2200 to 2299XLT Status CodesThis section lists the XLT status codes you can receive.2200: XLT Winsock Error This status code is retur

1-1152300 to 23992300 to 2399Named Database Status CodesThis section lists the status codes you can receive when using the named database features of

1-116Status Codes2306: DBNAMES.CFG could not be updatedThe path you specified for the bound, named database is invalid or the paths you specified for

1-1172300 to 2399Administrator and specifying a data path to the DDF directory. Deleting the MicroKernel Router key resolved the problem. 2308: The sp

1-118Status Codesbefore creating the bound, named database. For more information about bound databases, refer to Advanced Operations Guide.2324: Data

1-1192300 to 2399being bound. Make sure that you restore your data from a backup that is consistent with the bound state of the database.2330: Data fi

1-120Status Codes2335: Not allowed to change data locations and change name at the same timeThese two particular parameters are not allowed to be chan

1-1212300 to 23992342: Not allowed to unbind database and change data locations at the same timeThese two particular parameters are not allowed to be

1-5-1000 to -5300-1251: Multiple columns may not be renamed to the same nameWhen you rename multiple columns, each new name must be unique. You cannot

1-122Status Codes3000 to 3099MicroKernel Router Status CodesThis section lists the status codes you can receive from the MicroKernel router, which rec

1-1233000 to 30993005: The MicroKernel router encountered an operating system errorThe MicroKernel router encountered an unexpected error from the ope

1-124Status Codesaccess 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

1-1253000 to 3099 The target network operating system is not available. The target engine is not available. In a Windows 3.x environment, you are u

1-126Status Codes3020: An error occurred while loading the MicroKernelYou receive this status code when an error occurs while loading the MicroKernel

1-1273000 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 initiali

1-128Status Codes3100 to 3199Network Services Layer Status CodesThe following status codes originate from the Pervasive Network Services Layer (PNSL).

1-1293100 to 3199Communication protocols option for both the client and server. For more information on Communication protocols, refer to Advanced Ope

1-130Status CodesNetwork Services Layer is still valid, but was dropped by the network. Stop and restart the application.3111: Failure during send to

1-1313100 to 31993115: Pervasive Network Services Layer encountered a transport failureThe Pervasive Network Services Layer encountered a socket error

1-6Status Codes-1312: View already existsThe name that you specified for a view already exists in the dictionary. Select another name or remove the cu

1-132Status Codes3126: The Pervasive Network Services Layer was unable to resolve the given filename into a valid pathCheck that the given filename is

1-1333100 to 3199for and uninstall Scalable SQL (or Pervasive.SQL 7), and/or all if its components.

1-134Status Codes4000 to 4099Database Utilities Status CodesThis section lists the status codes you can receive when using the Database Utilities (DBU

1-1354000 to 40995 In the right hand frame, adjust the Supported Protocols list as appropriate to your network environment.6 Restart the engines for t

1-136Status Codes5000 to 5999Encryption Status CodesThis section lists status codes you can receive when using the Wire Encryption feature. In Advance

1-1375000 to 5999 You can also use the bcfg command-line utility (see Configuration Through CLI Utility in Advanced Operations Guide).

1-138Status Codes6000 to 6050Data Dictionary Status CodesThis section lists the status codes that pertain to the data dictionary files. These codes of

1-1396000 to 6050The number of index segments that you may use depends on the file’s page size. See status codes 26: The number of keys specified is i

1-140Status CodesProgrammer's Guide, which is part of the Pervasive PSQL Software Developer’s Kit (SDK).

1-1417000 to 70507000 to 7050Distributed Tuning Interface Status CodesThis section lists the status codes you can receive when using the Distributed T

1-7-1000 to -5300-1404: No such indexYou tried to access an index that does not exist. Check the name and path and try again.-1504: Null not validNull

1-142Status Codes7008: Invalid sequence numberSpecify a valid sequence number for the operation.7009: Data on open files is not availableData related

1-1437000 to 70507017: Dictionary path in useAnother process has the dictionary files in use. Close all other running applications and retry the opera

1-144Status Codes7025: Server name not foundThe server you specified cannot be found. Check the server name and try again.7026: Requester not loadedTh

1-1457000 to 70507033: Connection was lostThe remote connection to the server was lost. If this error persists, check your network configuration.7034:

1-146Status Codes7041:Cannot perform operation because database entries in FILE.DDF contain absolute pathsYou cannot perform the requested function be

1-1477000 to 7050the Create Database dialog within Pervasive PSQL Control Center. See New Database GUI Reference in Pervasive PSQL User's Guide.

1-148Status Codes7064 to 7140License Administrator Status CodesThis section lists the status codes you can receive when using the License Administrato

1-1497064 to 71407108: License key length is too longThe length of the license key you attempted to apply exceeds the maximum length allowed for a key

1-150Status Codesstill does not appear in the list, exit then restart License Administrator.7113: Invalid license key. Verify the provided keyThe lice

1-1517064 to 7140 You may have started the License Administrator on a client where a database engine is not installed. Click OK to establish a connec

1-8Status Codes You attempted to add a unique index to a column which already contains non-unique values.-1809: Permission deniedThe user does not ha

1-152Status Codes7124: A User Count Increase cannot be applied without a permanent licenseThe machine on which you are attempting to apply a user coun

1-1537064 to 7140Make sure that the key you are using is correct and that you have the correct Pervasive PSQL product installed.7131: The OS platform

1-154Status Codes7200 to 7499Authorization Status CodesThis section lists the status codes you can receive when authorizing your product.7201: An erro

1-1557200 to 74997218: An error occurred acquiring the machine configurationThe system encountered an error while trying to acquire the machine config

1-156Status Codes7224: User lacks the appropriate rights to apply or delete a keyThe target engine tests for appropriate permissions prior to apply or

1-1577200 to 7499 The registry information for the authorization server may be corrupt or missing on your machine. A network problem is preventing c

1-158Status Codes7262: Error encountered while loading the offline authorization key data fileAn internal error occurred while loading the offline fil

1-1597200 to 74997305: Product key not found in authorization databaseThe product key appears to be valid and has a valid checksum but cannot be found

1-160Status Codes7317: Deleting a key requires an applied keyDeletion cannot occur because no key is available. A product key must be applied before i

1-1617200 to 74997341: Product key cannot be applied because maximum authorizations have been reachedThe product key has already been applied the maxi

1-9-1000 to -5300-1903: Invalid account nameEither a user with the specified user name or a group with the specified group name does not exist. Check

1-162Status Codes7347: Maximum number of offline authorizations has been reachedThe maximum number of offline authorizations allowed for the product k

1-1637200 to 74997369: The server is currently unavailable. Please try again later.The requested server is inaccessible at this time. Try accessing th

1-164Status Codes7456: Invalid OEM user ID for the requested recordThe record you are trying to access has a different OEM user ID associated with it

1-1657200 to 74997473: Maximum number of seats for this OEM account has been reachedThe total maximum number of seats has been met. Accounts within an

1-166Status Codes8000 to 8499Component Management Status CodesThese status codes originate from the Component Management and Event Logging interface o

1-1678500 to 85898500 to 8589ECAS Interface Status CodesThis section describes the status codes returned by the ECAS (Enhanced Common Address Space) i

1-168Status Codes8505: An initialization error occurred when trying to establish a session with the Workgroup engineIn its attempt to auto-load the Wo

1-1698500 to 85898508: An error occurred when attempting to enable Btrieve accessThe application failed to enable the Btrieve access method in the Wor

1-170Status Codes8514: An error occurred when unloading the MicroKernelThe application failed to unload the MicroKernel.8515: An error occurred when d

1-1718500 to 85895 Restart the engines for the new settings to take effect.8518: An error occurred when attempting to allocate system memoryThe applic

1-10Status Codes-3005: Cannot alter a COBOL fake table. Invalid operationCOBOL applications that include OCCURS, partial REDEFINES, or variable record

1-172Status Codes8590 to 8599W3DBSMGR Status CodesThis section describes the status codes returned by the W3DBSMGR component. These errors are in the

1-1738590 to 85998594: Engine cannot be restartedThe Workgroup engine has been previously stopped while there were active applications and cannot be r

1-174Status Codes10000 to 10100SQL Connection Manager CodesThis section lists status codes returned by the SQL Connection Manager.10000 through 10064:

2-1chapter2MessagesA Reference to Pervasive PSQL MessagesThis chapter describes the messages that can be returned to Pervasive PSQL users. The message

2-2MessagesMKDE MicroKernel Database Engine MessagesREBUILD Rebuild Utility MessagesTable 2-1 Message Groups

2-3(No prefix)(No prefix)Generic MessagesThe following messages may be returned by more than one utility or component. These messages are not preceded

2-4MessagesInvalid Load File Format. End of Record Marker Not Found The Maintenance utility (BUTIL) encountered an invalid record terminator in the se

2-5(No prefix)Specifying SELECT, INSERT, UPDATE, DELETE or REFERENCES privilege for a Procedure is illegalStored procedures permissions do not include

2-6MessagesBREQUTILRequester Utility MessagesThis section lists the messages that the SQL and MKDE Requester utilities generate.BREQUTIL-8: MicroKerne

2-7BROUTERBROUTERMessage Router MessagesThe following messages are specific to the BROUTER Remote Communications Manager.BROUTER-2: The value specifie

1-11-1000 to -5300by using the Cobolschemaexec utility. (The utility describes the application’s understanding of data to the Pervasive PSQL relationa

2-8MessagesBUTILMaintenance Utility MessagesThe following messages are specific to the Maintenance utility.BUTIL-1: Message file initialization failed

2-9BUTILBUTIL-11: The command line requires the index fileIf you specify the BUTIL -INDEX or -SAVE command (modified by the Y parameter) to the Mainte

2-10MessagesBUTIL-19: BUTIL could not open the alternate collating sequence fileEnsure that you assigned a valid pathname to the Alternate Collating S

2-11BUTILBUTIL-27: An error occurred during the access of the variable page. BUTIL is writing the obtainable portion of the variable page.An error occ

2-12MessagesBUTIL-37: The record length cannot exceed the page sizeThe record length you specified is invalid. In the description file, the record len

2-13BUTILThe 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

2-14MessagesBUTIL-47: BUTIL cannot open the command fileEnsure that the command file exists and that you specified the command file location and filen

2-15BUTILBUTIL-62: BUTIL was expecting keyword xxxx on key segment descriptor nnCheck the syntax of the description file.BUTIL-63: BUTIL was expecting

2-16MessagesBUTIL-77: When BUTIL wrote a mirror copy of the Page Allocation Table at page #nn, an error occurredThe Maintenance utility returns this m

2-17BUTILthe ROLLFWD operation and specify the segment_number parameter of the earliest log segment you could restore.BUTIL-102: A Roll Forward error

disclaimer PERVASIVE SOFTWARE INC. LICENSES THE SOFTWARE AND DOCUMENTATION PRODUCT TO YOU OR YOUR COMPANY SOLELY ON AN “AS IS” BASIS AND SOLELY IN ACC

1-12Status Codes-3014: Trigger already existsYou are trying to create a trigger, but a trigger with the specified name already exists. Either use a di

2-18MessagesBUTIL-142: File xx existsFor more information about extended files, see Advanced Operations Guide.BUTIL-143: File xx exists. This file is

2-19BUTILBUTIL-152: There was an error opening file filenameCheck the data file attributes, path, and filename.BUTIL-155: BUTIL cannot open the file f

2-20MessagesMKDEMicroKernel Database Engine MessagesThis section lists the messages that the MicroKernel Database Engine generates.MKDE-12: The value

2-21MKDEMKDE-25: The file filename is rolling backRolling back is the procedure the MicroKernel uses to restore a file to a consistent state after a s

2-22Messagesloading, the loading fails and no operations are possible until the problem is corrected. If the error occurs later, during normal operati

2-23MKDEMKDE-79: An unexpected MKDE error nn occurred on DELETE from “xxxx”The MicroKernel returns this message during roll forward operations when a

2-24Messagesthe 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

2-25MKDEMKDE-90: An unexpected MKDE error nn occurred on CLOSE to filenameThe MicroKernel returns this message during roll forward operations when an

2-26MessagesMKDE-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.LOGThe M

2-27MKDEMKDE-1003: The value specified for Extended Operation Buffer Size is invalidThis message is obsolete in Pervasive.SQL 2000i and later versions

1-13-1000 to -5300-3018: Invalid data type conversion to an identity columnAn attempt was made to alter a data type to an identity column.-3019: Canno

2-28MessagesMKDE-1015: The value specified for Maximum Record Size is invalidThis message is obsolete in Pervasive.SQL 2000i and later versions. MKDE-

2-29MKDEMKDE-1025: The value specified for Auto-Terminate Delay is invalidObsolete in Pervasive.SQL 2000 and later versions. MKDE-1026: The value spec

2-30Messagesfiles. When an error occurs while writing to the transaction log file, the MicroKernel attempts to resume transaction logging after every

2-31MKDEMKDE-1167: Could not create IPC queueThe MicroKernel returns this message if an internal error occurs.MKDE-1168: Client(s) active - Shutdown a

2-32MessagesMKDE-1175: I/O error - filenameThe MicroKernel returns this message when it encounters an I/O error while reading from or writing to a fil

2-33MKDEMKDE-1184: Unable to set number of file handles to requested value. Maximum open files reduced to nn.This message is obsolete in Pervasive.SQL

2-34Messagesdoing the roll forward is the same as the version of the MicroKernel that created the log file.MKDE-1208: An Open operation failed on “xxx

2-35MKDEMKDE-1213: An internal error nn occurredThe MicroKernel returns this message when an internal error occurs. Try to perform the operation again

2-36MessagesMKDE-1219: An unexpected MKDE error nn occurred on BEGIN TRANSACTION to filenameThe MicroKernel returns this message during roll forward o

2-37MKDEMKDE-1224: An unexpected MKDE error nn occurred on BEGIN TRANSACTIONThe MicroKernel returns this message during roll forward operations when a

1-14Status Codes-3027: Invalid foreign key constraint nameThe foreign key constraint name that you have specified is invalid. Specify a name between 1

2-38MessagesMKDE-2004: The value specified for the Number of Open Files option is invalidThis message is obsolete in Pervasive.SQL 2000i and later ver

2-39MKDEMKDE-2010: The value specified for the Sort Buffer Size option is invalidThis message is obsolete in Pervasive.SQL 2000i and later versions. T

2-40Messagestransaction logging after every update to a data file containing system data. Therefore, when the condition causing the error is corrected

2-41MKDEThe format of a system error is id.op.rc where:The id corresponds to a section of code in the MKDE where the OS call took place. There are dif

2-42Messagessuccessfully, but the data returned by the call is not what was expected. In many cases, the appearance of an occasional System Error does

2-43MKDEMKDE-2061: Error writing the registry. Error code: nnThe MicroKernel returns this message when it encounters an error while trying to write in

2-44MessagesMKDE-2077: The log file format is invalidThe MicroKernel returns this message when the log segment file format is incompatible. Ensure tha

2-45MKDEMKDE-2083: An internal error nn occurredThe MicroKernel returns this message when an internal error occurs. Try to perform the operation again

2-46MessagesMKDE-2089: An unexpected MKDE error nn occurred on BEGIN TRANSACTION to filenameThe MicroKernel returns this message during roll forward o

2-47MKDEMKDE-2094: An unexpected MKDE error nn occurred on BEGIN TRANSACTIONThe MicroKernel returns this message during roll forward operations when a

1-15-1000 to -5300-3034: Type cannot be nullThe requested operation cannot be performed on a column definition that is nullable.-3035: Length of the f

2-48MessagesREBUILDRebuild Utility MessagesThis section lists the messages that the Rebuild utility generates.REBUILD-2: The utility could not allocat

2-49REBUILDREBUILD-9: The utility could not create the new file or files with the MicroKernel Database Engine 6.x advanced features Ensure that the co

2-50MessagesREBUILD-19: The utility could not access the output directory specified. Directory_name might not exist or did not allow write access.Veri

2-51REBUILDREBUILD-31: The utility could not create file_name. The MicroKernel Database Engine status code was code_number.The rebuild utility also ou

2-52MessagesREBUILD-48: The utility could not initialize the user interface library Close other applications to free up memory.REBUILD-63: The utility

2-53REBUILDREBUILD-71: The file file_name is already in a later format than the current MicroKernel Database Engine setting Configure the MicroKernel

2-54MessagesREBUILD-80: Password specified is longer than the maximum limit of length bytesVerify the password name and try the rebuild operation agai

Index-1IndexNumerics0 1-531 1-5410 1-57100 1-9410000 1-17410001 1-17410002 1-17410003 1-17410004 1-17410005 1-17410006 1-17410007 1-174100

Index-21012 1-1091013 1-1091015 1-1091016 1-1091017 1-1101018 1-1101019 1-110-102 1-48102 1-95-1020 1-31020 1-1101021 1-1111022 1-111-102

Index-3-1504 1-7-1507 1-7-1508 1-7151 1-104-1513 1-7-1520 1-716 1-62160 1-104-1603 1-7-1605 1-7161 1-104162 1-105163 1-105169 1-105170

1-16Status CodesIf you just tried to create the specified user, but you tried again because you are not sure if it was created, this error indicates t

Index-43003 1-1223004 1-122-3005 1-103005 1-123-3006 1-103006 1-123-3007 1-10-3008 1-103008 1-123-3009 1-103009 1-123-3010 1-11-3011 1-11

Index-5-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

Index-6-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

Index-7-4928 1-36-4930 1-36-4931 1-36-4932 1-36-4933 1-36-4934 1-36-4935 1-36-4936 1-37-4937 1-37-4938 1-37-4939 1-37-4940 1-37-4941 1-37

Index-8-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-4753 1-7754 1-7755 1-7756 1-775

Index-97111 1-1497112 1-1497113 1-1507115 1-1507117 1-1507118 1-1507119 1-1517120 1-1517122 1-1517124 1-1527125 1-1527126 1-1527130 1-152

Index-1082 1-8583 1-8584 1-8585 1-868500 1-1678502 1-1678503 1-1678504 1-1678505 1-1688506 1-1688507 1-1688508 1-1698509 1-1698510 1-169

Index-11BUTIL-2 2-8BUTIL-20 2-10BUTIL-21 2-10BUTIL-23 2-10BUTIL-25 2-10BUTIL-26 2-10BUTIL-27 2-11BUTIL-30 2-11BUTIL-31 2-11BUTIL-32 2-11BUTI

Index-12Message Router messages 2-7MessagesBREQUTIL 2-6BROUTER 2-7Btrieve Message Router 2-7BUTIL 2-8Generic 2-3Maintenance utility 2-8Message

Index-13MKDE-16 2-20MKDE-20 2-20MKDE-2001 2-37MKDE-2002 2-37MKDE-2004 2-38MKDE-2005 2-38MKDE-2007 2-38MKDE-2008 2-38MKDE-2009 2-38MKDE-2010

1-17-1000 to -5300-3052: Dictionary already existsA dictionary with the specified name already exists in that directory. Use a different dictionary na

Index-14messages 2-48REBUILD-10 2-49REBUILD-14 2-49REBUILD-15 2-49REBUILD-16 2-49REBUILD-17 2-49REBUILD-18 2-49REBUILD-19 2-50REBUILD-2 2-48R

Index-15Windows workstations 1-107MicroKernel Router 1-122Named Database 1-115Network Services Layer 1-128ranges 1-2SQL Relational Database Engin

Index-16

1-18Status Codes-3062: Database has no securityYou tried to set security privileges on a database that was not marked secure. First, enable security o

1-19-1000 to -5300-3071: Cannot revoke synonym privilegesYou cannot revoke privileges to a synonym; you must revoke privileges to the group the synony

1-20Status Codes-3082: DDF already boundYou cannot bind a Data Dictionary File that is already bound.-3083: DDF not boundYou cannot unbind a Data Dict

1-21-1000 to -5300-3092: RI synchronizationThe binding information in the Data Dictionary File and data files does not match.-3093: Trigger RI conflic

iiiContentsAbout This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vWho Should Read This Manual?. .

1-22Status Codes-3359: Not allowed to bind database and change data locations at the same timeSee 2341: Not allowed to bind database and change data l

1-23-1000 to -5300-3367: Not allowed to unbind database and change name at the same timeSee 2333: Not allowed to unbind database and change name at th

1-24Status Codes-3385: Cannot create DBNAMES.CFG fileSee 2314: Cannot create DBNAMES.CFG file.-3386: The bound database cannot share data dictionary f

1-25-1000 to -5300-3397: Invalid buffer lengthSee 2302: Invalid buffer length.-3398: The database name is invalidSee 2301: The database name is invali

1-26Status Codes-3485: The routing table of the Pervasive Network Services Layer is fullSee 3114: The routing table of the Pervasive Network Services

1-27-1000 to -5300-3495: The Pervasive Network Services Layer encountered a permission errorSee 3104: The Pervasive Network Services Layer encountered

1-28Status Codes-3783: The MicroKernel router encountered an internal errorSee 3016: The MicroKernel router encountered an internal error.-3784: The M

1-29-1000 to -5300-3795: The MicroKernel is not responding to the MicroKernel routerSee 3004: The MicroKernel is not responding to the MicroKernel rou

1-30Status Codes-4002: Specified push-down filter field not found in the tableCOBOL applications that include OCCURS, partial REDEFINES, or variable r

1-31-1000 to -5300-4851: A roll forward error occurredSee 148: A roll forward error occurred.-4852: The log segment is missingSee 147: The log segment

ivTables1-1 Status Code Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11-2 SET State

1-32Status Codes-4866: More than 5 concurrent users attempted to access the same data fileSee 133: More than 5 concurrent users attempted to access th

1-33-1000 to -5300-4890: The MicroKernel cannot access the archival logging configuration fileSee 110: The MicroKernel cannot access the archival logg

1-34Status Codes-4899: No cache buffers are availableSee 100: No cache buffers are available.-4902: The data buffer is too smallSee 97: The data buffe

1-35-1000 to -5300-4912: The handle table is fullSee 87: The handle table is full.-4913: The file table is fullSee 86: The file table is full.-4914: F

1-36Status Codes-4923: There is a conflict on the referenced fileSee 76: There is a conflict on the referenced file.-4926: The RI definition is out of

1-37-1000 to -5300-4936: The data buffer parameter specified on an Insert Extended operation is invalidSee 63: The data buffer parameter specified on

1-38Status Codes-4946: The language interface version is invalidSee 53: The language interface version is invalid.-4947: An error occurred while writi

1-39-1000 to -5300-4957: A file previously opened in Accelerated mode was not closedSee 42: A file previously opened in Accelerated mode was not close

1-40Status Codes-4967: The file cannot be extendedSee 32: The file cannot be extended.-4968: The file is already extendedSee 31: The file is already e

1-41-1000 to -5300-4978: The key buffer parameter is too shortSee 21: The key buffer parameter is too short.-4979: The MicroKernel or Btrieve Requeste

vAbout This ManualThis manual describes the status codes and messages you may encounter while using components of Pervasive PSQL v11. An explanation o

1-42Status Codes-4989: The key field is not modifiableSee 10: The key field is not modifiable.-4990: The operation encountered the end-of-fileSee 9: T

1-43-1000 to -5300-4998: The operation parameter is invalidSee 1: The operation parameter is invalid.-5022: Columns in the selection list and the retu

1-44Status CodesCREATE FUNCTION myfunc(:a INT DEFAULT myfunc(1)) RETURNS INTEGERASBEGINRETURN :a;END;-5032: RETURN statements in a UDF must have an ar

1-45-1000 to -5300-5202: Record is lockedAn attempt was made to access a record that is locked by another user. Wait until the record is unlocked and

1-46Status Codes-5225: Cannot drop an in-built function or an aggregate functionYou cannot delete an aggregate function or a pre-defined scalar functi

1-47-1000 to -5300index name: ALTER INDEX RENAME database1:table1:index1 TO index2. However, the following statement causes an error because a view na

1-48Status Codes-100 to -199Informative Status CodesThis section lists the informative status codes that the MicroKernel can return. The MicroKernel r

1-49-100 to -199-105: The CREATE statement completed successfullyThe following statements return this status code when they execute successfully:The M

1-50Status Codesapplication allows substitution variables, refer to the documentation included with the application to determine how to use them. -109

1-51-100 to -199 Operations that create or change dictionary definitions. Therefore, you cannot roll back the results of the following statements: AL

viWho Should Read This Manual?This manual provides information for developers, testers, and support personnel who install and run Pervasive PSQL Serve

1-52Status CodesIf you issued a DECLARE statement, the MicroKernel successfully created the cursor, variable, or condition you defined.-119: The SET a

1-5300Successful Interface Completion Status CodeAny interface call can return the following status code.0: The interface completed successfullyThis s

1-54Status Codes1 to 199MicroKernel Database Engine Status Codes This section describes status codes that the MicroKernel returns.1: The operation par

1-551 to 199Note Please see the Pervasive PSQL Knowledge Base for new and updated articles on troubleshooting this status code. You can access the Kno

1-56Status Codes6: The key number parameter is invalidThe value stored in the key number parameter is not valid for the file being accessed. The key n

1-571 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 E

1-58Status Codes The application attempted to open a file that has .^^^ as its extension. This extension is reserved for the MicroKernel to use durin

1-591 to 199LSL.COM LAN Card DriverIPXODI.COMIFSHLP.SYSNET START FULL These can be loaded high, using emm386. NET START FULL will load in upper memory

1-60Status Codes When accessing a file on a server, ensure that you have FILE SCAN rights to the directory in which the file resides. Occasionally, a

1-611 to 19913: The MicroKernel could not open the extension file for an extended fileThe MicroKernel could not open the extension file for an extende

viiManual OrganizationThe following list briefly describes each chapter in the manual: Chapter 1 — Status CodesThis chapter lists and explains each s

1-62Status Codes16: The application encountered an expansion errorThis status code is obsolete in MicroKernel versions 6.0 and later.The MicroKernel e

1-631 to 19920: The MicroKernel or Btrieve Requester is inactiveNote For an expanded list of possible recovery solutions, consult the Pervasive PSQL K

1-64Status Codes Make sure the Windows DLLs are in your path. Make sure the appropriate communications modules are loaded at the server.21: The key

1-651 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.

1-66Status CodesNote This happens when the Operating system returns an unusual status code to the engine. Normally, the engine expects either a succes

1-671 to 199Conditions For Which Status Code 26 Is ReturnedThe following conditions apply to the Btrieve Create API operation. See Create (14) in Btri

1-68Status CodesNullable ColumnsNote that nullable columns must also be considered. For example, in a data files with 4096 byte page size you are limi

1-691 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 by

1-70Status Codes30: The file specified is not a MicroKernel fileThis status code is returned in one of the following situations: The MicroKernel did

1-711 to 19933: The MicroKernel cannot unloadIn the DOS environment, The MicroKernel returns this status code for the following reasons: You attempte

viiiConventionsUnless otherwise noted, command syntax, code, and examples use the following conventions:CASE Commands and reserved words typically app

1-72Status Codes39: A Begin Transaction operation must precede an End/Abort Transaction operationThe application issued an End Transaction (20),or Abo

1-731 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 s

1-74Status Codes45: The specified key flags are invalidThe key flags specification on a Create operation is inconsistent. If a key has multiple segmen

1-751 to 19948: The alternate collating sequence definition is invalidThe MicroKernel returns this status code for the following reasons: The first b

1-76Status Codes³ To change the Create File Version setting:1 Start Pervasive PSQL Control Center (see Starting PCC on Windows in Pervasive PSQL User&

1-771 to 19953: The language interface version is invalidAn application tried to access a file containing variable-length records with a language inte

1-78Status Codes58: The compression buffer length is too shortThis status code is obsolete in Pervasive.SQL 2000i and later versions.59: The specified

1-791 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 0x000

1-80Status Codes64: The filter limit has been reachedThe MicroKernel returns this status code for the following reasons: During a Get Next Extended,

1-811 to 19967: The MicroKernel cannot open the SQL data dictionary filesThe MicroKernel returns this status code for the following reasons: An appli

1-1chapter1Status CodesA Reference to Pervasive PSQL Status CodesThis chapter describes the status codes and messages generated by any of the componen

1-82Status Codes71: There is a violation of the RI definitions If you attempted an Insert operation on a file under RI control, a foreign key value i

1-831 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 att

1-84Status Codes The application is currently processing a wait transaction and tried to access a file that another user has locked.When you are usin

1-851 to 19981: The MicroKernel encountered a lock errorThe MicroKernel returns this status code in one of the following situations: The application

1-86Status Codes Tried to update or delete a record locked by another application. The application can use either of the following recovery methods:

1-871 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 f

1-88Status Codes To configure your operating system to allow more handles, refer to your operating system documentation. It is helpful to know the fo

1-891 to 199 You attempted to remove a file from continuous operation, but a different client placed the file into continuous operation. You attempt

1-90Status Codes90: The redirected device table is fullThis status code is obsolete in MicroKernel versions 6.0 and later.The DOS Requester redirectio

1-911 to 199 A communication or network addressing problem exists in your network environment, so the MicroKernel requests never reach their destinat