Engine and Client Version Conflicts

---

If you update your engine to the latest Pervasive.SQL version without also updating your client requesters, you will encounter warning messages from Pervasive.SQL indicating the version conflict. The message displayed is:

An engine to client component mismatch was found 

When you receive such a message, it is also logged to your Pervasive Event Log (PVSW.LOG).

This message is only a warning. The client is not prevented from connecting to the engine in this situation. It simply recommends that you upgrade your clients as soon as it is feasible in order to obtain the best performance and reliability from your Pervasive.SQL database product.

If circumstances in your organization dictate that you cannot upgrade the clients for some time, you may want to disable the dialogs that appear when your client components are activated. However, you cannot disable the entries in the Pervasive Event Log, and you should note that over time this log could grow to a large size as these entries are logged.

To permanently solve the problem, update your client requesters to the same version as your server engine.

Disabling the Client Mismatch Warning Messages

   To disable the client component mismatch error

1. On the client with the older version of Pervasive.SQL, go to the Registry Editor (from the Start menu, select Run and type Regedit).
2. Go to the HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Microkernel Router\Version 7\Settings directory within the Registry Editor.
3. The MicroKernel Router settings will appear in the right hand frame of the Registry Editor. Add a new string value Engine Version Check and give it a value of No.

---

Caution
Use care when editing the Windows registry.

---