 | Status Codes and Messages (v9 SP2 (9.5) revision 1) |  |
|
This section lists the status codes you can receive from the MicroKernel router, which receives requests from the Btrieve requesters and routes them to the correct version of the MicroKernel.
The MicroKernel router could not internally allocate memory. Check the Pervasive Event Log (PVSW.LOG) for more information.
A call to the MicroKernel failed. This is most likely the result of an incorrect configuration. For example, if the MicroKernel is unavailable because of configuration settings and the file to be opened is local, then the MicroKernel router returns this status code.
The MicroKernel resource DLL is either missing or incompatible with the current version of the router. If this happens, the MicroKernel reverts to its default settings and continues to run. Check the Pervasive Event Log (PVSW.LOG) for more information.
The networking services component is not compatible with this version of the MicroKernel router. The most likely cause is that the Networking services DLL has been replaced by an older version. Check the Pervasive Event Log (PVSW.LOG) for more information.
The MicroKernel is not responding to requests from the MicroKernel router. Verify that the MicroKernel is running.
The MicroKernel router encountered an unexpected error from the operating system, such as a shared memory failure. Check the Pervasive Event Log (PVSW.LOG) for more information.
The session information contained in a position block is invalid. This status code occurs for one of the following reasons:
This status code results from an invalid configuration. For example, if both client configuration options, Access4Use Local MicroKernel Engine and Access4Use Remote MicroKernel Engine are set to Off, the router has no valid path to take. If this situation occurs, set at least one of these options to On, depending on whether you are using a local engine, a remote Server engine, or both.
The MicroKernel router could not find NETAPI.DLL.
The MicroKernel router could not find the NetWare API DLLs.
This status code is only relevant to the Win16 MicroKernel router. You receive this status code when the Use Thunk option is set to On and the thunk path is not accessible. Possible causes include:
Check the Pervasive Event Log (PVSW.LOG) for more information.
Access to the local engine is not possible because it is not loaded or could not be launched. You can receive this status code if you try to access a local file on a client and you do not have a Workgroup engine installed or if you try to access a local file on a server and the Server engine is not running.
If you have only a server engine installed and your Pervasive Event Log (PVSW.LOG) contains Status Code 3012 warning entries, perform the following steps:
To Turn Off Local Engine support (for clients and workstations only):
Access to the remote engine is not possible because the MicroKernel router could not initialize the networking component. Possible causes include:
The MicroKernel router could not complete the operation because it did not find an engine (local or remote) that could process the operation. Possible causes include:
An unexpected error occurred during the initialization of the MicroKernel router. Check the Pervasive Event Log (PVSW.LOG) for more information.
The MicroKernel router encountered an internal error. Check the Pervasive Event Log (PVSW.LOG) for more information.
The requester has more data to send the MicroKernel than the MicroKernel buffers can handle. This status code is only relevant to an engine running locally and does not apply to client/server environments. Some possible solutions include:
The MicroKernel router is shut down and is not accepting any more requests.
A semaphore error occurred while trying to establish contact with the local engine. Check the Pervasive Event Log (PVSW.LOG) for more information.
You receive this status code when an error occurs while loading the MicroKernel or when access to the server and client machine shared memory objects are unavailable. Check the Pervasive Event Log (PVSW.LOG) for more information.
The MicroKernel router rejected the response from the engine because it was badly formatted.Check the Pervasive Event Log (PVSW.LOG) for more information.
A request to the MicroKernel router specified a data buffer length that resulted in a data packet size greater than 64 KB, which is the maximum. This can occur even if the data buffer length for the request is smaller than 64 KB because the MicroKernel router adds some packet overhead as it forms the data packet. Check the Pervasive Event Log (PVSW.LOG) for more information.
An internal table used by the MicroKernel router to manage tasks is full. This error should only occur in Win16 environments and indicates that a large number of applications are using the Win16 MicroKernel router at the same time.
This code is returned if the path is remote, the client configuration setting for Use Local MicroKernel Engine has been set to Off, and either:
This code is returned if a Pervasive PSQL Linux requester attempts to connect to a Pervasive.SQL 2000 server that has Service Pack 2a or earlier, or a Pervasive.SQL V8 server without Service Pack 1.
|
Chapter contents
Prev topic: 2300 to 2399
|