Checking Your Pervasive Engine Installation
Last Updated: 11/20/2006

Our customers often ask us how they can confirm that their new database engine is working correctly. This question arises because the Pervasive database engine is designed to be an embedded engine, that is, it is designed to work behind the scenes and not be seen by the user. Since you can't see it, you may wonder if you are leveraging the benefits of the newer database engine.

Table of Contents:

Checking During Setup

Checking Via the Monitor Tool

Checking Via Function Executor

Checking During Setup

The first and easiest way to confirm that things are working is to run the Transactional and Relational tests during the client setup.

If you are installing a Workgroup Engine, this test will verify that the local client engine is working correctly. If the engine fails these tests, then the install did not succeed, and you may need to uninstall and try again. Be sure you are physically at the machine (no Remote Desktop) and that you are logged in as an Administrator.

If you are installing the Pervasive client, this test will verify that communications to the server is working correctly. You may need to alter the test parameters, depending on your install methods. The Transactional test should be connecting to the server's \PVSW\SAMPLES directory to run the test correctly. If your install does not default to this location, you may need to enter the correct pathname at the time of the test.

The Relational test should be testing the server's DEMODATA database. Again, be sure that the correct server's name shows up on this screen, or the test may fail.

When the tests complete successfully, you will get a series of checkmarks down the right side of the window.

Checking Via the Monitor Tool
The Pervasive Monitor tool is the next easiest way to confirm proper operation. On the database server, select Start/Programs/Pervasive/Utilities/Monitor and you will get the Monitor screen.

NetWare and Linux users must use the Monitor tool remotely by launching the app and selecting the Options/Connect menu item. (Windows users can do this from a workstation as well, but doing it from the server saves the extra login step.) You will be required to specify the server name and an Administrator username and password, but this will connect to the server.

From this window, select Microkernel/Active Users, and you should see a screen similar to the following:

The user showing up in the top-left quadrant indicates that this user is connecting to the database engine properly.

Now, simply launch your application on each workstation and verify that each user shows up on this screen. If you have users successfully launching the application, but they are NOT on this screen, then you may have old workstation-side components, such as Btrieve 6.15.

Checking via Function Executor
The Function Executor is one more way to validate access. To use this tool, select File/Open from the menu and try opening a file with this tool in the server's PVSW\DEMODATA directory.

When you click Open, you should get a dialog like this:

If not, then you will get an error message of some kind, as the following sample screen shows:

This error message, and specifically the numeric error code ,will tell us how to troubleshoot the problem Be sure to have this handy when you call for support, or check the “Status Codes & Messages” online help document for more information.

If you still can't get it to work, contact Goldstar Software and let us work with you to help!