User`s guide

1-54
Status Codes
1 to 199
MicroKernel
Database
Engine Status
Codes
This section describes status codes that the MicroKernel returns.
1: The operation parameter is invalid
The specified operation does not exist or is not valid.
You may receive this error if you are running a general-release
version of the V8 client software against a pre-release version of the
V8 database engine. If this is the case, you must uninstall your
database engine and install the general release version.
2: The application encountered an I/O error
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 file is damaged, and you must recover it. Refer to the
Advanced Operations Guide for more information on recovering
files.
 For pre-v6.0 data files, there is a large pre-image file inside a
transaction, and there is not enough disk space for a write to the
pre-image file.
 For pre-v6.0 data files, there is one pre-image file for multiple
data files. For example, if you name the data files
CUSTOMER.ONE and CUSTOMER.TWO, both files have pre-
image files named CUSTOMER.PRE.
 For pre-v6.0 data files that are larger than 768 MB, there is a
conflict among locking mechanisms. The file has not been
corrupted. Your application can retry the operation until the
conflict is resolved (when the competing application releases the
lock your application requires).
 A pre-v6.0 Btrieve engine attempted to open a v6.x or later
MicroKernel file.
 With Btrieve for Windows NT Server Edition v6.15.445, 32 bit
Windows application may return Status 2 or “MKDE
Terminated with Service Specific Error 0” after running an
application for an extended period of time.