 | Status Codes and Messages (v9 SP2 (9.5) revision 1) |  |
|
This section describes the status codes returned by the ECAS (Enhanced Common Address Space) interface. Most of the errors are system errors and cause an entry in the Pervasive event log. In many cases when you receive these errors, there may be some instability in the environment or memory allocation and you will need to restart the machine.
In its attempt to auto-load the Workgroup engine, the application failed to initialize the smart component library. You may get more information about the situation that caused this error by setting the environment variable PVSW_DISP_LOAD_ERRS=AIF, and running the application again. This setting enables the Services DLL to display on-screen module load errors. However, this environment variable should only be set to diagnose module load errors. In all other cases, it should not be set.
In its attempt to auto-load the Workgroup engine, the application failed to locate or load W3UPIXYY.DLL.
In its attempt to auto-load the Workgroup engine, the application discovered an incorrect version of W3UPIXYY.DLL. This problem may have been caused by a corrupt version of W3UPIXYY.DLL.
In its attempt to auto-load the Workgroup engine, the application failed to create the system semaphore. This problem may have been caused by the operating system running out of resources.
In its attempt to auto-load the Workgroup engine, the application failed to establish the session with the Workgroup engine. This is a system error.
Some customers who have only Server engines in their environment have reported frequent pairs of Status Code 8505 and 8517 in the PVSW.LOG file on one or more client workstations. The most likely cause is that your workstation client is configured to connect to a local Workgroup engine when one is not installed.
Note
If you are not certain whether your environment includes Workgroup engines, please check with your administrator. The procedure below disables access to your local Workgroup engine.
To prevent the client from attempting this connection, follow these steps:
In its attempt to auto-load the Workgroup engine, the application failed to load the MicroKernel, W3MKDE.DLL. This may have been caused by a missing W3MKDE.DLL.
The application lost its session with the Workgroup engine.
The application failed to enable the Btrieve access method in the Workgroup engine.
The application timed out during the initialization of the MicroKernel. This may have been caused by a bad configuration option or a malfunction of the Workgroup engine.
Check the Pervasive Event Log (PVSW.log) for more information.
This status code is obsolete in Pervasive.SQL 2000 and later versions.
In its attempt to auto-load the Workgroup engine, the application failed to load the Scalable SQL, W3SSQL.DLL. This may have been caused by a missing W3SSQL.DLL.
The application failed to enable the SQL access method in the Workgroup engine.
This status code is obsolete in Pervasive.SQL 2000 and later versions.
The application timed out during the initialization of the Scalable SQL engine. This may have been caused by an invalid configuration option or a malfunction of the Workgroup engine.
The application failed to disable the Btrieve access method in the Workgroup engine.
The application failed to unload the MicroKernel.
The application failed to disable the SQL access method.
This status code is obsolete in Pervasive.SQL 2000 and later versions.
The application failed to unload Scalable SQL.
The application could not close the session with the Workgroup engine.
Some customers who have only Server engines in their environment have reported frequent pairs of Status Code 8505 and 8517 in the PVSW.LOG file on one or more client workstations. The most likely cause is that your workstation client is configured to connect to a local Workgroup engine when one is not installed.
If you are not certain whether your environment includes Workgroup engines, please check with your administrator. The procedure below disables access to your local Workgroup engine.
To prevent the client from attempting this connection, follow these steps:
The application failed to allocate memory from the system. Possible ways to avoid this include closing all other applications and restarting the engine, decreasing the size of the cache, and changing the engine settings so that a smaller number of files and/or file handles are open.
In its attempt to auto-load the SQL Relational Database Engine (SRDE), the application failed to load the file, W3ODBCEI.DLL. This may have been caused by a missing W3ODBCEI.DLL.
8520: A timeout occurred during the initialization of the SRDE module
The application timed out during the initialization of the SQL relational database engine module. This may have been caused by a bad SRDE configuration option or a malfunction of the Workgroup engine.
8521: An error occurred when unloading the SRDE module
The application failed to unload the SRDE module.
|
Chapter contents
Prev topic: 8000 to 8499
|