Btrieve Error 161 on Password File When Starting Up Elliott

Q - We are receiving an Error 161: The maximum number of user count licenses has been reached.

This happens to all users when starting up Elliott.  We have rebooted all office computers and the PSQL server. There is no one is in Elliott. Yet we are still getting this error (we tried opening Elliott on only one computer). Everything was working fine yesterday.

A - The likely scenario to cause this to happen is that your PSQL license has become disabled or expired.  You should go to your PSQL server console and bring up the Pervasive License Administrator utility. See attached example below.

Check the PSQL license entry to see if it has been "disabled" or "expired."  

PSQL 11 License Is Disabled
The PSQL server license can become disabled because the underlying hardware has been changed.  For example, if you upgraded your PSQL server to a new hardware box by using backup and restore, the PSQL server noticed that the underlying hardware changed. At that point, its copy protection mechanism will disable the PSQL license until you resolve this issue.

If your old server is still up and running, you can go to your old server to "de-authorize."  Then you can re-authorize on the new server.  If your old server is no longer available, you can try to repair the PSQL license key. See the following KB article for details:
If you can't repair the PSQL license key yourself, then you will have to contact Netcellent.  

Keep in mind that if your PSQL is installed on a virtual server, it is likely to exacerbate this problem.  In the virtual environment, it is very easy to change memory size and allocate more CPU units to the virtual server.  This can potentially disable your PSQL license.  Also, in the virtual server environment, you can perform live migration, which is to move your PSQL virtual server from one hardware box to another.  This will also disable your legacy PSQL license unless you have a special PSQL Vx license installed.

PSQL 11 License Is Expired
When upgrading to a new server, many of our users simply install PSQL on the new server without installing the license key.  PSQL comes with a 30-day free trial.  So you may not even know you are running on a trial license until the license expires 30 days later. If that is the case, you will simply transfer your PSQL license from the old server to the new server by using the license administrator utility.

Running Out of PSQL User Licenses
It is also possible you ran out of PSQL user licenses.  But if that's the case, you should not receive Error 161 for every single user after you reboot the PSQL server and there's no one else in the system.

If you indeed exceed your PSQL user licenses, you simply have to give us a call to purchase more PSQL user licenses.

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