
2-42
Messages
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.
In addition, you can check the Microsoft website for a list of Win32
error codes.
MKDE-2053: Additional worker thread spawned
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.
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.
Comentarios a estos manuales