MKDE

---

MicroKernel Database Engine Messages

This section lists the messages that the MicroKernel Database Engine generates.

MKDE-12: The value specified for the -option is invalid

Enter the correct value in the BSTART.NCF, BTI.INI, or BTI.CFG file.

MKDE-13: The option specified is not a valid option

Remove the invalid option from the BSTART.NCF, BTI.INI, or BTI.CFG file.

MKDE-16: There is insufficient memory to load the MicroKernel Database Engine

The system has insufficient memory to allow the MicroKernel to load as it is configured. Use the Configuration utility to reconfigure the MicroKernel to use less memory, or unload any unnecessary applications.

MKDE-20: The log file filename cannot be written. Check disk space

If the disk is full, free some space by deleting any unnecessary files. When an error occurs while writing to the transaction log file, the MicroKernel attempts to resume transaction logging after every update to a data file containing system data. Therefore, when the condition causing the error is corrected (for example, when more disk space is made available), the MicroKernel automatically resumes transaction logging.

MKDE-25: The file filename is rolling back

Rolling back is the procedure the MicroKernel uses to restore a file to a consistent state after a system crash. This procedure undoes the most recent changes to the file (changes in the most recent system transaction).

MKDE-51: Program initialization failed; the program was not loaded

This is an informative message that the MicroKernel returns when an error prevents the MicroKernel from loading. Another message accompanies this one and provides more specific information about the nature of the error.

MKDE-57: The file filename cannot be created in the log segment directory xxxx

While initializing, the MicroKernel could not find the specified transaction log segment directory, so it did not load. Ensure that the directory exists and that the MicroKernel has rights to it. (This is not a problem for the NetWare NLM version of the MicroKernel, because it has rights to all directories and files.) Use the Configuration utility to specify the transaction log directory.

MKDE-58: The file filename cannot be opened in the log segment directory xxxx

While initializing, the MicroKernel could not open the specified file in the transaction log segment directory, so it did not load. Ensure that the directory and file exist and that the MicroKernel has rights to it. (This is not a problem for the NetWare NLM version of the MicroKernel, because it has rights to all directories and files.) Another possibility is that someone has opened the file with an exclusive lock. Use the Monitor utility to see if another user has locked the file.

MKDE-59: The log segment file filename cannot be created

The MicroKernel could not create the specified transaction log segment file. Ensure that you have enough disk space and that the MicroKernel has rights to the file. (This is not a problem for the NetWare NLM version of the MicroKernel, because it has rights to all directories and files.) Another possibility is that someone has opened the file with an exclusive lock. Use the Monitor utility to see if another user has locked the file.

This error can occur while the MicroKernel is loading, or later, during normal operations. If it occurs while the MicroKernel is loading, the loading fails and no operations are possible until the problem is corrected. If the error occurs later, during normal operations, there are some additional issues to consider.

If the MicroKernel is already loaded when an error occurs creating the transaction log file, it ceases transaction logging; however, the MicroKernel attempts to resume transaction logging after every update to a data file containing system data. Therefore, when the condition causing the error is corrected (for example, when more disk space is made available), the MicroKernel automatically resumes transaction logging.

MKDE-75: The log file format is invalid

The MicroKernel returns this message when the log segment file format is incompatible. Ensure that the version of the MicroKernel doing the roll forward is the same as the version of the MicroKernel that created the log file.

MKDE-76: An Open operation failed on "xxxx" with MKDE error nn

The MicroKernel returns this message during roll forward operations when a MKDE error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, "Status Codes" for a description of Status Code nn.

MKDE-77: An unexpected MKDE error nn occurred on INSERT to "xxxx"

The MicroKernel returns this message during roll forward operations when an Insert error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, "Status Codes" for a description of Status Code nn.

MKDE-78: An unexpected MKDE error nn occurred on UPDATE in "xxxx"

The MicroKernel returns this message during roll forward operations when an Update error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, "Status Codes" for a description of Status Code nn.

MKDE-79: An unexpected MKDE error nn occurred on DELETE from "xxxx"

The MicroKernel returns this message during roll forward operations when a Delete error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, "Status Codes" for a description of Status Code nn.

MKDE-80: The system is out of memory

The MicroKernel returns this message when the server has insufficient memory to allow the program to operate. Unload any unnecessary applications and retry the roll forward operation.

MKDE-81: An internal error nn occurred

The MicroKernel returns this message when an internal error occurs. Try to perform the operation again.

MKDE-82: An unexpected MKDE error nn occurred on GET EQUAL in "xxxx"

The MicroKernel returns this message during roll forward operations when a Get Equal error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, "Status Codes" for a description of Status Code nn.

MKDE-83: The log file is corrupt

The MicroKernel returns this message when the log segment file is damaged and unreadable. The Log Segment Manager cannot perform roll forward operations using this log segment.

MKDE-84: An error occurred while reading the log file

The MicroKernel returns this message when an error prevents the program from reading the log segment file. The MicroKernel cannot perform roll forward operations using this log segment.

MKDE-85: An unexpected MKDE error nn occurred on CREATE INDEX to filename

The MicroKernel returns this message during roll forward operations when an error occurs on a CREATE INDEX operation for the specified file. You may have a corrupted file, or your log file may be corrupt. Refer to Chapter 1, "Status Codes" for a description of Status Code nn.

MKDE-86: An unexpected MKDE error nn occurred on DROP INDEX to filename

The MicroKernel returns this message during roll forward operations when an error occurs on a DROP INDEX operation for the specified file. You may have a corrupted file, or your log file may be corrupt. Refer to Chapter 1, "Status Codes" for a description of Status Code nn.

MKDE-87: An unexpected MKDE error nn occurred on BEGIN TRANSACTION to filename

The MicroKernel returns this message during roll forward operations when an error occurs on a BEGIN TRANSACTION operation for the specified file. You may have a corrupted file, or your log file may be corrupt. Refer to Chapter 1, "Status Codes" for a description of Status Code nn.

MKDE-88: An unexpected MKDE error nn occurred on END TRANSACTION to filename

The MicroKernel returns this message during roll forward operations when an error occurs on an END TRANSACTION operation for the specified file. You may have a corrupted file, or your log file may be corrupt. Refer to Chapter 1, "Status Codes" for a description of Status Code nn.

MKDE-89: An unexpected MKDE error nn occurred on ABORT TRANSACTION to filename

The MicroKernel returns this message during roll forward operations when an error occurs on an ABORT TRANSACTION operation for the specified file. You may have a corrupted file, or your log file may be corrupt. Refer to Chapter 1, "Status Codes" for a description of Status Code nn.

MKDE-90: An unexpected MKDE error nn occurred on CLOSE to filename

The MicroKernel returns this message during roll forward operations when an error occurs on a CLOSE operation for the specified file. You may have a corrupted file, or your log file may be corrupt. Refer to Chapter 1, "Status Codes" for a description of Status Code nn.

MKDE-91: An unexpected MKDE error nn occurred on GET POSITION to filename

The MicroKernel returns this message during roll forward operations when an error occurs on a GET POSITION operation for the specified file. You may have a corrupted file, or your log file may be corrupt. Refer to Chapter 1, "Status Codes" for a description of Status Code nn.

MKDE-92: An unexpected MKDE error nn occurred on BEGIN TRANSACTION

The MicroKernel returns this message during roll forward operations when an error occurs on a BEGIN TRANSACTION operation. You may have a corrupted file, or your log file may be corrupt. Refer to Chapter 1, "Status Codes" for a description of Status Code nn.

MKDE-93: An unexpected MKDE error nn occurred on END TRANSACTION

The MicroKernel returns this message during roll forward operations when an error occurs on an END TRANSACTION operation. You may have a corrupted file, or your log file may be corrupt. Refer to Chapter 1, "Status Codes" for a description of Status Code nn.

MKDE-94: An unexpected MKDE error nn occurred on ABORT TRANSACTION

The MicroKernel returns this message during roll forward operations when an error occurs on an ABORT TRANSACTION operation. You may have a corrupted file, or your log file may be corrupt. Refer to Chapter 1, "Status Codes" for a description of Status Code nn.

MKDE-98: The log segment file SYS:SYSTEM/MKDE/LOG/0000XXX.LOG cannot be created. There was an error on the console or in the PVSW.LOG

The MicroKernel could not create the specified transaction log segment file. Ensure that you have enough disk space and that the MicroKernel has rights to the file. (This is not a problem for the NetWare NLM version of the MicroKernel, because it has rights to all directories and files.) Another possibility is that someone has opened the file with an exclusive lock. Use the Monitor utility to see if another user has locked the file.

This error can occur while the MicroKernel is loading, or later, during normal operations. If it occurs while the MicroKernel is loading, the loading fails and no operations are possible until the problem is corrected. If the error occurs later, during normal operations, there are some additional issues to consider.

If the MicroKernel is already loaded when an error occurs creating the transaction log file, it ceases transaction logging; however, the MicroKernel attempts to resume transaction logging after every update to a data file containing system data. Therefore, when the condition causing the error is corrected (for example, when more disk space is made available), the MicroKernel automatically resumes transaction logging.

MKDE-1001: The value specified for Cache Allocation is invalid

Specify a valid value. For more information about valid values, refer to the Pervasive.SQL Advanced Operations Guide.

MKDE-1002: The value specified for Longest Compressed Record Size is invalid

This message is obsolete in Pervasive.SQL 2000i. This setting is managed dynamically by the engine.

MKDE-1003: The value specified for Extended Operation Buffer Size is invalid

This message is obsolete in Pervasive.SQL 2000i. This setting is managed dynamically by the engine.

MKDE-1004: The value specified for Open Files is invalid

This message is obsolete in Pervasive.SQL 2000i. This setting is managed dynamically by the engine.

MKDE-1005: The value specified for Operation Bundle Limit is invalid

Specify a valid value. For more information about valid values, refer to the Pervasive.SQL Advanced Operations Guide.

MKDE-1007: The value specified for Number of Handles is invalid

This message is obsolete in Pervasive.SQL 2000i. This setting is managed dynamically by the engine.

MKDE-1008: The value specified for I/O Threads is invalid

Specify a valid value. For more information about valid values, refer to the Pervasive.SQL Advanced Operations Guide.

MKDE-1009: The value specified for Maximum Sort Buffer is invalid

Specify a valid value. For more information about valid values, refer to the Pervasive.SQL Advanced Operations Guide.

MKDE-1010: The path specified for Temporary Sorting Files is invalid

Specify a valid path. For more information about valid values, refer to the Pervasive.SQL Advanced Operations Guide.

MKDE-1011: Info: The Number of Handles cannot be less than the Number of Open Files

This message is obsolete in Pervasive.SQL 2000i. These settings are managed dynamically by the engine.

MKDE-1015: The value specified for Maximum Record Size is invalid

Specify a valid value for this option. For more information about valid values, refer to the Pervasive.SQL Advanced Operations Guide.

MKDE-1017: The value specified for System Transaction Hold Limit is invalid

Specify a valid value for this option. For more information about valid values, refer to the Pervasive.SQL Advanced Operations Guide.

MKDE-1019: The value specified for Maximum Active Clients is invalid

This message is obsolete in Pervasive.SQL 2000i. This setting is managed dynamically by the engine.

MKDE-1020: The value specified for Worker Threads is invalid

Specify a valid value for this option. For more information about valid values, refer to the Pervasive.SQL Advanced Operations Guide.

MKDE-1021: The value specified for Thread Priority Delta is invalid

Specify a valid value. For more information about valid values, refer to the Pervasive.SQL Advanced Operations Guide.

MKDE-1022: The value specified for Initiation Time Limit is invalid

Specify a valid value. For more information about valid values, refer to the Pervasive.SQL Advanced Operations Guide.

MKDE-1023: The value specified for Disk I/O Wait Time is invalid

Specify a valid value. For more information about valid values, refer to the Pervasive.SQL Advanced Operations Guide.

MKDE-1024: The value specified for Page Write Group Size is invalid

Specify a valid value. For more information about valid values, refer to the Pervasive.SQL Advanced Operations Guide.

MKDE-1025: The value specified for Auto-Terminate Delay is invalid

Specify a valid value. For more information about valid values, refer to the Pervasive.SQL Advanced Operations Guide.

MKDE-1026: The value specified for Number of Lines Allocated is invalid

Specify a valid value. For more information about valid values, refer to the Pervasive.SQL Advanced Operations Guide.

MKDE-1027: The value specified for Message Log File Limit is invalid

Specify a valid value. For more information about valid values, refer to the Pervasive.SQL Advanced Operations Guide.

MKDE-1028: The path specified for Home Directory is invalid

Specify a valid path. For more information about valid values, refer to the Pervasive.SQL Advanced Operations Guide.

MKDE-1030: The value specified for the option_name option is invalid

The MicroKernel Database Engine returns this message when the value specified for the option_name option is invalid. Specify a valid value.

MKDE-1032: The option specified is not a valid option

The MicroKernel Database Engine returns this message when the option you specified is not valid. Specify a valid configuration option.

MKDE-1152: MKDE cannot get sufficient memory to complete the operation

The computer has insufficient memory to allow the MicroKernel to load as it is configured. Configure the MicroKernel to use less memory or unload any unnecessary applications.

MKDE-1156: The log file filename cannot be written. Check disk space

The transaction log file filename cannot be written. Check the disk space. If the disk is full, free some space by deleting any unnecessary files. When an error occurs while writing to the transaction log file, the MicroKernel attempts to resume transaction logging after every update to a data file containing system data. Therefore, when the condition causing the error is corrected (for example, when more disk space is made available), the MicroKernel automatically resumes transaction logging.

MKDE-1161: The file filename is rolling back

Rolling back is the procedure the MicroKernel uses to restore a file to a consistent state after a system crash. This procedure undoes the most recent changes to the file (changes in the most recent system transaction).

MKDE-1164: Error creating/accessing semaphore

The MicroKernel returns this message if an internal error occurs.

MKDE-1165: Error creating execution thread

Decrease the values for either the Number of Worker Threads or the I/O Threads configuration option.

MKDE-1166: Could not open Pervasive Event Log file. This file is created in the home directory. Verify that the directory is present and sufficient space is available

The MicroKernel returns this message when it cannot create the Pervasive Event Log (PVSW.LOG) in the directory. Make sure that the disk on your computer is not full.

The home directory is defined as \WINNT\SYSTEM32 (Windows NT), \WINDOWS\SYSTEM (Windows 95) or SYS:\SYSTEM (NetWare server).

MKDE-1167: Could not create IPC queue

The MicroKernel returns this message if an internal error occurs.

MKDE-1168: Client(s) active - Shutdown anyway?

The MicroKernel returns this message when you attempt to shut down the MicroKernel Workstation/Workgroup engine while at least one application is still using the MicroKernel. If you choose to shut down anyway, you could lose data.

MKDE-1169: Could not open BTI.INI

The MicroKernel returns this message when it cannot open the BTI.INI file. Make sure that the file is in the home directory.

MKDE-1171: The file BTI.INI is flagged as read only. The MKDE can temporarily override this attribute to save the current settings. Do you wish to continue?

The MicroKernel returns this message if the BTI.INI file is flagged as read only and you attempt to save changes to the MKDE configuration settings, which are stored in the BTI.INI file. If you choose to continue, the MicroKernel updates the BTI.INI file but maintains its read only status. If you choose not to continue, the MicroKernel does not update the BTI.INI file. You can still change the configuration settings, but they are only in effect for the current session.

MKDE-1172: Error writing to BTI.INI

Make sure that your computer's disk is not full and that you have the appropriate rights to the file.

MKDE-1175: I/O error - filename

The MicroKernel returns this message when it encounters an I/O error while reading from or writing to a file. This message typically accompanies Status Code 2.

MKDE-1176: Variable page error - filename

The MicroKernel returns this message when it encounters an error on a variable page. This message typically accompanies Status Code 2.

MKDE-1177: Help is not available

The MicroKernel returns this message when it cannot find the help file (BTRIEVE.HLP). Make sure that the file is located in the home directory.

MKDE-1178: Resources allocated

This is an informative message from the MicroKernel Database Engine. No action is required.

MKDE-1179: Resources released

This is an informative message from the MicroKernel Database Engine. No action is required.

MKDE-1180: System Error: nn.nn.nn

The MicroKernel Database Engine returns this message when a system error occurs.

MKDE-1183: Not enough available cache to complete an operation

Configure the MicroKernel to use more cache memory or reduce the file's page size.

MKDE-1184: Unable to set number of file handles to requested value. Maximum open files reduced to nn.

This message is obsolete in Pervasive.SQL 2000i. This setting is managed dynamically by the engine.

The MicroKernel is unable to set the Maximum Open Files to the value you specified; instead the MicroKernel uses the value indicated in the message. To avoid receiving this message, run fewer applications at the same time.

MKDE-1192: Settings read from NOVDB.INI - To change to BTI.INI, save current settings

The MicroKernel returns this message when it loads and then finds a NOVDB.INI file where it expects to find the BTI.INI file. To use the BTI.INI file, open the configuration utility and save the current settings.

MKDE-1193: The MKDE is using default settings

The MicroKernel returns this message when it loads and cannot find values for one or more configuration options. The BTI.INI file is incomplete or missing. You may update the configuration options using the Pervasive Control Center.

MKDE-1194: Additional worker thread spawned

The MicroKernel returns this message when it must create more worker threads than the number specified by the Number of Worker Threads configuration option. To avoid receiving this message, increase the value for the Number of Worker Threads option.

MKDE-1207: The log file format is invalid

The MicroKernel returns this message when the log segment file format is incompatible. Ensure that the version of the MicroKernel doing the roll forward is the same as the version of the MicroKernel that created the log file.

MKDE-1208: An Open operation failed on "xxxx" with MKDE error nn

The MicroKernel returns this message during roll forward operations when an error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, "Status Codes" for a description of Status Code nn.

MKDE-1209: An unexpected MKDE error nn occurred on INSERT to "xxxx"

The MicroKernel returns this message during roll forward operations when an Insert error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, "Status Codes" for a description of Status Code nn.

MKDE-1210: An unexpected MKDE error nn occurred on UPDATE in "xxxx"

The MicroKernel returns this message during roll forward operations when an Update error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, "Status Codes" for a description of Status Code nn.

MKDE-1211: An unexpected MKDE error nn occurred on DELETE from "xxxx"

The MicroKernel returns this message during roll forward operations when a Delete error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, "Status Codes" for a description of Status Code nn.

MKDE-1212: The system is out of memory

The MicroKernel returns this message when the server has insufficient memory to allow the program to operate. Unload any unnecessary applications and retry the roll forward operation.

MKDE-1213: An internal error nn occurred

The MicroKernel returns this message when an internal error occurs. Try to perform the operation again.

MKDE-1214: An unexpected MKDE error nn occurred on GET EQUAL in "xxxx"

The MicroKernel returns this message during roll forward operations when a Get Equal error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, "Status Codes" for a description of Status Code nn.

MKDE-1215: The log file is corrupt

The MicroKernel returns this message when the log segment file is damaged and unreadable. The MicroKernel cannot perform roll forward operations using this log segment.

MKDE-1216: An error occurred while reading the log file

The MicroKernel returns this message when an error prevents the program from reading the log segment file. The MicroKernel cannot perform roll forward operations using this log segment.

MKDE-1217: An unexpected MKDE error nn occurred on CREATE INDEX to filename

The MicroKernel returns this message during roll forward operations when an error occurs on a CREATE INDEX operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, "Status Codes".

MKDE-1218: An unexpected MKDE error nn occurred on DROP INDEX to filename

The MicroKernel returns this message during roll forward operations when an error occurs on a DROP INDEX operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, "Status Codes".

MKDE-1219: An unexpected MKDE error nn occurred on BEGIN TRANSACTION to filename

The MicroKernel returns this message during roll forward operations when an error occurs on a BEGIN TRANSACTION operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, "Status Codes".

MKDE-1220: An unexpected MKDE error nn occurred on END TRANSACTION to filename

The MicroKernel returns this message during roll forward operations when an error occurs on an END TRANSACTION operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, "Status Codes".

MKDE-1221: An unexpected MKDE error nn occurred on ABORT TRANSACTION to filename

The MicroKernel returns this message during roll forward operations when an error occurs on an ABORT TRANSACTION operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, "Status Codes".

MKDE-1222: An unexpected MKDE error nn occurred on CLOSE to filename

The MicroKernel returns this message during roll forward operations when an error occurs on a CLOSE operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, "Status Codes".

MKDE-1223: An unexpected MKDE error nn occurred on GET POSITION to filename

The MicroKernel returns this message during roll forward operations when an error occurs on a GET POSITION operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, "Status Codes".

MKDE-1224: An unexpected MKDE error nn occurred on BEGIN TRANSACTION

The MicroKernel returns this message during roll forward operations when an error occurs on a BEGIN TRANSACTION operation. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, "Status Codes".

MKDE-1225: An unexpected MKDE error nn occurred on END TRANSACTION

The MicroKernel returns this message during roll forward operations when an error occurs on an END TRANSACTION operation. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, "Status Codes".

MKDE-1226: An unexpected MKDE error nn occurred on ABORT TRANSACTION

The MicroKernel returns this message during roll forward operations when an error occurs on an ABORT TRANSACTION operation. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, "Status Codes".

MKDE-2001: The value specified for the Cache Allocation option is invalid

The MicroKernel returns this message when the value specified for the Cache Allocation Size option is invalid. Use the Configuration utility and specify a valid value for this option.

MKDE-2002: The value specified for the Largest Compressed Record Size option is invalid

This message is obsolete in Pervasive.SQL 2000i.

The MicroKernel returns this message when the value specified for the Largest Compressed Record Size option is invalid. Use the Configuration utility to specify a valid value for this option.

MKDE-2004: The value specified for the Number of Open Files option is invalid

This message is obsolete in Pervasive.SQL 2000i. This setting is managed dynamically by the engine.

The MicroKernel returns this message when the value specified for the Number of Open Files option is invalid. Use the Configuration utility and specify a valid value for this option.

MKDE-2005: The value specified for the Operation Bundle Limit option is invalid

The MicroKernel returns this message when the value specified for the Operation Bundle Limit option is invalid. Use the Configuration utility and specify a valid value for this option.

MKDE-2007: The value specified for the Number of Handles option is invalid

This message is obsolete in Pervasive.SQL 2000i. This setting is managed dynamically by the engine.

The MicroKernel returns this message when the value specified for the Number of Handles option is invalid. Use the Configuration utility and specify a valid value for this option.

MKDE-2008: The value specified for the I/O Threads option is invalid

The MicroKernel returns this message when the value specified for the number of Number of Input/Output Threads option is invalid. Use the Configuration utility and specify a valid value for this option.

MKDE-2009: The value specified for the Active Clients option is invalid

This message is obsolete in Pervasive.SQL 2000i. This setting is managed dynamically by the engine.

The MicroKernel returns this message when the value specified for the Active Clients option is invalid. Use the Configuration utility and specify a valid value for this option.

MKDE-2010: The value specified for the Sort Buffer Size option is invalid

This message is obsolete in Pervasive.SQL 2000i. This setting is managed dynamically by the engine.

The MicroKernel returns this message when the value specified for the Sort Buffer Size option is invalid. Use the Configuration utility and specify a valid value for this option.

MKDE-2011: The path specified for the Temporary Directory option is invalid

The MicroKernel returns this message when the value specified for the Working Directory option is invalid. Use the Configuration utility and specify a valid path.

MKDE-2012: The value specified for the -option option is invalid

The MicroKernel returns this message when the value for an option is not valid. Return to the Configuration utility and enter the correct value.

MKDE-2013: The option specified is not a valid option

The MicroKernel Database Engine returns this message when the option specified is not a valid option. Return to the Configuration utility and remove the invalid option.

MKDE-2015: MKDE cannot get sufficient memory to complete the operation

The MicroKernel returns this message when the server has insufficient memory to allow the MicroKernel to load as it is configured. Use the Configuration utility to reconfigure the MicroKernel to use less memory, or unload any unnecessary applications.

MKDE-2019: The log file filename cannot be written. Check disk space

The MicroKernel returns this message when log file filename cannot be written. Check the disk space. If the disk is full, free some space by deleting any unnecessary files. When an error occurs while writing to the transaction log file, the MicroKernel attempts to resume transaction logging after every update to a data file containing system data. Therefore, when the condition causing the error is corrected (for example, when more disk space is made available), the MicroKernel automatically resumes transaction logging.

MKDE-2024: The file filename is rolling back

The MicroKernel returns this message when the file filename is rolling back. Rolling back is the procedure the MicroKernel uses to restore a file to a consistent state after a system crash. This procedure undoes the most recent changes to the file (changes in the most recent system transaction).

MKDE-2027: Error creating/accessing semaphore

The MicroKernel returns this message if an internal error occurs.

MKDE-2028: Error creating execution thread

This message is obsolete in Pervasive.SQL 2000i. This setting is managed dynamically by the engine.

MKDE-2029: Could not open Event Log file.

The MicroKernel returns this message when it cannot create the Pervasive Event Log (PVSW.LOG) in the home directory. Make sure that the home directory exists and that the disk on your computer is not full. Also, ensure that the MicroKernel has rights to the home directory and event log file.

The Home directory is defined as \WINNT\SYSTEM32 (Windows NT), \WINDOWS\SYSTEM (Windows 95), and SYS:\SYSTEM (NetWare servers).

MKDE-2039: System Error: nn.nn.nn

The MicroKernel returns this message when a system error occurs.

MKDE-2053: Additional worker thread spawned

This message is obsolete in Pervasive.SQL 2000i. This setting is managed dynamically by the engine.

This is an informative message the MicroKernel returns when it must create more worker threads than the number specified by the Number of Worker Threads configuration option. To avoid receiving this message, increase the value for the Number of Worker Threads option.

MKDE-2055: Error creating named pipe

The MicroKernel returns this message when it is unable to create a named pipe for the pipe-manager thread.

MKDE-2060: Error reading the registry. Error code: nn

The MicroKernel returns this message when it is unable to find a predefined setting in the registry. Use the -REGINSTALL startup parameter next time you start the MicroKernel. This parameter forces the MicroKernel to recreate its section in the registry with the default values for each configuration option.

MKDE-2061: Error writing the registry. Error code: nn

The MicroKernel returns this message when it encounters an error while trying to write into the registry. Use the -REGINSTALL startup parameter next time you start the MicroKernel. This parameter forces the MicroKernel to recreate its section in the registry with the default values for each configuration option.

MKDE-2065: Error calling Service Control dispatcher

The MicroKernel returns this message when it encounters an error during the service initialization.

MKDE-2067: There is no suitable protocol available on this computer

The MicroKernel returns this message when none of the supported protocols are installed on the computer. The Communications Server cannot initialize.

MKDE-2068: The communications server is not available

The MicroKernel returns this message when it encounters an error loading the Communications Server. Make sure the system path includes the directory where the Communications Server that was shipped with this version of the MicroKernel.

MKDE-2075: The transaction log file LAST_SEG.LOG cannot be opened

The MicroKernel returns this message when the log file format is invalid or the Transaction Log Directory does not exist. Ensure that the version of the MicroKernel that returns this message is the same as the version of the MicroKernel that created the log file.

MKDE-2076: An Open operation failed on "xxxx" with MKDE error nn

The MicroKernel returns this message during roll forward operations when an error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, "Status Codes" for a description of Status Code nn.

MKDE-2077: The log file format is invalid

The MicroKernel returns this message when the log segment file format is incompatible. Ensure that the version of the MicroKernel doing the roll forward is the same as the version of the MicroKernel that created the log file.

MKDE-2078: An Open operation failed on "xxxx" with MKDE error nn

The MicroKernel returns this message during roll forward operations when an error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, "Status Codes" for a description of Status Code nn.

MKDE-2079: An unexpected MKDE error nn occurred on INSERT to "xxxx"

The MicroKernel returns this message during roll forward operations when an Insert error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, "Status Codes" for a description of Status Code nn.

MKDE-2080: An unexpected MKDE error nn occurred on UPDATE in "xxxx"

The MicroKernel returns this message during roll forward operations when an Update error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, "Status Codes" for a description of Status Code nn.

MKDE-2081: An unexpected MKDE error nn occurred on DELETE from "xxxx"

The MicroKernel returns this message during roll forward operations when a Delete error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, "Status Codes" for a description of Status Code nn.

MKDE-2082: The system is out of memory

The MicroKernel returns this message when the server has insufficient memory to allow the program to operate. Unload any unnecessary applications and retry the roll forward operation.

MKDE-2083: An internal error nn occurred

The MicroKernel returns this message when an internal error occurs. Try to perform the operation again.

MKDE-2084: An unexpected MKDE error nn occurred on GET EQUAL in "xxxx"

The MicroKernel returns this message during roll forward operations when a Get Equal error occurs. The MicroKernel returns the specified status code for the specified file. Refer to Chapter 1, "Status Codes" for a description of Status Code nn.

MKDE-2085: The log file is corrupt

The MicroKernel returns this message when the specified log segment file is damaged and unreadable. The MicroKernel cannot perform roll forward operations using this log segment.

MKDE-2086: An error occurred while reading the log file

The MicroKernel returns this message when an error prevents the program from reading the log segment file. The MicroKernel cannot perform roll forward operations using this log segment.

MKDE-2087: An unexpected MKDE error nn occurred on CREATE INDEX to filename

The MicroKernel returns this message during roll forward operations when an error occurs on a CREATE INDEX operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, "Status Codes".

MKDE-2088: An unexpected MKDE error nn occurred on DROP INDEX to filename

The MicroKernel returns this message during roll forward operations when an error occurs on a DROP INDEX operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, "Status Codes".

MKDE-2089: An unexpected MKDE error nn occurred on BEGIN TRANSACTION to filename

The MicroKernel returns this message during roll forward operations when an error occurs on a BEGIN TRANSACTION operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, "Status Codes".

MKDE-2090: An unexpected MKDE error nn occurred on END TRANSACTION to filename

The MicroKernel returns this message during roll forward operations when an error occurs on an END TRANSACTION operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, "Status Codes".

MKDE-2091: An unexpected MKDE error nn occurred on ABORT TRANSACTION to filename

The MicroKernel returns this message during roll forward operations when an error occurs on an ABORT TRANSACTION operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, "Status Codes".

MKDE-2092: An unexpected MKDE error nn occurred on CLOSE to filename

The MicroKernel returns this message during roll forward operations when an error occurs on a CLOSE operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, "Status Codes".

MKDE-2093: An unexpected MKDE error nn occurred on GET POSITION to filename

The MicroKernel returns this message during roll forward operations when an error occurs on a GET POSITION operation for the specified file. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, "Status Codes".

MKDE-2094: An unexpected MKDE error nn occurred on BEGIN TRANSACTION

The MicroKernel returns this message during roll forward operations when an error occurs on a BEGIN TRANSACTION operation. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, "Status Codes".

MKDE-2095: An unexpected MKDE error nn occurred on END TRANSACTION

The MicroKernel returns this message during roll forward operations when an error occurs on an END TRANSACTION operation. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, "Status Codes."

MKDE-2096: An unexpected MKDE error nn occurred on ABORT TRANSACTION

The MicroKernel returns this message during roll forward operations when an error occurs on an ABORT TRANSACTION operation. You may have a corrupted file, or your log file may be corrupt. For more information about Status Code nn, refer to Chapter 1, "Status Codes."