Troubleshooting Common Pervasive PSQL Issues

This section outlines problems you may encounter during the installation or when first using the Workgroup product.

I fail to see the effects of my configuration changes.

Try stopping and then restarting the database engine. Whenever you make a change to engine configuration components, you must stop and restart the database engine for the changes to take effect. For information on how to start and stop the database engine, see Verifying Database Engine is Running .

Why do I (now) receive Status 95, after running my application successfully?

Your application has lost its session with the database engine. This can happen if you make changes to your configuration settings and must restart the database engine, as in the troubleshooting example given above. At the moment the database engine is stopped, any application that is running loses its session with the database engine. You must stop all those utilities and restart them in order to reestablish communication.

See the Status Codes and Messages manual for more cases in which this status code can be returned.

Installing a Pervasive PSQL application has rendered another application unusable.

If the latest DLLs have been overwritten, it is possible to restore the overwritten DLLs using a backup directory that is automatically created when you install Pervasive PSQL v9 Service Pack 2.

Pervasive PSQL uses a system called Smart Components to avoid component mismatches and the occurrence of an older program overwriting newer components. To provide an interface for legacy applications, however, some component names are still capable of being overwritten.

How do I verify that my DOS components are functioning properly?

Pervasive provides a DOS version of BUTIL.EXE in C:\PVSW\BIN\DOS for purposes of verifying that your DOS components are functioning properly.

To verify using the DOS version of BUTIL:

Enter the following at a DOS prompt:

cd \pvsw\bin\dos 
butil -stat ..\..\samples\sample.btr

In addition, use of the BDOSSTUB.EXE is needed for some applications using Windows 95 DOS Box for Btrieve if you encounter a Status 20, indicating the requester is not loaded. Some applications built with Turbo Pascal have this problem, which can be avoided by loading the BDOSSTUB.EXE TSR before starting the DOS application.

Why can't I restart my application after an improper program exit?

Database engine components may remain in memory if the engine is interrupted improperly.

If you cannot restart your program after improperly aborting the application by using Ctrl-C or stopping the process:

Shut down and restart your system.

Avoid terminating applications in an abnormal manner.

Why isn't my application using the Workgroup engine?

If you previously installed Pervasive PSQL requesters and later installed the Pervasive PSQL v9 Service Pack 2 Workgroup engine but your application is only using the requesters, you may have an outdated configuration that sets Local Access to Off. The Pervasive PSQL v9 Service Pack 2 Workgroup engine's installation does not overwrite existing settings. To reset Local Access to On, see Using a Workgroup Engine to Access Local Files and a Remote Server Engine to Access Remote files .

I have previously installed requesters and then Pervasive PSQL v9 Service Pack 2. How do I resolve a Status 3012 returned while running a 16-bit application?

A 16-bit Pervasive PSQL application that functions properly going to a remote server will require an adjustment when running against the Workstation engine. The Pervasive PSQL Workgroup engine requires that 16-bit applications use the ODBC thunk mechanism.

Thunking with the Microsoft-provided ODBC thunk DLLs is required for remote Pervasive PSQL engine access from a Win16 ODBC application running on a Win32 workstation.

You may also receive a Status 802 from the Workgroup engine in this scenario.

Status Code 3012 (Local engine is not accessible to the MicroKernel router) can be corrected by examining your Thunk settings.

How Do I Access the Pervasive PSQL v9 Service Pack 2 Online Manuals?

If you wish to read the online documentation:

Access the Pervasive 4Documentation commands on the Start menu and click Pervasive PSQL v9 Service Pack 2.

Click on the desired manual under the Contents tab or search for a topic.

I received an error message during installation that begins: "Setup did not update the PATH statement in autoexec.bat because the new path would be too long for Windows."

This message appears when the installation program cannot update the PATH environment variable because the resulting PATH definition would be too long (exceeds the environment space). For info on how to increase the environment space defined in config.sys, see the Microsoft knowledge base article:

http://support.microsoft.com/?kbid=230205

If you get this error message, then a REM statement (a comment) has been added to your autoexec.bat file. The REM statement contains the PATH value that would have been entered. You can change the PATH statement manually.

The best approach, if possible, is to install the product at a location with a shorter installation directory so that the value of PATH does not exceed the environment space.