Diagnosing Load Errors

Pervasive.SQL provides the following types of information you can use in diagnosing module load errors:

Status codes. You can refer to the Status Codes and Messages manual for more information about the specific status code returned.

Event log. You can look for the following information in the Pervasive.SQL Event Log to get additional information about a specific module load error:


Component Name	The logical or physical name of the module that received the load failure. Logical names used are: ServicesIfc-Abstract OS Services BtrvIfc-Btrieve MKDEIfc-MicroKernel PSQLIfc-Pervasive.SQL The physical name is logged if the calling module attempted to load a component using a binding rule. For example, a physical name is W3BIF102.
Type	The type of load error, as follows: E (Error)-The module could not be found or an operating system-specific error occurred while loading the module. W (Warning)-A symbol could not be found or was not exported by the module.
Message	The message depends on the type of module load error. If the module could not be found, the event log contains the binding rule that specified the downstream component. If an operating system-specific error occurred, the event log contains that operating system error. If a symbol could not be found or was not exported, the event log contains that symbol.

On-screen errors. The event log is not functional until the Services DLL loads. Therefore, if a load error occurs while binding to the Services DLL, the event log does not log the error. Instead, Pervasive.SQL can display an on-screen error.

You must enable the Services DLL to display on-screen module load errors by setting the PVSW_DISP_LOAD_ERRS environment variable. Its format is as follows:

PVSW_DISP_LOAD_ERRS=AIF

This environment variable should only be set to diagnose module load errors. In all other cases, it should not be set.

To diagnose an error, set this variable as specified and perform the operation. The load error is displayed in a message box on your system.