What to Do When PSQL 11 License Is Disabled
Release Date: 06/12/2018
Q - I recently migrated my workstation from one virtual server host to another for load balancing reasons. After the migration, the PSQL 11 Workgroup engine on the machine became disabled. When I started up Elliott, I received the following message:
Btrieve Error 161 on Password File
How do I fix this?
A - What happened was that the PSQL 11 license model validated the motherboard, CPU, hard drive, NiC card and size of your memory. When one of those is changed, it assumes that the same PSQL license is now installed on two different physical machines and thus disabled the license. This is not very friendly to a virtual server environment where the server or workstation can be moved around for load balancing purposes.
To avoid your PSQL 11 license becoming disabled, you should de-authorize the PSQL 11 license key before the migration. Then re-authorize it after the migration.
The question is what to do now that the migration already took place and the license is disabled. You can use the following steps to re-activate your PSQL 11 license:
(1) Start up PSQL Control Center.
(2) From the menu, choose "Tools" -> "License Administrator."
(3) In License Administrator, highlight the license key that has been disabled. Choose Repair.
(4) If the Repair is successful, you should receive the following message:
The product has successfully been repaired.
Pervasive PSQL has been authorized with the current machine
configuration. Future changes to the machine configuration could
disable your key(s). As a precaution, your should deauthorize the
key before your make machine configuration changes and
reauthroize the key after the changes have been made.
You have ? remaining repairs available for this product key.
See sample screen below:
See also the following KB article on this subject:
PSQL 12 and up has a better license model where it only matches on the NETBIOS name of the server. As long as the machine name is not changed, it will not break the license and thus make it friendly for the virtual server environment.
If you need additional help, please contact Netcellent for further assistance.
EMK
Related Articles
Does Elliott Deferred Processing Take up License?
Release Date: 01/30/2025 Version: 7.x & Up Q - We are running on Azure Virtual Desktop. It looks like the deferred processing takes one of the licenses. Was the policy changed? A - Deferred processing will take one PSQL (Actian) license. But on the ...A Case to Optimize PSQL Query Performance with INNER JOIN SYCONTCT & SYCONREL Tables
Release Date: 11/29/2023 Version: 7.x & Up Q - With our custom web application, we attempt to find an existing customer and associated contact when creating new customers via the Elliott web services. We are finding the customer just fine, but when I ...A Case Where PSQL 13 Client Is Not Compatible with PSQL 15 Server
Release Date: 02/04/2025 Version: 8.6 Do Users Need to Upgrade to PSQL 15 Client When Upgrading PSQL Server? We were often asked in the past if our users should upgrade their PSQL 13 client when they upgrade to the PSQL 15 server. In our past ...An Example of Debugging NOTE_ORD_VIEW PSQL Expression Evaluation Error
Q - When I try to access the NOTE_ORD_VIEW in the PSQL control center, I get this error: "[LNA][Pervasive][ODBC Engine Interface]Expression evaluation error." See sample screen below. It does not display any results, but it does display the create ...How to Update Elliott 8.5 License Key Code
Release Date: 11/13/2019 Last Updated: 3/7/2022 Version: 8.5 & Up Q - I received an Elliott 8.5 license key code. How do I apply this new license key code to my Elliott 8.5? A - The following instructions apply to Elliott 8.5, 8.6, and all future ...