The status codes and messages listed here are generated by PSQL components.

Status codes are not the same as numbered messages (see 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 Engine.

Status codes are returned to an application making a PSQL interface call. The application determines whether or not to display the status code to the user. Applications will often display status codes in addition to helpful messages about a problem that has occurred, but the application developer determines this. Many utilities provided with PSQL use transactional and relational access interfaces, and they may therefore return status codes as well as utility-specific messages.

Some messages include references to status codes.

The status codes appear in numeric order. The following table lists the numeric ranges for each type of code.

Any interface call can return the following status code.

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

This section describes status codes that the MicroKernel Engine returns.

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 prerelease version of the V8 database engine. If this is the case, you must uninstall your database engine and install the general release version.

This status code typically indicates a corrupt file, an error while reading from or writing to the disk. One of the following has occurred:

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

The MicroKernel cannot find the specified key value in the index path.

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

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.

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

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

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

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

The MicroKernel returns this status code in the following situations:

During an Update operation, the application attempted to modify a key field that cannot be modified by definition.

The MicroKernel returns this status code in the following situations:

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.

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

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

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

This status code became obsolete in MicroKernel version 6.0.

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.

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

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

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.

This status code became obsolete in Btrieve language interface version 6.0.

The position block parameter must be exactly 128 bytes long.

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

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

One solution is to disable the Antivirus software. Contact the third party vendor for additional information on configuring the Antivirus software to eliminate scanning specific data files.

The number of keys specified for the page size is invalid. Note that the maximum number of keys is 119 for all file versions.

The number of key segments can vary but must be within the limits shown by the following table.

The following conditions apply to the Btrieve Create API operation. See Create (14) in Btrieve API Guide, which is part of the PSQL Software Development Kit (SDK).

The following condition applies to the Btrieve Create Index API operation. See Create Index (31) in Btrieve API Guide, which is part of the PSQL Software Development Kit (SDK).

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.x or later, and TRUENULLCREATE set to the default value of On, has true null support. Files created using an earlier file format, or with Pervasive.SQL 7, or with TRUENULLCREATE set to Off, do not have true null support and do not have this limitation.

The specified key field position is less than 1 or exceeds the defined record length for the file. Either the key position is greater than the record length or the key position plus the key length exceeds the record length.

The physical record length, which is the logical record length specified when creating the file plus any additional overhead for duplicate keys, reserved duplicate pointers, variable record pointers, and blank truncation information must be less than or equal to the page size minus 10 bytes (8 bytes if creating files in version 5 file format), and must be greater than or equal to 4 bytes.

For key-only files, the maximum record length is 253 bytes (255 bytes if creating files in version 5 file format).

For more information about calculating the physical record length, see PSQL Programmer's Guide.

The MicroKernel returns this status code for the following situations pertaining to the Btrieve Create or Create Index API operations. See Create (14) and Create Index (31), both in Btrieve API Guide, which is part of the PSQL Software Development Kit (SDK).

This status code is returned in one of the following situations:

This status code became obsolete in MicroKernel version 6.0.

An application tried to extend a file that had already been extended; you can only extend a file once.

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

In the DOS environment, The MicroKernel returns this status code for the following reasons:

This status code became obsolete in MicroKernel version 6.0.

An application specified an invalid file name for the extended partition. Check the validity of the file name.

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

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

This status code became obsolete in MicroKernel version 7.0.

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

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.

This status code became obsolete in MicroKernel version 6.0.

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

The application tried to perform an operation that is not allowed under these operating conditions. For example:

This status code became obsolete in MicroKernel version 6.0.

The MicroKernel returns this status code for the following reasons:

The MicroKernel returns this status code for the following reasons:

The application tried to use the Get Direct/Record operation to establish positioning on an index path for a key whose value is null in the corresponding record. The MicroKernel cannot establish positioning based on a null key value.

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.

The MicroKernel returns this status code for the following reasons:

This status code became obsolete in MicroKernel version 6.0.

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

The MicroKernel returns this status code for the following reasons:

The MicroKernel returns this status code for the following reasons:

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

The MicroKernel returns this status code for the following reasons:

For more information, see Owner Names in Advanced Operations Guide.

This status code became obsolete starting as of MicroKernel version 6.0.

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

An application tried to access a file containing variable-length records with a language interface from Btrieve v3.15 or earlier.

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

The data field indexed by an autoincrement key can be part of a different segmented key only if the key number of the autoincrement key is less than the key number of the new segmented key and the new data type flag referencing the field is not AUTOINCREMENT

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

This status code became obsolete in MicroKernel version 6.0.

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

This status code became obsolete in Pervasive.SQL 2000i.

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 file name specified in the key buffer parameter.

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

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

This status code is returned in the following situations:

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

The MicroKernel returns this status code for the following reasons:

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

This status code became obsolete in Pervasive.SQL 2000i.

The MicroKernel tried to open files bound to too many MicroKernel databases. To avoid receiving this status code, you must set a higher value for the number of databases that the MicroKernel can open.

See Advanced Operations Guide for more information about bound files.

The MicroKernel returns this status code for the following reasons:

If the data file has RI definitions, the DBNAMES.CFG file must be in the location specified in the DBNames Configuration Location option in the server configuration settings. Also, ensure that FILE.DDF and RELATE.DDF (if the file has RI definitions) are in the locations specified by the Working Directory option in the server configuration settings.

The MicroKernel cannot enforce the Delete Cascade rule on a file under referential integrity (RI) control because the record that the application attempted to delete has more than 16 levels of descendants. Delete records from the lower levels, and then try again to delete the record that the application was attempting to delete initially. See Advanced Operations Guide for more information about RI.

The application encountered an error while the MicroKernel was attempting to enforce the Delete Cascade rule in response to a Delete operation. This status code indicates that the related file has been damaged and must be recreated. See Advanced Operations Guide for more information about RI and the Delete Cascade rule.

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

See Advanced Operations Guide for more information about referential integrity.

The MicroKernel returns this status code for the following reasons:

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

A Btrieve operation may be canceled for various reasons, such as a deliberate choice by the user to do so, insufficient system resources, higher priority of another operation, or shutdown of the engine or the operating system.

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

This status code became obsolete in MicroKernel version 7.0.

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

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

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

This status code became obsolete in MicroKernel version 7.0.

There is a malfunction that the MicroKernel cannot specifically detect or from which the MicroKernel cannot recover. Retry the operation. If the error persists, there may be system corruption; try to clear the system by rebooting, and then try the operation again.

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

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

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

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

This status code became obsolete in MicroKernel version 7.0.

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

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

An application may receive this status code if the database engine is unable to allocate memory to represent a Btrieve data file. The database engine also has a limit of 65,535 files that it can handle at the same time. The status code is also returned if that limit is reached.

One possible cause of this status code is an application that continues to open additional files without closing the data files that it has already opened. View the active files with the Monitor utility to examine whether this may be happening. See Monitoring Active Files in Advanced Operations Guide.

In addition, consider status code 87: The handle table is full. Status code 86 is for files and status code 87 is for handles. Multiple handles can be open for a given file. If the database engine cannot allocate memory for a Btrieve handle, then the application may receive a status 87. The handles allocated to client applications are limited by memory. (Older types of handles that are allocated to DOS applications using the DOS requesters are limited 65,535.)

This status code became obsolete in Pervasive.SQL 2000i. The handle table is managed dynamically by the engine.

You have either attempted to open more handles than the MicroKernel is configured to support, or the MicroKernel attempted to open more files than the operating system allows.

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.

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

NOTE: default value is 20.

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

In the last case described above, once the server has gone down, the Btrieve engine does not know which files were in continuous operation. status code 88 is returned because of this condition.

In order for you to take the files out of continuous operation, you must open the files before trying to end continuous operation mode. When the file is reopened, the Btrieve engine detects that the continuous ops flag is set and looks for the delta file. At that point, the delta file roll-in occurs.

To initiate the roll-in of an existing delta file, the associated data file must be opened. You can open the file with a utility such as the function executor or the application that uses the file. If the application that uses the file repeatedly opens and closes the file, you are advised to open the file with the function executor. This recommendation is made because the delta roll-in is a low priority task. The roll-in was designed in this fashion so that the file can still be used while the roll-in is occurring. If the application closes the file and the roll-in has not finished, the roll-in is initiated again when the file is reopened. As a low priority task, the roll-in process may take some time. Once the engine completes the roll-in, it deletes the delta file.

This status code became obsolete in MicroKernel version 5.0.

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

This status code became obsolete in MicroKernel version 6.0.

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. This status code also occurs if you detach from a server and attach to a different server. Once a client has attached to a server, the Requester does not remove its name from the server routing table.

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

This status code became obsolete in MicroKernel version 7.0.

The application exceeded the maximum number of active transactions. Use the configuration properties to specify a higher value for the Number of Transactions configuration option.

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

The MicroKernel returns this status code in the following situations:

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

If you are using the SPX protocol:

The MicroKernel returns this status code for the following reasons:

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

This indicates that the MicroKernel has used all the cache buffers it allocated at load time.

You may encounter this status code if your application uses a large number of write operations (insert, update, and delete) in a user transaction. The current implementation of the MicroKernel Engine requires all modified pages to reside in cache until the transaction completes.

Note: On a machine with limited available memory, you may not be able to successfully complete very large transactions with thousands of write operations.

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. After that, whenever the engine starts, it reads the value from the Registry and does not recalculate the setting. If you add or remove memory from the system, you must modify the cache allocation size setting to take best advantage of the new amount of memory available.

This indicates that there is not enough operating system memory available to perform the requested operation. To fix this problem, perform one or more of the following:

This indicates that the MicroKernel has run out of stack space. To increase the amount of stack space available to your application, relink the application, setting the stack size to a higher value. The MicroKernel returns this status code only to Windows-based applications that call WBTRCALL.DLL, or applications that call the MicroKernel Engine on the local server.

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

During a Create or Create Index operation, the operating system was not able to return a collation table for the country ID and code page specified. Ensure that the application specified the locale’s country ID and code page correctly and that the operating system is configured to support the country ID and code page.

An application tried to create a file with Variable-tail Allocation Tables (VATs) but without variable-length records (a precondition for files to use VATs). This status code applies to key-only files as well as to regular data files.

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.

An application tried to use either a Get Direct/Chunk operation or an Update Chunk operation on a file in pre-v6.0 format.

The Windows platform of the workstation MicroKernel attempted an operation using incompatible versions of the DLLs. Shut down the MicroKernel and make sure that you are using the most recent versions of the DLLs.

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

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 file name for the archival log file in the BLOG.CFG file. Ensure that the BLOG.CFG file indicates the correct file name for the archival log and ensure that the archival log file exists.

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

The status code can result from different situations. In one case, the database engine cannot find the archival log file associated with the specified file. By default, the MicroKernel names the archival log file the same as the logged file, but with a .log extension. However, you can specify a different file name for the archival log file in the BLOG.CFG file. Ensure that the BLOG.CFG file indicates the correct file name for the archival log and ensure that the archival log file exists.

Another cause can be that archival logging is still turned on for a file and your are trying to roll forward a log file of the same name. Because the database engine is actively logging to the log file, you cannot use it to roll forward.

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

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

The MicroKernel cannot contact the engine running on the gateway computer even though it can read the locator file. This might occur the following reasons:

An operation that caused the delta file to be read during Continuous Operations encountered invalid content. See also Using Continuous Operations in Advanced Operations Guide.

No user action is required if this status code occurs during a start of the PSQL engine. That is, PSQL was in Continuous Operations for one or more files when an outage occurred. The database engine does not attempt to roll in any invalid delta files.

In the scenario just described, the database engine logs a message reporting this status code. The OPEN operation that caused access to the bad delta file will still succeed even though the delta file contains invalid content. If a transaction log exists, lost transactions are rolled forward as normally occurs during an OPEN operation after an outage.

After the start and OPEN complete and any transactions are rolled forward, move the delta file with invalid content to a different directory. This allows you to perform Continuous Operations on the same data file again and retains the delta file with invalid content if you need technical support.

If an operation returns this status code while Continuous Operations is active, the operation did not successfully either read from or write to the delta file. In this case, the delta file may no longer be usable for Continuous Operations. Your best option is to do the following actions in the order indicated:

This status code may result if you use a large key size for an index and small page sizes. Index keys can fill the B-Tree to the allowable depth even though the B-Tree is not completely full.

To prevent this status code, try one or both of the following:

Certain conditions prevent Defragmenter from acting on a data file. Attempts to defragment the file return this status code. To diagnose and solve this problem, check for the following things:

In the current release, key-only files cannot be defragmented.

If you receive this error, then the action has been aborted because it was unable to lock a file before attempting to defragment it, and the allotted time for the request expired.

File defragmentation stopped because its validation could not be completed. No changes have been made to the file, and the operation of your system is unchanged.

The incomplete validation most likely occurred because you are using Microsoft Volume Shadow Copy Service (VSS). Defragmentation is not currently supported for a server engine in an environment where VSS has performed backup operations. However, if you restart the engine, you should be able to defragment files until VSS runs again.

The engine did not allow a requested defragmentation to begin because free disk space was too low. Defragmenter requires free disk space equal to the size of the file to be defragmented, plus a small amount for defragmenting operations. Files undergoing high write activity may need more space. If space becomes low on a disk volume where defragmentation occurs, the engine cancels defragmentation of files on that volume and returns this error code. The space needed to defragment a file is displayed in its analysis results.

File defragmentation stopped because its validation could not be completed. No changes have been made to the file, and the operation of your system is unchanged.

Incomplete validation most likely occurred because as defragmentation of a file nears completion, the engine inspects open file handles to determine whether the defragmented file poses a risk of record retrieval errors. If it determines a risk, then defragmentation validation fails. Defragmentation may succeed during a period of lower activity.

This status code became obsolete in MicroKernel version 6.15. It can indicate a temporary condition in which no system locks are currently available. The following are example cases:

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

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

If the file uses a page size smaller than 4,096 bytes, you can rebuild the file using Rebuild utility and set the page size to 4,096 bytes, to take advantage of the larger file size limit.

Obsolete starting in Pervasive.SQL 7. In the Pervasive.SQL 2000i SDK for a workstation environment, you attempted to access a data file with more than five MicroKernels at the same time. The Pervasive.SQL 2000i SDK for a Workgroup environment limits the number of concurrent file users to five engines.

The MicroKernel returns this status code for the following reasons:

The MicroKernel found a readable collate.cfg file, but the specific International Sorting Rule table is invalid.

The MicroKernel returns this status code in the following situations:

This error indicates one of the following types of mismatch:

Certain operations either use, or reserve the use of, the key number parameter as a subfunction number, rather than as a means to specify a file index to be used with the operation. (Note: This is also done in the GetEqual operation). This status code is returned if an application does not specify a valid subfunction number (via the key number parameter) to one of these operations:

The MicroKernel returns this status code in the following situations:

The same key number was generated by two different threads generating system keys.

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

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

While using the Btrieve API to alter database tables or entries, the system encountered SQL restrictions placed on the database by the SQL layer.

You cannot insert or delete chunks within the fixed portion of a record.

The MicroKernel detected a corrupt parameter in the Service Reply Block (SRB) because either:

To resolve this problem, reinstall PSQL to restore consistency among the installed components. If you still encounter the problem after reinstalling and restarting, contact Technical Support.

Several scenarios can result in this status code being returned:

This status code became obsolete in Pervasive.SQL 2000i. The related configuration setting is managed dynamically by the engine.

You may receive this status code due to one of the following:

The NULL indicator segment (NIS) cannot be the last segment of the key descriptor.

This status code indicates that your client software is not up-to-date with your remote database engine. You should only receive this status code if you are running V8 pre-release client software against a V8 general-release remote engine.

The solution for this issue is to uninstall your client software and install the latest V8 client.

Authentication to the database failed due to a wrong or missing username.

Authentication to the database failed due to a wrong or missing password.

Specify a valid database name for the machine.

A Btrieve login request failed because the client is already logged into the specified database.

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.

The URI connection string was formatted incorrectly. The first five bytes should be “btrv:”.

An Open or Create was issued using a URI connection string that contained neither a file name nor a table name.

An Open was issued using a URI connection string that contained no file name, and a table name that does not exist in FILE.DDF.

An Open was issued using a URI connection string that contained a full path file name that references a directory that does not exist as one of the data directories for the database.

Add the directory to the database using the database properties dialog in the PSQL Control Center (Windows) or the dbmaint utility (Linux).

The workstation MicroKernel engine returns the following status codes in Windows and DOS environments.

This status code became obsolete in MicroKernel version 7.0.

Version 6.x MicroKernels return this status code when the value specified for the Number of Locks configuration option is out of range. Pre-v6.0 MicroKernels return this status code when the value specified for the Multiple Locks configuration option is out of range.

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

This status code is received when the value for Cache Allocation Size is invalid.

In Pervasive.SQL 2000i, the Extended Operation Buffer Size setting became obsolete. This resource is managed dynamically by the MicroKernel. Its value 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 versions starting with MicroKernel v6.0 that are loaded with the Create Files in Pre-v6.x Format configuration option set to Yes. These options became obsolete in MicroKernel v7.8.

In Pervasive.SQL 7, the Open Files configuration setting became obsolete. This resource is managed dynamically by the MicroKernel.

For pre-v6.0 engines, the Open Files configuration option must be between 1 and 250, inclusive. For v6.0 and later engines, see the appropriate version documentation for valid range information.

The specified configuration options contain invalid or unidentifiable values.

This status code became obsolete in MicroKernel version 7.0.

The file name specified for the Transaction file name configuration option is not valid. Ensure that the transaction file name is correct.

This status code became obsolete in MicroKernel version 7.0.

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

This status code became obsolete in MicroKernel version 7.0.

Ensure that Compression Buffer Size option is set to a valid range. Check the target server configuration settings. See Advanced Operations Guide for valid range information.

This status code became obsolete in MicroKernel version 6.0.

The Maximum Number Of Files In A Transaction configuration option is invalid. Valid values are 0 to 18; the default is 12.

This status code became obsolete in MicroKernel version 7.0.

In the Windows environment, this status code is returned if the task entry table is full. You can change the value for the Number of Tasks option using the Setup utility.

In the DOS environment, this status code is returned if the BREQNT requester is used without the /t parameter when BTRVID calls are present in the application. Reload the requester with a non-zero value for the /t parameter. For information on DOS Requester parameters, see Getting Started with PSQL.

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

This status code became obsolete in MicroKernel version 6.0.

You attempted to initialize the MicroKernel when it was already initialized. To reinitialize the MicroKernel, close all files, end/abort all transactions, and issue Btrieve operation 25, using the BTRV interface before calling the initialization function.

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.

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

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

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

Correct any problems stated in the console message or error log, then retry the operation.

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

This section lists the status codes that the Btrieve Requesters generate.

The Btrieve requester encountered an internal error. Check the PSQL Event Log (pvsw.log) for more information.

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

A provided option is invalid in the current context. For example, a provided flag is unsupported or a provided integer is out of range for the called function or method.

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

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

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

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

The resource DLL is either missing or incompatible with the current version of the requester. If this happens, the MicroKernel reverts to its default settings and continues to run.

Check the PSQL Event Log (pvsw.log) for more information.

This section lists the XLT status codes you can receive.

This status code is returned when a Windows Socket initialization error occurs.

This status code is returned when the MicroKernel cannot establish a Remote Procedure Call (RPC) to the Relational Engine.

This section lists the status codes you can receive when using the named database features of the PSQL engine.

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.

Not a named database. Verify you have entered a valid database name.

The size of the sending buffer is too small and needs to be increased.

While creating a database, you specified a database name that already exists in the DBNAMES.CFG file. Specify a different, unique name for the database, or remove the existing database name first.

While creating a database, you specified an invalid database type. Specify a database type of either bound or unbound.

The path you specified for the bound, named database is invalid or the paths you specified for the data file locations are invalid. Ensure that the entered paths are either UNC paths or local paths and then retry the operation. Paths that contain mapped drive letters are not allowed.

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.

If returned from the Client Reporting Engine, this error indicates an attempt to create, drop, or modify a database on that system. You can perform these operations only locally on the system designated as the storage server or remotely by connecting to the storage server through PCC, bcfg, or other tool.

While creating a database, you specified an invalid RI setting. Specify only whether enforcement of referential integrity is on or off.

You cannot modify the definition of a named database if another user is modifying the definition or if a user is connected to it. You also cannot connect to a named database if someone is modifying its definition.

You cannot bind a data file referenced by a table in a bound, named database to another named database, or to another table in the same named database. For more information about bound databases, see Advanced Operations Guide.

The data dictionary files for a bound, named database cannot be referenced by another named database. For more information about bound databases, see Advanced Operations Guide.

An error occurred while attempting to generate the DBNAMES.CFG. The DBNAMES.CFG is created when the first database on the system is created. If the workstation DBNAMES.CFG file is being generated, ensure that the Windows directory in the Database Names Directory configuration option is a valid directory.

PSQL cannot create the database files for the bound database. Ensure that the data dictionary files do not already exist at the specified location. Remove any existing data dictionary files before creating the bound, named database. For more information about bound databases, see Advanced Operations Guide.

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

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

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.

This status code often indicates a situation in which the data dictionary files have been restored from a backup that was made when the database was bound. Either restore the data dictionary from a backup that is consistent with the bound state of the database, or bind and then unbind the database. The unbinding of the database removes the binding information from the data dictionary files.

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

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. This status code often indicates a situation in which the data files for the database was bound. Either restore your data files from a backup that is consistent with the bound state of the database, or bind and then unbind the database.

The unbinding of the database removes the binding information from the data files if the binding information is no longer needed.

These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.

These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.

These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.

These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.

These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.

These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.

These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.

These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.

These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.

These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.

These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.

These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.

Unspecified error.

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.

The MicroKernel router could not internally allocate memory. Check the PSQL Event Log (pvsw.log) for more information.

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

The MicroKernel resource DLL is either missing or incompatible with the current version of the router. If this happens, the MicroKernel reverts to its default settings and continues to run. Check the PSQL Event Log (pvsw.log) for more information.

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

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

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

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

This status code results from an invalid configuration. For example, if both client configuration options, Access > Use Local MicroKernel Engine and Access > Use Remote MicroKernel Engine are set to Off, the router has no valid path to take. If this situation occurs, set at least one of these options to On, depending on whether you are using a local engine, a remote Server engine, or both.

The MicroKernel router could not find NETAPI.DLL.

Access to the local engine is not possible because it is not loaded or could not be launched. You can receive this status code if you try to access a local file on a client and you do not have a 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 PSQL Event Log (pvsw.log) contains status code 3012 warning entries, perform the following steps.

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

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

An unexpected error occurred during the initialization of the MicroKernel router. Check the PSQL Event Log (pvsw.log) for more information.

The MicroKernel router encountered an internal error. Check the PSQL Event Log (pvsw.log) for more information.

The requester has more data to send the MicroKernel than the MicroKernel buffers can handle. This status code is only relevant to an engine running locally and does not apply to client/server environments.

To avoid this error, reduce the data buffer size to no bigger than 63 KB or 64,512 bytes.

The MicroKernel router is shut down and is not accepting any more requests.

A semaphore error occurred while trying to establish contact with the local engine. Check the PSQL Event Log (pvsw.log) for more information.

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 PSQL Event Log (pvsw.log) for more information.

The MicroKernel router rejected the response from the engine because it was badly formatted.Check the PSQL Event Log (pvsw.log) for more information.

A request to the MicroKernel router specified a data buffer length that resulted in a data packet size greater than 64 KB, which is the maximum. This can occur even if the data buffer length for the request is smaller than 64 KB because the MicroKernel router adds some packet overhead as it forms the data packet. Check the PSQL Event Log (pvsw.log) for more information.

This code is returned if the path is remote, the client configuration setting for Use Local MicroKernel Engine has been set to Off, and either:

This code is returned if a PSQL Linux requester attempts to connect to a Pervasive.SQL 2000 server that has Service Pack 2a or earlier, or a Pervasive.SQL V8 server without Service Pack 1.

This status code results if a second user attempts to access another user's database engine through the MicroKernel Engine. 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. If so, other users will not be able to connect to that engine.

One situation in which this status code may result is if a user starts the Workgroup Engine or Cache Engine in a Terminal Services session or by switching users through fast-user switching. Other users on the system cannot access that engine nor can they start their own copy of the engine. To allow multiple users access to a Workgroup Engine or Cache Engine in a Terminal Services session or through fast-user switching, start that engine as a service instead of as an executable.

The following status codes originate from the PSQL Network Services Layer (PNSL).

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:

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

No transport protocol that is common to both the target server engine and clients is available. For example, this status code could be caused by a client using SPX when the server engine only has TCP/IP available. Check the Supported protocols setting within the Communication protocols option for both the client and server. For more information on Communication protocols, see Advanced Operations Guide.

The PSQL 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:

Check the PSQL Event Log (pvsw.log) for more information if you receive this status code.

The PSQL Network Services Layer has insufficient memory to continue. Verify that you are not in a low memory condition.

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

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

The PSQL Network Services Layer attempted to send an application request to the target server and encountered a network specific error from the target. Check the PSQL Event Log (pvsw.log) for more information.

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

The PSQL Network Services Layer Server Routing Table is full. This table normally grows dynamically as needed. Verify that you are not in a low memory condition.

The PSQL Network Services Layer encountered a socket error while creating the local transport endpoint on the client side. Check the PSQL Event Log (pvsw.log) for more information.

When a PSQL Client cache engine is running under high load, the PSQL Network Services Layer may return this status code to indicate a mismatch in server and client requester data buffers. This error does not currently have an entry in the PSQL Event Log (pvsw.log). Status code 100 may also be associated with this behavior.

If this error is seen in when the client cache engine is running, make sure that you are using client components from PSQL v12 SP1 Update 2, PSQL v13, or later.

NSL was unable to return the access context on the specified session for the supplied object. There are several reasons why NSL could not obtain the context and it varies depending on the transport type.

For each user of the Network Services Layer, a task entry is created. If the maximum number of tasks has already been reached (512 and not configurable), this error is returned. Close any applications using PSQL that are no longer needed.

Check that the given file name is a valid file format and path.

This status code means that AutoReconnect was unsuccessful. The following messages will appear in PVSW.LOG:

This error is returned when the Scalable SQL interface attempts to communicate with the Pervasive.SQL 8 Network Services Layer (NSL).

The legacy Scalable SQL Engine is not supported in any combination with Pervasive.SQL 8 components. If you receive this error, search for and uninstall Scalable SQL (or Pervasive.SQL 7), and/or all if its components.

This section lists the status codes you can receive when using the Database Utilities (DBU).

If you receive this status code while attempting to start the PSQL Transactional or Relational Services, you are missing a key file. To resolve this problem, uninstall PSQL and reinstall it.

This status code may appear when all three communication protocols (TCP/IP, SPX and NetBios) are present. By default, all three of these protocols are enabled. To resolve this error message, disable one of the protocols in the server configuration.

Starting with Pervasive.SQL 8, the Server engine no longer supports NetBIOS.

This section lists status codes you can receive when using wire encryption or enabling database security. In Advanced Operations Guide, see PSQL Security for more information about these topics.

Your client configuration setting for Wire Encryption is set to Always, and the server to which you are trying to connect either has a Wire Encryption setting of Never, or the server has a version of less than 8.50 which does not support the Wire Encryption feature.

To resolve this condition, either change the Wire Encryption setting of the client to If Needed or change the Wire Encryption setting of the server to Always or If Needed.

To change the Wire Encryption setting:

Your client configuration setting for Wire Encryption is set to Never, and the server to which you are trying to connect has a Wire Encryption setting of Always.

To resolve this condition, change the Wire Encryption setting of the client to If Needed or Always.

To change the Wire Encryption setting:

This section lists the status codes that pertain to the data dictionary files. These codes often relate to errors involving referential integrity.

The column name cannot be used. The name may contain invalid characters or the name may be a duplicate name. See Naming Conventions in PSQL Programmer's Guide.

The column to which the foreign key is to be associated does not exist in the primary table.

This column cannot be made null. Certain data types, such as identity and small identity, cannot be null. Check the data type of the column. See Data Types in SQL Engine Reference for a list of the PSQL data types.

The number for the data type is not within the valid ranges. The current range is 0 to 30. See Data Types in SQL Engine Reference for a list of the PSQL data types.

The index number is less than zero. Negative numbers are not allowed as index numbers.

The number of index segments is greater than the maximum allowed. Note that the maximum number of keys is 119 for all file versions. The number of key segments can vary but must be within the limits shown by the following table.

The number of index segments that you may use depends on the file page size.

See status codes 26: The number of keys specified is invalid and 29: The key length is invalid for related information about index segments and the MicroKernel Engine.

See also Choosing a Page Size and Segmentation in PSQL Programmer's Guide.

The index name is already being used a column. Use a unique index name. See Naming Conventions in PSQL Programmer's Guide.

This section lists the status codes you can receive when using the Distributed Tuning Interface. See Btrieve API Guide for more information on this interface.

Specify a valid connection handle with the API call.

Specify a valid pointer with the API call.

Increase the buffer size. Some APIs report the required size in an out parameter.

This error can be returned in the following situations:

Specify a valid data type for the operation.

Check the valid range for the setting in the configuration reference section of Advanced Operations Guide.

Check the list of selection items to ensure all are valid selections. You can find the valid values in the configuration reference section of Advanced Operations Guide.

Specify a valid sequence number for the operation.

Data related to open files is not currently available.

The client ID needed for this operation is invalid. Specify a valid client ID.

You have insufficient access rights to perform the operation requested. Many DTI functions require administrative rights on the server. See Btrieve API Guide for more information on rights required for DTI operations.

The named database you are trying to add already exists. Specify a unique name for the named database.

The requested named database does not exist. Specify a valid named database.

Before you can use DTI functions, you must first initialize DTI by calling the PvStart() function. Then you can invoke DTI operations. When finished, use PvStop() to terminate the DTI session. See Btrieve API Guide for more information.

The operation you requested requires an open file.

Dictionary files for the specified database already exist.

Another process has the dictionary files in use. Close all other running applications and retry the operation.

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: []{}() ?*=!@,;

The DSN you are trying to create already exists. Specify a different name for the DSN.

The DSN you are trying to locate does not exist. Specify a valid DSN name.

Specify a valid open mode. For information, see DSN Open Mode in ODBC Guide.

A component needed for DTI is not loaded. Try restarting your PSQL engines.

You receive this status when trying to delete a database that shares DDF files with another database.

When creating a database, an invalid Btrieve Security Policy was specified. Specify one of:

The server you specified cannot be found. Check the server name and try again.

The connection could not be established because the client requester is not loaded.

The connection could not be established because the internal server name table is full.

The number of client connections for DTI is limited to 100.

The connection could not be established because the limit on client connections has been reached.

The connection could not be established because DTI encountered a permissions error. Check your username and password and try again.

The connection could not be established due to lack of memory resources.

No remote connection could be established. Check your network configuration.

The connection could not be established due to an unknown reason.

The remote connection to the server was lost. If this error persists, check your network configuration.

The database name you specified exceeds the length limit. In Advanced Operations Guide, see PSQL Database Concepts for information on valid database names.

When copying a database, you specified a smaller number of data paths than the original database contained.

The file name you specified already exists. Choose a unique file name for the operation.

The password you specified for the operation is not valid.

The path specified as the destination could not be found. Verify the path you provided to the API.

The path specified for dictionaries could not be found. Verify the path you provided to the API.

On Linux, this error can result if you try to create a database with PSQL Control Center and the owner of the directory is not psql. Ensure that the owner of the directory where you want to create the database is psql. Use the chown command to change ownership. For example, chown psql directoryname.

A parameter passed to DTI was invalid. See the DTI documentation in Btrieve API Guide for the valid options.

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.

The creation of a bound database requires data dictionary files (DDFs). For a bound database, ensure that the CREATE DATABASE statement or the Create New Database wizard also specifies the creation of dictionary files.

One or more characters sent by the client in a DTI function argument string are invalid and cannot be translated to the server’s encoding. Verify the function arguments.

One or more characters received from the server in a DTI function argument string are invalid and cannot be translated to the client’s operating system encoding. It may be necessary to use a different client machine.

The internal buffer is too small to process a DTI argument. One possible workaround is to use shorter arguments.

The translation option in the DTI function PvCreateDSN2() or PvModifyDSN2() specifies an invalid encoding. For the valid options, see the translate argument for these functions in Distributed Tuning Interface Guide.

The code page specified for the database is invalid (not supported by the database engine). Verify the code page and use one supported by the database engine. The code pages supported can be viewed from the Create Database dialog within PSQL Control Center. See New Database GUI Reference in PSQL User's Guide.

An API is being used that is not supported for this platform.

This section lists the status codes you can receive when using the License Administrator.

A session tried to release a license (for user count, session count, or data in use) but the session either had not acquired a license from the server or had acquired a license for a different product.

An application attempted to obtain the license (for user count, session count, or data in use) for a product, but no license has been authorized. Ensure that a license has been authorized for the product before attempting to obtain the license information.

The license key you attempted to authorize contains one or more invalid characters. All alphanumeric characters (upper or lower case) are permitted except for “i” and “o.” Lower case letters are automatically converted to upper case.

Correct any invalid characters in the license key and authorize the key again.

The license key an application attempted to authorize is not valid because the Product Type is invalid. The permissible types are permanent and temporary, and increase licenses for user count, session count, or data in use.

Ensure that you have a valid license key issued by Actian Corporation or by your application vendor if the PSQL database engine is embedded in an application.

The length of the license key you attempted to authorize exceeds the maximum length allowed for a key (30 characters). Ensure that the license key contains 30 characters.

The license key you are trying to deauthorize does not exist. The license key may have already been deauthorized.

If you are using the License Administrator GUI to deauthorize the key, press F5 to redisplay the list of authorized licenses. Check the refreshed list for the license key you were trying to deauthorize. If the license key still appears to exist, exit, then restart License Administrator.

All of the installed licenses are temporary ones that have expired. The values for user count, session count, or data in use no longer apply. You need to install a valid license, temporary or permanent, to provide new values for user count, session count, or data in use.

You have attempted to deauthorize a temporary license. Temporary licenses cannot be deauthorized; they become invalid after their expiration date. Verify that the license you want to deauthorize is a type that can be removed.

The license key you are attempting to authorize has already been authorized. You cannot reauthorize a license once it has been authorized unless you deauthorize it first. Temporary licenses cannot be deauthorized.

If you are using the License Administrator GUI to authorize the license, press F5 to redisplay the list of licenses. Check the refreshed list for the license you were trying to authorize. If the license still does not appear in the list, exit, then restart License Administrator.

The license key you attempted to authorize is not a valid license. Ensure that you have a valid license key issued by Actian Corporation or by your application vendor if the PSQL database engine is embedded in an application.

This status code is also displayed if your key is for a specific platform that does not match the platform on which you are attempting to authorize the license. For example, if your license key is for “Win64,” you cannot authorize the license for a Windows 32-bit operating system or on a Linux platform.

If you are using the License Administrator GUI to authorize the key, repaste or retype the key in the Key field, then click the button to authorize the key.

If your machine configuration changes between generating the authorization request code and the receipt of your authorization key data string from PSQL Support, then this status code can indicate that the authorization key data string no longer matches your machine, even though the product key itself is valid. In this case, you have two options:

Return your machine to its previous configuration, then attempt to authorize your license key again.

Or

Follow these steps:

The license key you attempted to authorize is not a valid license because the name of the PSQL product in the key is not PSQL Server or PSQL Workgroup. Only these two product IDs are supported at this time.

Ensure that you have a valid license key issued by Actian Corporation or by your application vendor if the PSQL database engine is embedded in an application.

The buffer assigned for the DTI function or DTO method is too small. Increase the size of the buffer. Refer to the applicable function in Distributed Tuning Interface Guide or to the applicable method in Distributed Tuning Objects Guide.

The length of the license key you attempted to authorize exceeds the maximum length allowed for a key (30 characters). Ensure that the license key contains 30 characters.

License Administrator is unable to connect to the remote server. This could indicate the following:

License Administrator is unable to connect to the database engine on the local machine where License Administrator is running. Ensure that a database engine is installed and running on the local machine. Follow the steps in Verifying Database Engine is Running in Getting Started with PSQL.

The license or licenses you are attempting to deauthorize cannot be deauthorized. Temporary licenses cannot be deauthorized. They become invalid after their expiration date.

Verify that the license is a type that can be deauthorized.

The temporary trial license you are attempting to authorize has expired, and one of the following is true:

The PSQL product cannot be installed without a valid license. Click Continue if you have a valid license to authorize. If you need an additional trial period, you can request a new trial license from Actian Corporation.

An authorized permanent key is required before an increase key can be authorized. The software vendor ID number for an increase key must match the vendor ID number for an authorized permanent key. Increase keys obtained from Actian Corporation are universal. That is, they are compatible with any permanent key from any vendor.

Ensure that you have a valid permanent key authorized before authorizing an increase key. Also ensure that the vendor ID numbers match if the increase key was obtained from a vendor, or use an increase key obtained from Actian Corporation. Vendor ID numbers can be verified with the License Administrator utilities. See License Administration in PSQL User's Guide.

The machine on which you are attempting to authorize a permanent license key already contains a permanent license key from the same vendor in the “active” state. You may not authorize more than one active permanent license key from the same vendor.

If a permanent license key has already been authorized from a vendor and is active, you may only authorize an increase for user count, session count, or data in use. Deauthorize the existing license key and then authorize the new permanent license key.

You may authorize another permanent key from the same vendor to the same machine if the existing permanent key is in a “failed validation” or a “disabled” state. That is, the existing permanent key is not active. If another permanent key is authorized while an existing key is in the “failed validation” state, the existing key changes state to “disabled.” The other permanent key then becomes the active key.

The license increase you are attempting to authorize would increase the value beyond the maximum limit for user count, session count, or data in use. You cannot increase the value beyond the maximum limit allowed by your license agreement.

The key or a related key you are trying to deauthorize requires that you have PSQL v10.13 or later installed. Upgrade to PSQL v10.13 or later and use the License Administrator utility to deauthorize the key.

The PSQL product version associated with the key you are trying to authorize does not match the PSQL product currently installed.

Make sure that the key you are using is correct and that you have the correct PSQL product installed.

The operating system associated with the key you are trying to authorize does not match the PSQL product currently installed.

Make sure that the key you are using is correct and that you have the correct PSQL product installed.

The engine type (Server or Workgroup) associated with the key you are trying to authorize does not match the PSQL engine currently installed.

Make sure that the key you are using is correct and that you have the correct PSQL product installed.

An authorized permanent key cannot be deauthorized because of its associated user count increase key. The user count increase key is in a Failed Validation or Disabled state or will move into a Failed Validation state during the next validation.

First, determine why there is a problem with the UCI key. Fix the problem and validate the UCI key. After that, reattempt the deauthorization of the authorized permanent key.

Some PSQL editions carry restrictions for certain features, such as licensing. For more information, contact technical support.

This section lists the status codes you can receive when authorizing your product.

One of the authorization libraries has produced an error that prevents further processing.

Try restarting the services or reinstalling PSQL and try authorization again. If this error persists, check the log file to determine the library name reported and contact PSQL Support.

The product key specified is invalid. Type, or paste, a valid product key and try to authorize the key again.

The product key appears to be a valid key, but failed to pass a checksum validation. A common reason is that the key was typed incorrectly. Another possibility is that a transmission error prevented the checksum validation.

Ensure that a valid product key is specified and try again to authorize the key.

The system encountered an error while trying to calculate the machine ID for the current session.

Ensure that you are logged on as an Administrator with full access rights and try authorizing or deauthorizing the key again. If you are using Windows Vista or subsequent Windows operating systems, turn off UAC. If you are authorizing or deauthorizing the key remotely, try the operation locally.

The system encountered difficulty while trying to acquire the machine configuration and has logged information to the PSQL logging repositories.

Ensure that you are logged on to the operating system as an Administrator with full access rights and try again to authorize or deauthorize the key. If you are using Windows Vista or later operating system, turn off UAC. If you are trying to authorize or deauthorize a key remotely, try the operation locally.

If you encounter this situation in a Windows operating system, ensure that WMI is working properly because it is the utility that acquires the machine configuration.

If you encounter this situation on a Linux operating system, ensure that the dmidecode utility is installed on the system and restart the PSQL daemon.

The PSQL database engine must be running before you can authorize or deauthorize a key. See Starting and Stopping the Database Engine in PSQL User's Guide for details.

The authorization call to DTI could not be completed or there is a problem connecting to the engine.

Try restarting the engine or services and try authorization again. If the problem persists, try reinstalling PSQL and try authorization again.

The string returned during authorization was empty or invalid.

Make certain that the PSQL is running and try authorization again.

The target engine tests for appropriate permissions prior to authorizing or deauthorizing 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 authorize or deauthorize the key. If you are using Windows Vista or subsequent Windows operating systems, temporarily turn off UAC.

If authorizing on Terminal Services, ensure that the setting for “Restrict Administrative Functions from a WTS Client” is off. In PCC, open the properties for the MicroKernel Router under Local Client. On the Properties dialog, ensure that the option “Restrict Administrative Functions from a WTS Client” is not selected.

This error can also be seen if you are running the PSQL Workgroup Engine as an application on Windows Vista or subsequent Windows operating systems and not running as an Administrator. Try closing the Workgroup Engine and then restarting w3dbsmgr.exe using the “Run as administrator” option. Another option is to uninstall the Workgroup Engine and reinstall it to run as a service.

Deauthorizing cannot occur because no key is available. A product key must be authorized before it can be deauthorized. Ensure that the product key you want to deauthorized has been authorized. The key may have been removed without first being deleted.

With License Administrator, verify the key that you want to deauthorize. See To Refresh the License Information List and To Display License Information, both in PSQL User's Guide. Try the deauthorization again and specify a valid key.

This version of PSQL does not support authorization. Try authorization from a machine running PSQL v10.13 or later.

The Internet connection cannot access the authorization server to obtain data needed for key validation.

Possible causes include, but are not limited to, the following:

If these explanations and solutions do not address your problem, contact PSQL Technical Support.

This status code applies only to Linux. The service files that process the Internet authorization and deauthorization processes were not found.

Verify that the web service file elsdid is located in /usr/local/psql/bin and that the file has execution permissions. Try restarting the services or reinstalling PSQL and attempting authorization again.

The authorization key data entered is not valid for the target machine. The key may have been malformed during the offline authorization process.

Try entering the authorization key data again or try offline authorization again.

A failure occurred during authorization of the key. Contact your product key vendor for assistance with troubleshooting.

The offline data failed to pass an internal checksum validation. A transmission error may have prevented the checksum validation. Try performing offline authorization again.

An internal error occurred while saving the offline file of authorization request data. Make sure that the directory has appropriate permissions and the target folder exists. Try saving the offline file again.

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.

The product key entered is invalid. Type or paste a valid product key and try again.

The target machine used for offline authorization is invalid. Make sure you are using the same machine for offline authorization as the machine on which you created the authorization request data file.

This status code can also be seen when the offline authorization utility licgetauth.exe is run on a Vista or later Windows OS machine without administrator privileges. To avoid this problem, run the utility from a command prompt window using the Run as an Administrator option.

The offline file is not consistent with the offline operation. Try starting the offline authorization from the beginning.

Offline authorization cannot be performed remotely. Perform offline authorization using a machine with a local Internet connection.

During offline authorization an internal error prevented processing. Try offline authorization again.

The licensing component on the local machine is incompatible with the remote licensing server. An older version of the licensing component on the local machine can result in this status code being returned. Contact the product key vendor for a compatible version of the local licensing component.

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 PSQL Customer Support.

The system is unable to decrypt the key because the key state is invalid. This error can occur if the system is unable to decrypt the key provided, or if after the key was decrypted the key no longer matches the key’s profile.

Make sure that the key you are using is correct or try using a new key. Contact PSQL Customer Support to report this situation.

The product key specified has been disabled in the authorization database on the remote licensing server. A product key may be disabled for various reasons. Contact PSQL Customer Support.

The product key entered is not the correct length. Product keys are either 25 or 30 characters in length, depending on the version of PSQL you are authorizing. Type or paste a valid product key and try again.

The product key has already been authorized on a different machine. First deauthorize the product key on the old machine, then try to authorize the key again on the new machine.

This status code can also result when you try to deauthorize a key on the machine where the key resides. A common cause is that changes to the hardware signature from when the key was authorized now prevent its deauthorization. In that case, repair the key.

The signature of the machine on which the key was originally authorized does not match the signature of the machine on which you are attempting to deauthorize the key. This happens in two situations: when a key is copied to another machine and when, due to hardware updates, a machine signature changes. In the first case, you need to purchase an additional permanent key. In the second case, you need to repair the key. After the correct action, reattempt the deauthorization.

The product key has already been authorized on the machine. Authorization is not required because it has already been performed.

A key can be on the machine but not in the authorization database on the remote licensing server. If so, clear the key on the machine using the “clear” option with the clilcadm utility, then authorize the key. See License Administrator Command Line Interface in PSQL User's Guide.

Deauthorization cannot occur because no key is available. A product key must be authorized before it can be deauthorized. Ensure that the product key you want to deauthorize has been authorized. The key may have been removed without first being deleted.

With License Administrator, verify the key that you want to deauthorize. See To Refresh the License Information List and To Display License Information, both in PSQL User's Guide. Try the deauthorization again and specify a valid key.

The authorization database on the remote licensing server lists no machine associated with the key. This situation can happen if you copy a VM image that includes a key already authorized, then you deauthorize the key on the original image and attempt to deauthorize the key on the copied VM image.

To prevent this status code, deauthorize the key before you copy the VM image. To remove a key on the copied VM image, clear the key using the CLI License Administrator. The “clear” option removes the key from the local machine without deauthorizing it. After you clear the key, authorize it on the copied VM image.

The operation attempted is not allowed on keys designated as Multimachine. Make certain you are using the correct key with the correct action.

In most circumstances, it is possible to authorize from within a virtual machine session. The only time this error message can appear is if the product key being authorized dates from the early PSQL v10 product line. If it appears, contact your product key vendor or try the authorization again outside of a virtual machine session.

The product key cannot be authorized from within a software debugger. Exit the debugger and try the authorization again.

The product key has already been authorized the maximum number of times allowed by the usage count.

A usage count allows you to authorize a product key again in the event of unforeseen circumstances on a particular machine. For example, if you had to replace the storage disk, you would have to reinstall the product and authorize the product key again on the same machine.

The product key has already been authorized the maximum number of times allowed.

Product keys have limited number of times they can be authorized and deauthorized. Contact your product key vendor if you need to authorize the product key again.

The product key has already been deauthorized the maximum number of times allowed. Product keys have limited number of times they can be authorized and deauthorized. Contact your product key vendor if you need to deauthorize the product key again.

The product key has already been repaired the maximum number of times allowed.

Product keys have limited number of repairs allowed. Contact your product key vendor if you need to repair the product key again.

The product key you are trying to authorize has already been authorized on the maximum number of machines allowed for the product purchased.

Deauthorize the key on one of the machines where the key has already been authorized before you try to authorize the product and use this key or contact your vendor to purchase additional licenses.

The maximum number of offline authorizations allowed for the product key has been met.

Product keys have limited number of offline authorizations allowed. Contact your product key vendor if you need more offline authorizations.

Temporary (non-removable) license keys may be authorized only once and cannot be deauthorized.

The temporary license has already been authorized and cannot be authorized again.

You are allowed to authorize a temporary license key once. A temporary license cannot be added to a machine that already uses it.

Changes to the target record were not committed because of multi-user access. Refresh, verify the record, then resubmit your changes.

The authorization server is currently busy. Please try authorizing again later.

The requested operation cannot be completed due to multi user access conflicts. Wait a few moments and try the operation again.

The requested server is inaccessible at this time. Try accessing the server again in 20-30 minutes.

The system detected an IP address from a country or city that is on the restricted embargo list. Please contact PSQL Customer Support if you feel you reached this message in error.

The credentials for the user are not recognized. Check the user credentials and try logging in again.

The current user does not have permission for the requested operation. Try logging in as a user with appropriate permissions, or request appropriate permission.

The requested user account is inactive. The user account needs to be authorized, or an active user account needs to be selected.

The license data prevents this key from entering the active state. Contact your product key vendor.

The OEM ID no longer exists. Select another OEM ID to use, or contact PSQL Support for assistance.

The account for the OEM is no longer active. Select an active OEM account, or contact PSQL Support for assistance.

The OEM user is no longer active. Select an active OEM user to use, or contact PSQL Support for assistance.

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.

Products are authorized to OEMs based on their contractual agreement with Actian Corporation. The requested product is not authorized for the current OEM. Select an authorized product to continue.

The maximum number of operations (resets or repairs) for the product key has been met. Product keys have limited number of resets and repairs allowed. Contact your product key vendor if you need to perform one of these operations again.

The maximum number of seats for the OEM has been met.

OEM accounts have a limited number of seats based on their contract with Actian Corporation. Contact PSQL Customer Support if you need to add seats to the OEM contract.

The maximum number of licenses for the OEM has been met.

OEM accounts have a limited number of licenses based on their contract with Actian Corporation. Contact PSQL Customer Support if you need to add licenses to the OEM contract.

The total maximum number of seats has been met. Accounts within an OEM have a limited number of seats based on their contract with Actian Corporation. Contact Actian Corporation if you need to add seats to the account.

The total maximum number of licenses has been met.

Accounts within an OEM have a limited number of licenses based on their contract with Actian Corporation. Contact Actian Corporation if you need to add seats to the account.

The requested value is either not defined or is greater than the maximum limit currently available.

The operating system requested for the product key is invalid for the current account. Make sure that you are using the correct account and select a valid operating system.

The product type requested for the product key is invalid for the current account. Make sure that you are using the correct account and select a valid product type.

The product type requested for the product key is invalid for the current account. Make sure that you are using the correct account and select a valid product type.

These status codes originate from the Component Management and Event Logging interface of the MicroKernel.

An interface was not initialized properly. Check the PSQL Event Log (pvsw.log) for more information.

The component could not be found. Check the PSQL Event Log (pvsw.log) for more information.

You receive this status code when one of the following occurs:

For locations of PSQL files, see Where are the PSQL files installed? in Getting Started with PSQL.

While using a multi threaded application, one thread shut down a component and other threads continue trying to use it.

This status code indicates that a general error occurred when checking or setting database security. The database engine was unable to associate the error with a more specific status code. If the error persists, contact Technical Support.

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

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

In its attempt to auto-load the Workgroup engine, the application failed to locate or load W3UPIXYY.DLL.

In its attempt to automatically load the Workgroup engine, the application discovered an incorrect version of W3UPIXYY.DLL. This problem may be caused by a corrupt version of W3UPIXYY.DLL.

In its attempt to auto-load the Workgroup engine, the application failed to create the system semaphore. This problem may have been caused by the operating system running out of resources.

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 8517 and in the pvsw.log file on one or more client workstations. The most likely cause is that your workstation client is configured to connect to a local Workgroup engine when one is not installed.

To prevent the client from attempting this connection, follow these steps:

In its attempt to auto-load the Workgroup engine, the application failed to load the MicroKernel, W3MKDE.DLL. This may have been caused by a missing W3MKDE.DLL.

The application lost its session with the Workgroup engine.

The application failed to enable the Btrieve access method in the Workgroup engine.

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 PSQL Event Log (PVSW.log) for more information.

This status code became obsolete in Pervasive.SQL 2000.

In its attempt to auto-load the Workgroup engine, the application failed to load the Scalable SQL, W3SSQL.DLL. This may have been caused by a missing W3SSQL.DLL.

The application failed to enable the SQL access method in the Workgroup engine.

This status code became obsolete in Pervasive.SQL 2000.

The application timed out during the initialization of the Scalable SQL engine. This may have been caused by an invalid configuration option or a malfunction of the Workgroup engine.

The application failed to disable the Btrieve access method in the Workgroup engine.

The application failed to unload the MicroKernel.

The application failed to disable the SQL access method.

This status code became obsolete in Pervasive.SQL 2000.

The application failed to unload Scalable SQL.

The application could not close the session with the Workgroup engine.

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. The most likely cause is that your workstation client is configured to connect to a local Workgroup engine when one is not installed.

To prevent the client from attempting this connection, follow these steps:

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.

In its attempt to auto-load the Relational Engine, the application failed to load the file, W3ODBCEI.DLL. This may have been caused by a missing W3ODBCEI.DLL.

The application timed out during the initialization of the Relational Engine module. This may have been caused by a bad engine configuration option or a malfunction of the Workgroup Engine.

The application failed to unload the Relational Engine module.

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.

This error occurs when W3DBSMGR.DLL failed to initialize the component library. You may also get more information about the problem that caused this error by setting the environment variable PVSW_DISP_LOAD_ERRS=AIF, and running the application again. This setting enables the Services DLL to display on-screen module load errors. However, this environment variable should only be set to diagnose module load errors. In all other cases, it should not be set.

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

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

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

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.

This section lists status codes returned by the SQL Connection Manager.

Restart your application, then access the data source again. Contact your system administrator if you continue to have problems.

The SQL Connection Manager may be inactive or using a different transport protocol from the client.

Verify that the relational service is running. On Windows, open the Services control panel and inspect the Pervasive.SQL Relational service.

Verify that the client and server are using the same communication protocols. Open PCC on the client workstation. In PSQL Explorer, right-click MicroKernel Router. Click Properties then Communication Protocols. Make sure the list of supported protocols is the same as that for the server. In PSQL Explorer, right-click on the server name. Click Properties then Communication Protocols.

This section lists status codes returned by the Relational Engine. 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 PSQL Technical Support.

A parameter was passed to an invalid internal API.

This status code may be returned in if the engine tries to allocate memory and is unsuccessful.

Free up some resources and try again. Reduce the Cache Allocation Size and/or Max MicroKernel Memory Usage configuration settings; or exit other applications on the computer.

While trying to open a file, a handle was not returned. Close some of your open programs and files and try again.

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.

The record length was larger than the maximum allowed and some data has been truncated. Record the steps taken to get this error and notify Technical Support.

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.

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.

Starting with Pervasive.SQL 8, the number of sessions allowed is allocated dynamically.

The file specified is not a valid database name or the database is corrupt.

There was an attempt to access a database that has been exclusively locked by another user. Wait until the user removes the exclusive lock before continuing.

You cannot rename a column and modify that column at the same time. For example, the following statement causes an error because column c1 is being renamed and modified at the same time: alter table t1 (rename column c1 to c2, modify column c1 int). However, the following statement is permissible because different columns are being renamed and modified: alter table t1 (rename column c1 to c2, modify column c3 int).

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

When you rename multiple columns, you can rename the same column only once. For example, the following statement causes an error because column c1 is being renamed twice: ALTER TABLE t1 (RENAME COLUMN c1 to c2, RENAME COLUMN column c1 to c3).

There was an attempt to access a table that has been exclusively locked by another user. Wait until the user removes the exclusive lock before continuing.

The name you specified for a table already exists in the dictionary. Select another name or remove the current table definition before trying again.

The requested operation cannot be performed because another user is accessing or modifying the table. Try the operation again.

The table or object your tried to access does not exist. Check for the correct name and path and try again.

You must perform an exclusive lock on the desired database before using DDL statements.

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.

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.

The name you specified for a table does not exists in the dictionary. Specify the name of an existing table and try the operation again.

The name you specified for a view does not exists in the dictionary. Specify the name of an existing view and try the operation again.

The name you specified for a trigger does not exists in the dictionary. Specify the name of an existing trigger and try the operation again.

The name you specified for an index does not exists in the dictionary. Specify the name of an existing index and try the operation again.

You have attempted to define the same index more than once in this definition. Rewrite the statement so the index is defined only once.

In some cases, you may be reissuing a create index statement because you cannot tell if your first statement succeeded. If you receive this error code under such conditions, then you can proceed on the assumption that your first create index operation was successful.

You tried to access an index that does not exist. Check the name and path and try again.

Null is not a valid parameter in the operation performed.

The column specified does not exist. Specify a correct column name.

The field specified for this table has already been defined.

You cannot create an index on column types BIT, LONGVARCHAR, or LONGVARBINARY. You must create the index using a different column type.

You cannot index a character column greater than 254 characters.

A query required a temporary table and there was no unique row identifier (index) to correlate the temporary table to the result set. Adding an index to the order by or group by column will often resolve this problem.

This status code is returned in the following situations:

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.

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.

This status code can also be returned when you try the following conditions:

An invalid username or password may have been specified. Check your password and try again. If you continue to have problems, check with your system administrator.

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.

The password specified was not correct. Check your password and try again. If you continue to have problems, check with your system administrator.

The user does not have the proper permissions to access the file.

You are trying to create a user-defined function (UDF) with the same name as an existing one. Modify the name of the UDF and execute the CREATE statement again.

The length of a user-defined function (UDF) name must be at least one character and cannot exceed 30 characters. Modify the name of the UDF to fit within the name length restrictions.

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 PSQL Relational Engine.) You cannot perform an INSERT operation on such data files.

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 PSQL Relational Engine.) You cannot perform an ALTER TABLE operation on such data files.

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 PSQL Relational Engine.) You cannot perform a CREATE TRIGGER operation on such data files.

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 PSQL Relational Engine.) You cannot perform a CREATE INDEX operation on such data files.

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 PSQL Relational Engine.) If a main table contains any OCCURS layouts, you must delete the OCCURS tables before you can delete the main 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 PSQL Relational Engine.) If a main table contains any REDEFINES layouts, you must delete the REDEFINES tables before you can delete the main 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 PSQL Relational Engine.) A main table can contain indexes to which an OCCURS table can map. If an OCCURS table maps a main table index, you cannot delete the main table index unless you first remove the mapping from the OCCURS 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 PSQL Relational Engine.) A table can contain a logical expression associated with the table. Such a table filter is referred to as a “push-down filter.”

You cannot update a column if it has a push-down filter defined it.

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 PSQL Relational Engine.) You cannot perform a CREATE INDEX operation on a variable record layout table unless you use the IN DICTIONARY keyword (CREATE INDEX . . . IN DICTIONARY . . .).

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.

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.

The total size of the fixed-length portion of a record has exceeded 65535 bytes. The total size of the fixed-length portion of any data record may not exceed 65535 bytes. The fixed-length portion of any data record is made up of the following:

Status code -3016 is returned if you attempt to create a table that exceeds this limit, or if you attempt modifications that would cause a table to exceed the limit.

To determine the size in bytes of the fixed-length portion of a record before you attempt to create a new table, you can use the following calculation:

(sum of the fixed-length column sizes in bytes) + (number of nullable columns) + (8 * number of variable-length columns) = record size in bytes

If you want to determine the size of the fixed-length portion of the record for an existing data file, you can use the BUTIL -STAT command to display a report that includes this information.

The path/file name for the data file is too long.

An attempt was made to alter a data type to an identity column.

An attempt was made to drop a system table.

The path/file name that you have specified is invalid. Specify a simple, relative path between 1-64 characters.

IN DICTIONARY is not allowed on bound databases.

A NOTE/LVAR column cannot coexist with a LONGVARCHAR/LONGVARBINARY. NOTE/LVAR must first be altered to a LONGVARCHAR/LONGVARBINARY.

Data conversion failed because data cannot be converted due to data type mismatch or data overflow. This error may occur if, for example, you attempt to alter a column of type DOUBLE to type FLOAT.

An attempt was made to convert a char/binary data to a char/binary column that has fewer bytes.

An attempt was made to convert a number to a numeric column that has less precision.

You cannot convert the value NULL into a non-nullable column.

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.

The password that you have specified is invalid. For maximum password length and allowed characters, see Identifier Restrictions by Identifier Type in Advanced Operations Guide.

The group or user name that you have specified is invalid. Specify a group or user name between 1and 30 characters. Numerals and letters only. Must start with a letter.

The procedure or trigger name that you have specified is invalid. Specify a name 1–30 characters long. Numerals and letters only. Must start with a letter.

The attempt to load MKC library failed. Ensure that the following file is located in the proper directory and is the correct version for your product.

Linux: libmkc.* is located in /usr/local/psql/lib directory.

An attempt was made to delete all indexes referencing a column. An index was encountered that is used in the primary key.

An attempt was made to delete all indexes referencing a column. An index was encountered that is used in the foreign key.

The requested operation cannot be performed on a column definition that is nullable.

You cannot define a foreign key if the column it references has a different type or attribute.

You cannot define a foreign key if the column it references has a different type or attribute.

You cannot define a foreign key if the column it references has a different type or attribute.

You cannot define a foreign key if the column it references has a different data type.

You cannot drop the referenced table because a trigger refers to it.

A group with the specified group name already exists. Use a different group name. If you continue to have problems, check with your system administrator.

If you just tried to create the specified group, but you tried again because you are not sure if it was created, this error indicates that the group was in fact created with the first attempt.

A user with the specified user name already exists. Use a different user name. If you continue to have problems, check with your system administrator.

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.

Cannot drop the table because it is referenced by a foreign key.

A trigger cannot be recursively called more than 30 times.

Cannot drop the index because it is referred to by a foreign key.

Nullable columns are not allowed in this operation.

You tried to create a foreign key before defining a primary key. Define a primary key before continuing.

The page size specified is invalid. Specify a page size that is a multiple of 512 and lies in the range 512-4,096 bytes (4,096 is the default).

The free space specified is not valid. Specify a free space percentage of 5, 10, 20, or 30 percent.

The page number specified is not valid. Specify a page number between 1-65,535.

The dictionary you are trying to access is already locked by another user. Wait until that user has unlocked the dictionary and try again.

A dictionary with the specified name already exists in that directory. Use a different dictionary name or path.

There was an attempt to define referential integrity upon a table that does not exist. Check the table name and try again.

The specified savepoint name already exists.

There can be only one ACS on a given index.

Cannot create true null column in a legacy table.

There are attributes of the Column Collating Sequence that conflict with the column definition.

Cannot drop the last column of a table. A table must contain at least one column.

The dictionary files for the specified database could not be found. Make sure the dictionary files exist and are in the proper directory.

The specified constraint name already exists.

While creating a column constraint name, the constraint name was too long, null, or had an invalid character.

You tried to set security privileges on a database that was not marked secure. First, enable security on the database.

You cannot secure a database that has already been secured.

Cannot perform an alter table on a legacy table.

Either an invalid user name was used or the password failed. Make sure you are using the proper login information. If you continue to have problems, check with your system administrator.

A group with the specified group name does not exist. Specify a valid group name. If you continue to have problems, check with your system administrator.

A group may not be deleted if there are still valid users in that group. Remove any user names before deleting the group.

Public is a default group and you are not allowed to change or add a synonym for the Public group.

Public is a default group and cannot be dropped from the list of groups.

Administrator is a default user and cannot be dropped from the list of users.

You cannot revoke privileges to a synonym; you must revoke privileges to the group the synonym refers to.

You cannot grant privileges to a synonym; you must grant privileges to the group to which the synonym refers.

Administrator is a default user and you cannot revoke privileges from the Administrator user name.

While converting a database, a file could not be renamed.

While converting a database, a file could not be deleted.

The index name is either too long or null.

The column name is either too long or null.

The table name is either too long or null.

You cannot bind a database that is already bound. A database can be bound only once.

The binding information does not match the information specified in the Data Dictionary Files.

You cannot bind a Data Dictionary File that is already bound.

You cannot unbind a Data Dictionary File that is not bound.

You cannot bind a database that uses shared Data Dictionary Files.

You cannot bind a database that uses shared data files.

You cannot drop the index because it is referenced by a primary key.

The table already has a primary key defined. You must delete the existing primary key and recreate it.

The file specified uses data file format v6.x or before and must be migrated to the current version of data file format before it can be used. Use the Rebuild utility to migrate file versions.

A foreign key cannot reference the table it is in.

While defining a foreign key, there was a foreign key delete rule violation.

Starting with PSQL v11 SP3, this code became obsolete. A restriction on a self-referencing table can be either cascade or restrict.

You must have a delete cascade defined in the foreign key to be able to do a self-referencing delete.

The binding information in the Data Dictionary File and data files does not match.

If a delete trigger exists on the table, a delete cascade in a foreign key is not allowed.

Delete name rules or attributes are not valid.

Update name rules or attributes are not valid.

Cannot delete a stored procedure, trigger or view while in use.

The collating sequence has a bad name, cannot be used, or may be corrupt.

The range for the specified number is invalid. Check the range for the option specified and enter a correct number.

While creating a foreign key, the database name specified is either too long or it is null.

See 2342: Not allowed to unbind database and change data locations at the same time.

See 2341: Not allowed to bind database and change data locations at the same time.

See 2340: Not allowed to create data dictionary and unbind database at the same time.

See 2338: Not allowed to change the dictionary location and create dictionary files at the same time.

See 2337: Not allowed to change data dictionary location and unbind database at the same time.

See 2336: Not allowed to change data dictionary location and bind database at the same time.

See 2335: Not allowed to change data locations and change name at the same time.

See 2334: Not allowed to create a data dictionary files and change name at the same time.

See 2333: Not allowed to unbind database and change name at the same time.

See 2332: Not allowed to bind database and change name at the same time.

See 2331: Not allowed to change data dictionary location and change name at the same time.

See 2330: Data file for a table is bound, but does not need to be bound.

See 2329: Data file for a table is not bound.

See 2326: Data dictionary files are bound, but do not need to be bound.

See 2325: Data dictionary files are already bound.

See 2324: Data dictionary files are not bound.

See 2316: Cannot create DDF files for the bound database.

See 2314: Cannot create DBNAMES.CFG file.

See 2313: The bound database cannot share data dictionary files.

See 2312: The bound database cannot share table data files.

See 2309: The database is in use.

See 2308: The specified RI flag is invalid.

See 2307: Cannot open DBNAMES.CFG file.

See 2306: DBNAMES.CFG could not be updated.

See 2305: The specified path for data dictionary or data file locations is invalid.

See 2304: The database type is invalid.

See 2303: The database name must be unique; the specified database name already exists.

See 2302: Invalid buffer length.

See 2301: The database name is invalid.

See 2300: No more database names are defined.

You receive this status code when you attempt to make a column-level GRANT statement for a right that is not supported. Only SELECT, INSERT and UPDATE are valid column level rights.

In SQL Engine Reference, see GRANT for more information about valid syntax.

See 3126: The PSQL Network Services Layer was unable to resolve the given file name into a valid path.

See 3124: PSQL Network Services Layer task table is full.

See 3119: No authentication context is available.

See 3115: PSQL Network Services Layer encountered a transport failure.

See 3114: The routing table of the PSQL Network Services Layer is full.

See 3112: Failure during receive from the target server.

See 3111: Failure during send to the target server.

See 3110: The network layer is not connected.

See 3108: The PSQL Network Services Layer detected an invalid session.

See 3107: The PSQL Network Services Layer is out of memory.

See 3106: The PSQL Network Services Layer encountered a connection failure.

See 3105: No available transport protocol for the PSQL Network Services Layer.

See 3104: The PSQL Network Services Layer encountered a permission error.

See 3103: Server name not found by PSQL Network Services Layer.

See 3022: The MicroKernel router could not send the request to the remote engine because the specified data buffer length resulted in a data packet object that is too large.

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

See 3020: An error occurred while loading the MicroKernel.

See 3019: The MicroKernel router encountered a semaphore error.

See 3018: The file is already closed.

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

See 3016: The MicroKernel router encountered an internal error.

See 3015: The MicroKernel router encountered an initialization error.

See 3014: The MicroKernel router cannot find an engine.

See 3013: The remote engine is inaccessible to the MicroKernel router because the networking component is not loaded.

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

See 3009: NETinterface.DLL is not loaded.

See 3008: Invalid configuration for MicroKernel router.

See 3006: The MicroKernel router detected an invalid session.

See 3005: The MicroKernel router encountered an operating system error.

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

See 3003: The MicroKernel router detected an incompatible network component.

See 3002: The MicroKernel router resource DLL is unavailable.

See 3001: Local access is unavailable to the MicroKernel router.

See 3000: The MicroKernel router encountered a memory allocation error.

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 PSQL Relational Engine.) A table can contain a logical expression associated with the table. Such a table filter is referred to as a “push-down filter.”

If you specify a push-down filter, you must also specify a relational operator for the filter (such as equals, greater than, less than, and so forth).

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 PSQL Relational Engine.) A table can contain a logical expression associated with the table. Such a table filter is referred to as a “push-down filter.”

If you specify a push-down filter for a column, the column must be in the table with which the filter is associated.

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 PSQL Relational Engine.) A table can contain a logical expression associated with the table. Such a table filter is referred to as a “push-down filter.”

If you specify a push-down filter, you must also specify a valid relational operator for the filter. Valid operators include less than, greater than, equal to, less than or equal to, greater than or equal to, and not equal to.

See 162: The client table is full.

See 161: A key has reached a maximum limit for user count, session count, or data in use, or has changed state to expired or disabled

See 149: SQL Trigger.

See 148: A roll forward error occurred.

See 147: The log segment is missing.

See 146: Duplicate system key.

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

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

See 138: The NULL indicator position is invalid.

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

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

See 134: The MicroKernel cannot read the International Sorting Rule.

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

See 132: The file has reached its size limit.

See 130: The MicroKernel ran out of system locks.

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

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

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

See 113: The MicroKernel is unable to open the archival log for the specified file.

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

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

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

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

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

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

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

See 104: The MicroKernel does not recognize the locale.

See 103: The chunk offset is too big.

See 102: Insufficient stack space is available.

See 101: Insufficient operating system memory is available.

See 100: No cache buffers are available.

See 97: The data buffer is too small.

See 96: A communications environment error occurred.

See 95: The session is no longer valid.

See 94: The application encountered a permission error.

See 93: The record lock types are incompatible.

See 92: The transaction table is full.

See 91: The application encountered a server error.

See 90: The redirected device table is full.

See 89: A name error occurred.

See 88: The application encountered an incompatible mode error.

See 87: The handle table is full.

See 86: The file table is full.

See 85: The file is locked.

See 84: The record or page is locked.

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

See 82: The MicroKernel lost positioning.

See 81: The MicroKernel encountered a lock error.

See 80: The MicroKernel encountered a record-level conflict.

See 79: A programming error occurred.

See 78: The MicroKernel detected a deadlock condition.

See 77: The application encountered a wait error.

See 76: There is a conflict on the referenced file.

See 73: The RI definition is out of sync.

See 72: The MicroKernel cannot open the RI referenced file.

See 71: There is a violation of the RI definitions.

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

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

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

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

See 65: The field offset is incorrect.

See 64: The filter limit has been reached.

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

See 62: The descriptor is incorrect.

See 61: The work space is too small.

See 60: The specified reject count has been reached.

See 59: The specified file already exists.

See 58: The compression buffer length is too short.

See 57: An expanded memory error occurred.

See 56: An index is incomplete.

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

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

See 53: The language interface version is invalid.

See 52: An error occurred while writing to the cache.

See 51: The owner name is invalid.

See 50: The file owner is already set.

See 49: The extended key type is invalid.

See 48: The alternate collating sequence definition is invalid.

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

See 46: Access to the requested file is denied.

See 45: The specified key flags are invalid.

See 44: The specified key path is invalid.

See 43: The specified record address is invalid.

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

See 41: The MicroKernel does not allow the attempted operation.

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

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

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

See 37: Another transaction is active.

See 35: The application encountered a directory error.

See 34: The specified extension name is invalid.

See 33: The MicroKernel cannot unload.

See 32: The file cannot be extended.

See 31: The file is already extended.

See 30: The file specified is not a MicroKernel file.

See 29: The key length is invalid.

See 28: The record length is invalid.

See 27: The key position is invalid.

See 26: The number of keys specified is invalid.

See 25: The application cannot create the specified file.

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

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

See 22: The data buffer parameter is too short.

See 21: The key buffer parameter is too short.

See 20: The MicroKernel or Btrieve Requester is inactive.

See 19: The application encountered an unrecoverable error.

See 18: The disk is full.

See 16: The application encountered an expansion error.

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

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

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

See 12: The MicroKernel cannot find the specified file.

See 11: The specified file name is invalid.

See 10: The key field is not modifiable.

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

See 8: The current positioning is invalid.

See 7: The key number has changed.

See 6: The key number parameter is invalid.

You attempted to create a stored procedure with the same name as an existing stored procedure. Follow these steps to recover:

Also see 5: The record has a key field containing a duplicate key value

See 4: The application cannot find the key value.

See 3: The file is not open.

See 2: The application encountered an I/O error.

See 1: The operation parameter is invalid.

The number and type of columns specified in the selection list must match the number and type of columns in the RETURNS clause. For example, the following code returns error -5022 because the RETURNS clause specifies one column but the SELECT list contains two columns:

A user-defined function (UDF) allows only IN parameters. Parameters of type OUT and INOUT are not allowed. For example, the following code returns an error because parameter “a” is designated as “out”:

A user-defined function (UDF) must contain a RETURN statement as the last statement in the function definition.

The name of a user-defined function (UDF) default parameter cannot be the same name as the UDF itself. For example, the following code is incorrect because both the UDF name and the parameter name are “myfunc”:

The RETURN statement within a user-defined function (UDF) must specify an argument because a UDF always returns a value.

The stored procedure returned one of the following error conditions:

An attempt was made to access a record that is locked by another user. Wait until the record is unlocked and try again.

The MicroKernel was unable to open the table. Make sure you have the proper access rights and table privileges.

The format used for the date is incorrect. Check for the correct ODBC date format and try again.

The ODBC driver failed to translate the data between the data source and the application. Check if the application is using SQLSetConnectOption to override the default translation dll.

The specified procedure name does not exist. Check the name of the procedure called and try again.

The ODBC driver does not support this predicate. Consult the SQL Engine Reference for valid predicates.

The code page value in the ODBC configuration file is invalid. See Advanced Operations Guide for valid configuration settings.

The name of a user-defined function (UDF) cannot be same as the name of a predefined scalar function. For a discussion of the scalar functions, see Scalar Functions in SQL Engine Reference.

You cannot delete an aggregate function or a predefined 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.

You cannot invoke a user-defined function (UDF) with a CALL statement. You must use a SELECT statement to invoke a UDF.

The name you specified for a user-defined function (UDF) does not exists in the dictionary. Specify the name of an existing UDF and try the operation again.

The name you specified for a stored procedure does not exists in the dictionary. Specify the name of an existing stored procedure and try the operation again.

The name that you specified for a stored procedure already exists in the dictionary. Specify another name or remove the current stored procedure definition and try the operation again.

The name that you specified for a user-defined function (UDF) already exists in the dictionary. Specify another name or remove the current UDF definition and try the operation again.

Tables, views, procedures, and functions can be associated with databases only. Triggers, indexes, and columns can be associated with databases and tables. The following statement is permissible because the database name and table name may be used to qualify an 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.

When the underlying authentication is domain authentication, this generic error may be returned. Most likely, something went wrong in the Active Directory Service Interfaces (ADSI) calls used to authenticate the domain user and get the user’s domain group associations.

When the underlying authentication is domain authentication, this error may be returned because the domain user cannot be found or the password is incorrect.

When the underlying authentication is domain authentication, this error may be returned because the domain user is not associated with a PSQL group in the database. The domain user must belong to an AD group that is associated with a PSQL group in the database being accessed.

When the underlying authentication is domain authentication, this error may be returned because the domain user belongs to more than one PSQL group in the database. The domain user must belong to an AD group that is associated with one, and only one, PSQL group in the database being accessed.

When the underlying authentication is domain authentication, this error may be returned because domain authentication is being used on a non-Windows platform.

When the underlying authentication is domain authentication, this error may be returned because the RPC Server is not available (Windows error 1722). This may occur when PSQL is querying the AD domain. The user should try logging in again.

When the underlying authentication is domain authentication, this error may be returned due to a session credential conflict (Windows error 1219) when the domain server is called. Multiple connections are not allowed to a server or shared resource by the same user while using more than one user name. Disconnect all previous connections to the server or shared resource and try again.

The PSQL_MOVE keyword (used with ALTER TABLE) must specify a column location greater than zero but less than the total number of columns. For example, assume that table t1 has only two columns, col1 and col2. Both of the following statement return an error:

The first statement attempts to move the column to position zero. The second statements attempts to move the column to position three, which is a number greater than the total number of columns (two).

Permissions on views and stored procedures are permissible only on databases with V2 metadata.

Certain functionality, such as trusted and non-trusted views and stored procedures, are permissible only on databases with V2 metadata.

The last (or the only) column in a partial index is not of data type CHAR or VARCHAR.

This section lists the informative status codes that the MicroKernel can return. The MicroKernel returns these codes as negative values.

The following statements return this status code when they execute successfully:

The MicroKernel made the requested change. However, if a SET OWNER statement was issued during a transaction, the change does not take effect until the user begins a new transaction.

The MicroKernel added the specified rows to the table(s).

The MicroKernel made the specified changes to the table(s).

The MicroKernel deleted the specified rows from the table(s).

The following statements return this status code when they execute successfully:

The MicroKernel successfully added the group, index, stored procedure, table, trigger, or view to the data dictionary.

The MicroKernel successfully made the requested change to the table dictionary definition. If a column has been altered (including a primary key or foreign key) without specifying the IN DICTIONARY keyword, the MicroKernel also changed the data file.

The following statements return this status code when successfully executed:

The MicroKernel successfully removed the group, index, stored procedure, table, trigger, or view from the dictionary. (Dropping a table also deletes the data file for that table.)

The current SQL statement contains substitution variables and cannot be executed until values are supplied for each variable. If your application allows substitution variables, refer to the documentation included with the application to determine how to use them.

The beginning or the end of the view has been reached.

The MicroKernel assigned the specified rights to the user or group.

The MicroKernel revoked the specified rights from the user or group.

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

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

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

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

This status code became obsolete in MicroKernel version 4.0, except when you are using v3.01 Compatibility mode.

This status code became obsolete in MicroKernel version 4.0, except when you are using v3.01 Compatibility mode. Starting in MicroKernel v4.0, stored procedures are used instead of stored statements.

The MicroKernel executed the stored statement that you submitted for execution.

The following statements return this status code when they execute successfully:

If you issued a DECLARE statement, the MicroKernel successfully created the cursor, variable, or condition you defined.

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

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

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

The FETCH statement returns this status code upon successful completion.

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

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

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