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.


Pervasive PSQL

  1. Btrieve Error Codes 001 - 199
  2. Btrieve Error Codes 3000 - 3099
  3. Btrieve Error Codes 3100 - 3199
  4. PSQL Version Required by Each Elliott Version
  5. Do I Need to Change PSQL Server Engine Default Parameters After Installing It?
  6. New Elliott PSQL Server Processor and RAM Suggestions
  7. Can I Dynamically Adjust Elliott / PSQL 11 Server Memory?
  8. Received "Your Computer Does Not Have PSQL 10 or 11 Client " Even though PSQL Client Is Just Installed
  9. Btrieve Error 161 on Password File When Starting Up Elliott
  10. Problems with Using Pervasive Rebuild Utility on APOPNFIL and AROPNFIL Tables
  11. Security Issue with Installing PSQL Client Remotely on User's Workstation
  12. PSQL and Distributed File System (DFS)
  13. How Do I Turn on PSQL Relational Engine Security?
  14. An Example of Debugging NOTE_ORD_VIEW PSQL Expression Evaluation Error
  15. Btrieve Error 025 on COP Open Order by Salesman Report
  16. What Is the *.^01 File for My PSQL Btrieve Table?
  17. Suggested Files to be Monitored by Audit Master
  18. Pervasive Backup Agent Is Not Compatible with Creating Work Files
  19. Hardware Recommendations for Your PSQL Database Server
  20. How to Optimize SQL SELECT Statement When Retrieving Data from Invoice History
  21. New User-Defined Functions in Elliott DDF
  22. How to Improve Query Performance When Retrieving Data from Notes & Invoice History
  23. How to Retrieve Tracking Number for an Order from Notes
  24. Actian PSQL Not Started Automatically After Server Reboot
  25. Create a New Database in the PCC for Relational Engine Access
  26. Slow PSQL Relational Engine Performance
  27. IPV6 May Cause Problem for PSQL 11 Relational Query
  28. DDF Files in DATA Folder May Confuse PSQL
  29. What to Do When PSQL 11 License Is Disabled
  30. Quick Installation Guide for Audit Master
  31. Quick User Guide for Audit Master
  32. PSQL 13, Micrsoft SQL Integration Service & Pervasive PSQL OLE DB Provider
  33. Your Firewall Needs to Allow Outbound Traffic to the Netherlands for PSQL Licensing Server Purposes
  34. A Case of Btrieve Error 046 on ARCRCLOG A/R Credit Card Log File
  35. A Support Case of Migrating to Different Version of DDF
  36. How to Clear the Message "Unable to Read your Users record (9/068)"
  37. Setup of the PSQL 13 Report Engine
  38. How to Create CPHSTTRX_VIEW with Left Join to CPINVHDR Due to Invoice Database Archive
  39. How to Access Elliott's Data by Using Query in Microsoft Office Excel 2019
  40. Elliott Database Naming Convention
  41. What Does Btrieve Error 080 Mean?

Feedback and Knowledge Base