Protocol mismatch between client cache and remote engine The NULL indicator cannot be the last segment The MicroKernel cannot allow unauthorized access to files in a secure MicroKernel databaseĪ key has reached a maximum limit for user count, session count, or data in use, or has changed state to expired or disabled The MicroKernel has detected an unacceptable value in the key number The MicroKernel cannot find the specified Alternate Collating Sequence in the file The specified ISR table is corrupt or otherwise invalid The MicroKernel cannot read the International Sorting Rule More than 5 concurrent users attempted to access the same data file Maximum number of B-Tree index levels reached The file is owned by another MicroKernel engine acting as a Gateway The MicroKernel cannot access the archival logging dump file The archival log for the specified file is invalid The MicroKernel is unable to open the archival log for the specified file The specified file is in use by another client The specified filename was not found in the archival logging configuration file The MicroKernel cannot access the archival logging configuration file The application attempted to perform a chunk operation on a pre-v6.0 fileĪn unknown error was encountered either creating or accessing a semaphore The MicroKernel cannot perform a Get Next Chunk operation The file cannot be created with Variable-tail Allocation Tables(VATs) The MicroKernel does not recognize the locale Insufficient operating system memory is available The application encountered a permission errorĪ communications environment error occurred The application encountered a server error The application encountered an incompatible mode error
#BTRIEVE CLIENT UPDATE#
The MicroKernel attempted to update or delete a record that was read outside the transaction The MicroKernel encountered a record-level conflict The MicroKernel detected a deadlock condition There is a conflict on the referenced file The MicroKernel cannot open the RI referenced file There is a violation of the RI definitions The Delete operation specified a file that is damaged The MicroKernel cannot perform the RI Delete Cascade operation The MicroKernel cannot open the SQL data dictionary files The maximum number of open databases has been exceeded The data buffer parameter specified on an Insert Extended operation is invalid The specified reject count has been reached The compression buffer length is too short The application specified an invalid attribute for an AUTOINCREMENT key The variable-length portion of the record is corrupt The language interface version is invalid The alternate collating sequence definition is invalidĪn error occurred while writing to the cache The number of files opened exceeds the maximum allowed The MicroKernel does not allow the attempted operationĪ file previously opened in Accelerated mode was not closed The file access request exceeds the maximum number of files allowed The MicroKernel encountered a transaction control file I/O errorĪ Begin Transaction operation must precede an End/Abort Transaction operation The application encountered a directory error The file specified is not a MicroKernel file The application cannot create the specified file
The page size or data buffer size is invalid
The position block parameter is not 128 bytes long The MicroKernel or Btrieve Requester is inactive The application encountered an unrecoverable error The application encountered an expansion error The application encountered an I/O error during pre-imaging The MicroKernel cannot create or open the pre-image file The MicroKernel could not open the extension file for an extended file The MicroKernel cannot find the specified file The operation encountered the end-of-file The record has a key field containing a duplicate key value The application cannot find the key value
#BTRIEVE CLIENT CODE#
To get more information on these status codes, or codes outside of the 1 - 199 range, use the status code checker page.
Omega for DOS, or other applications running on Btrieve 6 or earlier are unlikely to return values outside of this range. Errors related to a database operation being attempted by this application usually fall within the 1 - 199 value range allocated to Btrieve API calls. When the Pervasive.SQL database engine needs to report an issue it returns a non-zero status code to the application (Omega, WIPC, etc.).
0 kommentar(er)
