License Problems with Pervasive PSQL, Actian PSQL, or Actian Zen

Pervasive Software (now Actian Corporation) switched to an "activation" licensing model for PSQL Summit v10, and they have continued with the same model for newer versions. This "activation" model provides a software "activation key", also known as an "authorization key", with your purchase. This key is applied to the database engine on the server, which then contacts Actian's web-based licensing servers, ensures that the key is valid and has not yet been used, submits the server's hardware signature, and then authorizes the engine to run with a specific license on that server hardware.

For the most part, this process is simple and easy. However, experience has shown that there are several ways in which this process can break down:

• If a server is wiped out for any reason without the license being deactivated first, the license will be unusable. This can arise due to a hardware failure, virus attack, or just forgetting to remove the license before wiping out a test server.
• If the server hardware changes for some reason, the hardware signature can change, making the license switch to "Disabled" or (on PSQL v11) "Failed Validation" for up to two weeks before changing to "Disabled". This can occur when a hardware device (NIC, mainboard, memory module) fails or is replaced on v11 or older. For PSQL v12 and newer, this will only occur when the server name is changed.
• If the user forgets to enter in a permanent license after purchasing it, the 30-day trial license that is applied automatically during the installation can expire and prevent access to the engine.
• If the site exceeds the capacity of the license, either with a pure machine count (PSQL Server) or the data size in use or session count in use (PSQL Vx Server).

Most of these problems will result in a Btrieve Status 161 being returned to the application, which is simply a generic "License Exceeded" message. Troubleshooting this status code can sometimes be difficult, especially if you are unfamiliar with the PSQL tools and utilities. This page should provide everything you need to fix your license problems!

If you need help from Actian Corporation to address a licensing issue, here is their contact information:

• Phone: 800-BTRIEVE
• EMail: dbcic@actian.com
• International Contact Info: Actian's Web Site Contact Page

Verify Your Installed PSQL Version

The first task is to make sure you know which version of PSQL is installed. Go into the Control Panel Programs applet (or Add/Remove Programs, for older systems) and verify the exact engine installed. Note the database engine Version (v10, v11, etc.), the type of engine (Workgroup Engine or Server Engine) and bit level (32-bit or 64-bit).

Verify Your Installed License Key

Once you have the above information, verify your license key. Start the PSQL License Administrator on the server and look at the licenses listed on the bottom half of the window. (If you do not have server access, you can also do this from a workstation by entering the server name into the box provided and clicking "connect".) You should see an "Active" license indicating the same version, engine type, and platform. (Note that newer licenses will indicate "Any" for the platform. This means that your license will work on any bit level.)

If you do not see the license data on this screen, then it is possible that your license key was never installed. Apply the license. If needed, you can find more explicit directions in our white paper on applying a license key. Of course, if you have not yet purchased your license, you should do so now.

If you see a license for a different version, engine type, or platform, then it may be possible that the wrong software was installed. For example, if your license is for a Workgroup Engine and a Server Engine was installed, the system will not function after the 30-day trial. The solution is to remove the wrong software and reinstall the right one, then apply your license key. If needed, you can download the correct engine from Actian's web site. Be sure to check your license and download the software that you have purchased.

Fixing a DISABLED or FAILED VALIDATION License

If you see a DISABLED license (or FAILED VALIDATION), then your hardware or server name has likely changed and your key was invalidated because of it. The simplest solution is to change your hardware back to the original configuration, deactivate your license from the PSQL License Administrator, then change your hardware as needed, and re-apply your license key afterwards.

If you are unable to do this, then you will need to contact Actian Corporation via phone at 800-BTRIEVE or via Email at dbcic@actian.com. Be sure to have all of your critical information (version, product serial number, license key, etc.) available when you call, or provide all of the important details in your Email for fastest response. Better yet, click on the big red button to the left titled "Fix My PSQL License" and it'll take you right to Actian's web site, with a list of everything that they would ask you for.

Numeric Status Codes Returned from the License Administrator

The License Administrator can return a number of numeric status or error codes. Here's a quick list of the most common ones and how to fix them:

• 7101 or 7113: You probably have a typo. Verify the license key and pay attention to confusing characters like "0" versus "O". This could also indicate that you are trying to install a 32-bit license on a 64-bit server engine, or vice versa. Verify the license key and platform information one more time.
• 7115: Usually returned when you try to install a newer license (like v11) onto an older engine (v10) that doesn't recognize the license type. Check your engine and license version one more time.
• 7118 or 7119: Often returned when trying to install a license on a workstation with the PSQL Client installed. Apply your license from the server if possible. If you must do it from a workstation, then you will need to enter the server name and click "Connect" before entering the license key.
• 7125: Each server can have only ONE base license. This message indicates that you are trying to apply a second base license. You must purchase and install a User Count Increase license to add users to an existing server.
• 7132: PSQL licenses are valid for the engine purchased only. If you are getting this error, check to make sure that you have installed the correct software. For example, if your license is for PSQL Server, make sure that the software installed was not Vx Server or Workgroup.
• 7213: While the text of this message is confusing, the solution is pretty simple: You probably have a typo. Verify the license key and pay attention to confusing characters like "0" versus "O". This could also indicate that you are trying to install a newer license onto an older engine. Verify the license key and platform information one more time.
• 7218: This error indicates a problem with the Windows Management Interface (WMI). From a command prompt, try running "WMIC", then enter "CPU" at the prompt and verify that you get a valid result. If not, you may have to rebuild the WMI environment.
• 7224: This error code indicates that you have Insufficient rights to apply your code, which usually happens on Windows 7 or newer systems. Open our white paper on applying licenses and scroll to the last two pages for the steps needed to fix this, or watch the following video.
  

• 7315 or 7334: To get around the Status 7315 or 7334 issue the clear command from the command line License Administrator. For 32-bit systems, the command is "clilcadm -c <licensestring>", and for 64-bit servers, use " w64clilcadm -c <licensestring>".
• Others: If you have any other errors, contact Actian for more help!

Status 161 with a Valid License Installed (on all EXCEPT PSQL Vx)

If you are getting a Status 161 when you have a valid license installed, then you are most likely exceeding the number of allowable connected workstations. To confirm this, start the PSQL Monitor tool, select the Microkernel/Resource Usage menu item, and look at the Licenses line in the resulting dialog. Verify that the "Maximum" value matches the expected license count. (A mismatch could indicate a version problem.) Then, verify that the "Peak" is hitting the "Maximum" value. If so, then you have these options:

• Ask idle users to log off of the database application to free up licenses.
• Reboot any workstations that may have terminated the database application abnormally.
• Purchase additional licenses in the form of a User Count Increase and apply the license to the server.

If you see a number of licenses that you cannot believe, then you can check into this further by going into the Microkernel/Active Users (or Active Sessions) screen. Click on the first user in the upper-left corner of the window, and write down the Network Address data found in the lower left quadrant. Press the down arrow to go to the next user session, and repeat this process for each database connection. If an address appears as a complete duplicate, you can skip it, because it has already been counted. You should get a number of unique network addresses that matches your current license count.

If you do find a "dead" connection that is taking a license but should not be, you can also use the "Delete User" button to clear it out and free up a license. Note that if you do this to a user actively using the system, that user may lose data.

Status 161 with a Valid License Installed (on PSQL Vx)

If you are getting a Status 161 when you have a valid license installed on PSQL Vx Server, then you may be exceeding the allowable data in use limit or the allowable session count limit. To confirm this, start the PSQL Monitor tool, select the Microkernel/Resource Usage menu item, and look at the Session Count line in the resulting dialog, as well as the Data In Use MB line. Verify that the "Maximum" value matches the expected license count. (A mismatch could indicate a version problem.) Then, verify that the "Peak" is hitting the "Maximum" value. If so, then you have these options:

• Ask idle users to log off of the database application to free up licenses.
• Reboot any workstations that may have terminated the database application abnormally.
• Delete idle user sessions from the PSQL Monitor tool (as explained above).
• Get all users out of the database and rebuild files (with the Rebuild Utility) to reclaim deleted record space, compact the index structrues, and make them physically smaller .
• Purchase additional licenses in the form of a Session Count Increase or Data In Use Increase and apply the license to the server. (Note that temporary forms of these licenses are also available, at a reduced cost.)

If you find any other common errors, please let us know, and we can add it here!