Skip to content

Pervasive.SQL Database Level Errors (21000 ..)

The Pervasive error handling mechanism uses error numbers similar to the DataFlex error handling mechanism. To avoid error number conflicts, the DataFlex Pervasive.SQL Driver adds 21000 to the Pervasive.SQL error number. If you encounter an error with a number above 21000, subtract 21000 to obtain the original Pervasive.SQL error number. Refer to the Pervasive.SQL documentation for a description of the error.

For example, if you receive error 21020: “The MicroKernel or Btrieve Requester is inactive,” subtract 21000 to get the Pervasive.SQL error number (20). In the Pervasive.SQL documentation, you will find the following text (from the Pervasive.SQL 8.5 documentation):

20: The MicroKernel or Btrieve Requester is Inactive

Note

For an expanded list of possible recovery solutions, consult the Pervasive.SQL Knowledge Base at http://support.pervasive.com/eSupport.

If you are running an application in a client/server environment:

  • Make sure the Btrieve requester is loaded.
  • Verify that the IPX/SPX or TCP/IP protocol is properly installed on the client machine and that no two machines on the network have the same Internal Network Number.
  • Ensure that at least one of the client configuration options, Access → Use Local MicroKernel Engine or Access → Use Remote MicroKernel Engine, is enabled. If your environment includes both a server engine and Workgroup engines, you should have both settings enabled.

If you are running an application in a workstation/workgroup environment, ensure that the MicroKernel is loaded.

If you are running an application in a client/server environment and also need to access files located on a local drive:

  • Make sure the Btrieve Requester is loaded.
  • Ensure both of the client configuration options, Access → Use Local MicroKernel Engine or Access → Use Remote MicroKernel Engine, are enabled.
  • Make sure a local MicroKernel is available and loaded.

If you are operating in a NetWare environment:

  • Ensure that the MicroKernel and (if applicable) the Btrieve Requester are loaded before generating any requests.
  • Verify that the appropriate communication modules are loaded at the server.

If you are operating in a Windows Server environment:

  • Ensure that the MicroKernel is started before generating any requests.
  • Verify that the Windows DLLs are in your path.
  • Ensure that the appropriate communications modules are loaded at the server.

See Also

Pervasive.SQL