|
If you update your engine to the latest Pervasive PSQL version without also updating your client requesters, you may encounter warning messages from Pervasive PSQL indicating the version conflict. The message displayed is:
When you receive such a message, it is also logged to your Pervasive Event Log (PVSW.LOG).
This message is a warning. The client is not prevented from connecting to the engine in this situation. Note, however, that Pervasive recommends that you use client requesters that are the same version as the database engine. If you choose, you may use a client requester that is an older version than the database engine with which it interacts. In some situations, depending on the type of SDK access method used by your application, an older version requester will not work with the database engine. Your application will be unable to communicate with the database engine. For those situations, you must use client requesters that are the same version as the database engine.
Client requesters that are a newer version than the database engine may or may not function correctly. Pervasive does not guarantee that newer versions of client requesters will function correctly with older versions of the engine. Therefore, Pervasive recommends that you avoid the use of newer version client requesters with an older engine.
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.
To disable the client component mismatch error
Regedit). HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Microkernel Router\Version 7\Settings directory within the Registry Editor. Engine Version Check and give it a value of No.
Caution
Use care when editing the Windows registry.
|
Chapter contents
Prev topic: Issues After Uninstalling Pervasive PSQL on Windows
|