 | Status Codes and Messages (9.1 revision 1) |  |
|
This section lists the messages that the MicroKernel Database Engine generates.
Specify with PCC the correct value for the configuration properties setting. For versions prior to Pervasive.SQL 9, enter the correct value in the BSTART.NCF, BTI.INI, or BTI.CFG file. Note that, with Pervasive.SQL 9, MKDE configuration settings reside in the registry on Windows platforms and in the Pervasive registry for Linux and NetWare platforms.
Remove the invalid option from the BSTART.NCF, BTI.INI, or BTI.CFG file. Note that, with Pervasive.SQL 9, MKDE configuration settings reside in the registry on Windows platforms and in the Pervasive registry for Linux and NetWare platforms.
The system has insufficient memory to allow the MicroKernel to load as it is configured. Use the configuration properties to reconfigure the MicroKernel to use less memory, or unload any unnecessary applications.
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.
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).
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.
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 properties to specify the transaction log directory.
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.
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.
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.
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.
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.
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.
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.
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.
The MicroKernel returns this message when an internal error occurs. Try to perform the operation again.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
The MicroKernel Database Engine returns this message when a system error occurs. See MKDE-2039: System Error: nn.nn.nn for more information.
Specify a valid value. For more information about valid values, refer to Advanced Operations Guide.
This message is obsolete in Pervasive.SQL 2000i and later versions. This setting is managed dynamically by the engine.
This message is obsolete in Pervasive.SQL 2000i and later versions. This setting is managed dynamically by the engine.
This message is obsolete in Pervasive.SQL 2000i and later versions. This setting is managed dynamically by the engine.
Specify a valid value. For more information about valid values, refer to the Advanced Operations Guide.
This message is obsolete in Pervasive.SQL 2000i and later versions. This setting is managed dynamically by the engine.
Specify a valid value. For more information about valid values, refer to Advanced Operations Guide.
Specify a valid value. For more information about valid values, refer to Advanced Operations Guide.
Specify a valid path. For more information about valid values, refer to Advanced Operations Guide.
This message is obsolete in Pervasive.SQL 2000i and later versions. These settings are managed dynamically by the engine.
This message is obsolete in Pervasive.SQL 2000i and later versions.
This message is obsolete in Pervasive.SQL 2000i and later versions.
This message is obsolete in Pervasive.SQL 2000i and later versions. This setting is managed dynamically by the engine.
Obsolete in Pervasive.SQL 2000i and later versions. The number of Worker Threads is managed dynamically by the engine. If you receive this message, contact Pervasive Technical Support.
Obsolete in Pervasive.SQL 2000 and later versions.
Specify a valid value. For more information about valid values, refer to the Advanced Operations Guide.
Obsolete in Pervasive.SQL 2000 and later versions.
Obsolete in Pervasive.SQL 2000 and later versions.
Obsolete in Pervasive.SQL 2000 and later versions.
Obsolete in Pervasive.SQL 2000 and later versions.
Obsolete in Pervasive.SQL 2000 and later versions.
Obsolete in Pervasive.SQL 2000 and later versions.
The MicroKernel Database Engine returns this message when the value specified for the option_name option is invalid. Specify a valid value.
The MicroKernel Database Engine returns this message when the option you specified is not valid. Specify a valid configuration option.
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.
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.
The MicroKernel Database Engine returns this message when a system error occurs. See MKDE-2039: System Error: nn.nn.nn for more information.
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).
The MicroKernel returns this message if an internal error occurs.
Decrease the value of the Number of Input/Output Threads configuration option.
To perform this task, open Pervasive.SQL Control Center (see Starting PCC in Pervasive.SQL User's Guide). Right-click the database engine you wish to configure then click Properties. Click Performance Tuning then set the desired value for Number of Input/Output Threads.
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 32-bit platforms), \WINDOWS\SYSTEM (Windows 98/ME) or SYS:\SYSTEM (NetWare server).
The MicroKernel returns this message if an internal error occurs.
The MicroKernel returns this message when you attempt to shut down the Workgroup engine while at least one application is still using the engine. If you choose to shut down anyway, you could lose data.
The MicroKernel returns this message when it cannot open the file BTI.INI. Make sure that the file is in the home directory. Note that, with Pervasive.SQL 9, MKDE configuration settings reside in the registry on Windows platforms and in the Pervasive registry for Linux and NetWare platforms.
The MicroKernel returns this message if the BTI.INI file is flagged as read only and you attempt to changes to the BTI.INI configuration settings. 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. Note that, with Pervasive.SQL 9, MKDE configuration settings reside in the registry on Windows platforms and in the Pervasive registry for Linux and NetWare platforms.
Make sure that your computer's disk is not full and that you have the appropriate rights to the file. Note that, with Pervasive.SQL 9, MKDE configuration settings reside in the registry on Windows platforms and in the Pervasive registry for Linux and NetWare platforms.
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.
The MicroKernel returns this message when it encounters an error on a variable page. This message typically accompanies Status Code 2.
This message is obsolete in Pervasive.SQL 2000 and later versions.
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.
This is an informative message from the MicroKernel Database Engine. No action is required.
This is an informative message from the MicroKernel Database Engine. No action is required.
The MicroKernel Database Engine returns this message when a system error occurs. See MKDE-2039: System Error: nn.nn.nn for more information.
Configure the MicroKernel to use more cache memory or reduce the file's page size.
This message is obsolete in Pervasive.SQL 2000i and later versions. 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.
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 properties and save the current settings. This message pertains to legacy versions of the product and no longer applies to more recent versions. Also note that, with Pervasive.SQL 9, MKDE configuration settings reside in the registry on Windows platforms and in the Pervasive registry for Linux and NetWare platforms.
The MicroKernel returns this message when it cannot find values for any configuration options in the location they are normally stored (Pervasive registry for Linux and NetWare and the registry on Windows). This message means that the internal default values are being used and saved off to the default location. You may update the configuration options using the Pervasive.SQL Control Center. See Changing Your Configuration in Advanced Operations Guide.
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.
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.
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.
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.
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.
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.
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.
The MicroKernel returns this message when an internal error occurs. Try to perform the operation again.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
The MicroKernel returns this message when the value specified for the Cache Allocation Size option is invalid. Use the configuration properties and specify a valid value for this option. In Pervasive.SQL 8 and later, this value can be managed dynamically by the MicroKernel.
This message is obsolete in Pervasive.SQL 2000i and later versions.
The MicroKernel returns this message when the value specified for the Largest Compressed Record Size option is invalid. Use the configuration properties to specify a valid value for this option.
This message is obsolete in Pervasive.SQL 2000i and later versions. 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 properties and specify a valid value for this option.
The MicroKernel returns this message when the value specified for the Operation Bundle Limit option is invalid. Use the configuration properties and specify a valid value for this option.
This message is obsolete in Pervasive.SQL 2000i and later versions. 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 properties and specify a valid value for this option.
The MicroKernel returns this message when the value specified for the number of Number of Input/Output Threads option is invalid. Use the configuration properties and specify a valid value for this option.
This message is obsolete in Pervasive.SQL 2000i and later versions. 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 properties and specify a valid value for this option.
This message is obsolete in Pervasive.SQL 2000i and later versions. 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 properties and specify a valid value for this option.
The MicroKernel returns this message when the value specified for the Working Directory option is invalid. Use the configuration properties to specify a valid path.
The MicroKernel returns this message when the value for an option is not valid. Return to the configuration properties and enter the correct value.
The MicroKernel Database Engine returns this message when the option specified is not a valid option. Return to the configuration properties and remove the invalid option.
The MicroKernel returns this message when the server has insufficient memory to allow the MicroKernel to load as it is configured. Use the configuration properties to reconfigure the MicroKernel to use less memory (Cache Allocation Size attribute), or unload any unnecessary applications.
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.
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).
The MicroKernel returns this message if an internal error occurs.
This message is obsolete in Pervasive.SQL 2000i and later versions. This setting is managed dynamically by the engine.
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 32-bit platforms), \WINDOWS\SYSTEM (Windows 98/ME), and SYS:\SYSTEM (NetWare servers).
The MicroKernel returns this message when a system error occurs.
The MKDE uses the System Error messages to record unexpected errors resulting from an operating system call made by the MKDE. For example, if an error is returned when the MKDE makes a file
I/O call to the operating system, that error is recorded in the PVSW.LOG as a System Error.
The format of a system error is id.op.rc where:
|
id
|
Unique System Error identifier
|
|
op
|
Btrieve operation being performed at the time
|
|
rc
|
any unexpected return code from the operating system.
|
The id corresponds to a section of code in the MKDE where the OS call took place. There are different id ranges depending on which MKDE is being used:
The common code base contains all the file I/O requests, variable allocations, caching, and so on. The platform specific ranges cover other file open, close, read, and lock requests. These codes can guide us to the portion of the MKDE code that was executing when the System Error occurred. For example, ids ranging from 110 - 124 correspond to the I/O Subsystem of the MicroKernel where disk I/O calls are made, and system errors with these ids usually correspond to file corruption problems. A list of ids is not available publicly because a list without the specific MKDE and knowledge of the code would not have much value.
The second piece of the system error is the operation code. This corresponds to the Btrieve request that was being processed when the error occurred. For example, a 5 is a GetEqual operation. Refer to the Pervasive.SQL Programmer's Reference for more information about Btrieve operation codes. If the system error occurs while the MKDE is performing some task that is not specifically associated with a Btrieve operation, the op will be set to -1.
The third piece of the system error is the OS return code. The meaning of the values reported here varies depending on the OS call made and the type of failure that occurred. A return code value of 0 for different IDs is likely to have different meanings, but in each case the OS did not return an actual error code. An example of a System Error where the OS return code is zero is when the OS call returns successfully, but the data returned by the call is not what was expected. In many cases, the appearance of an occasional System Error does not indicate a problem. It is likely that the operation being performed was retried without an error and processing continued normally.
If there is a problem that would cause an interruption in normal operation, the System Error would correspond to a Pervasive status code returned to the application. For example, attempting to access a physically corrupt file will produce a system error such as 116.5.0 and the application will receive a Status Code 2.
If you experience repeated occurrences of a specific system error, along with abnormal behavior of your application, and you do not find any documentation in our knowledge base about the error, you should contact Pervasive with a description of the system error and the symptoms of failure in the application, and we will provide more details about the system error in question.
The list of Win32 error codes is available on Microsoft's website at http://msdn.microsoft.com/library/en-us/debug/base/system_error_codes.asp.
The main list of OS error codes is contained in the Microsoft file, winerror.h.
Note
One common System Error on NetWare 4.x is a known problem in NetWare's Turbo FAT feature. This problem often manifests as error "MKDE-103 System Error 116.2.0." For more information on this particular topic, please see the following Pervasive Knowledge Base article:
http://support.pervasive.com/eSupport/publisher.asp?id=6bf0e1d1-09fb-11d5-b22b-00508b5d6b61
This message is obsolete in Pervasive.SQL 2000i and later versions. Worker threads are 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.
The MicroKernel returns this message when it is unable to create a named pipe for the pipe-manager thread.
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.
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.
The MicroKernel returns this message when it encounters an error during the service initialization.
The MicroKernel returns this message when none of the supported protocols are installed on the computer. The Communications Server cannot initialize.
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.
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.
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.
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.
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.
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.
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.
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.
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.
The MicroKernel returns this message when an internal error occurs. Try to perform the operation again.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
|
Chapter contents
Prev topic: BUTIL
|