July 2011

New License Administration Features in PSQL v11 SP1

Pervasive PSQL v11 SP1 has some new license administration features that will do a lot to help PSQL users avoid licensing problems and keep their PSQL databases running. Here's a summary of the key improvements:

  • The number of product key authorizations has doubled to 10.
  • A Remaining Authorizations counter has been added to the PSQL v11 License Administrator.
  • A Failed Validation product key state has been added.
  • The new Pervasive Notification Viewer will notify users of any changes in PSQL product key state.

Product Key Authorizations/Remaining Authorizations Counter

Starting with PSQL v11 SP1 the number of allowed product key authorizations has increased to 10 (up from 5). Once the 10 authorization limit has been reached, Pervasive Support must be contacted to enable additional authorizations. To help you keep track, we have added a Remaining Authorizations counter to the PSQL License Administrator. The number of remaining authorizations is now available via the counter, and each time you authorize or deauthorize a key a pop-up message will let you know the number of authorizations remaining.

PSQL v11 Product Key States

Prior to PSQL v11 SP1, changing anything but memory on a virtual machine would disable the PSQL product key. The same thing would happen on a physical machine if more than two of the six items that made up the machine ID were changed. (For more background on the product authorization process and how changing hardware can disable a product key, read the Product Authorization Whitepaper.)

Now, instead of automatically disabling the key because of a change in machine ID, PSQL v11 SP1 does two really helpful things: a) it puts the key in a "Failed Validation" state and b) it delivers a notification about the new key state. The important thing is that PSQL keeps running and you have time to fix the issue.

Pervasive PSQL v11SP1 now has three product key states:
  • Active - Key is registered and live in the licensing database. No issue.
  • Failed Validation - Key has a potential problem - usually related to changes to the VM or physical machine. Once the key is in the Failed Validation state, it enters a 14 day time interval where it PSQL will continue to operate. If the issue is not resolved or the key is not repaired during the 14 days, the key will be Disabled.
  • Disabled - The product key cannot be deleted or deauthorized and the database cannot access any files.
Validation Check and Intelligent 14 Day "Grace Period"

Product keys are validated during the initial authorization process and periodically thereafter. During the validation process, the PSQL engine checks to make sure that the machine ID has not changed. If the validation process discovers that the machine ID has changed the key state changes to Failed Validation and a 14 day time period begins.

The good news about the 14 day period is that it has been intelligently engineered to not end on a weekend, so that if the problem isn't resolved in the 14 days the product key will be disabled on a day when you can call Pervasive Support for help.

Notification Viewer

The Pervasive Notification Viewer is a Windows and Linux tray application that creates a notice whenever the product key state changes. Notices are repeated daily until the issue is resolved. The Notification Viewer also provides information about the reason for the validation failure and steps to take to resolve the issue.

Notification Viewer Normal                     Notification Viewer Alert

Notification Viewer Details

How to Resolve a Failed Validation Key State

There are two ways to return a key to the Active State once the validation check fails. The first option is to return the machine to its original state (before the validation check failed), deauthorize the key, make the hardware changes and reauthorize the key. The second option is to contact Pervasive Support (or, if you got your copy of PSQL from a Pervasive OEM, contact the OEM) and ask to have the key repaired. Repairing the key puts it into a state where it can be deauthorized and reauthorized on the machine. In both cases it is a good idea to authenticate the key validation manually using the Validate button on the PSQL License Administrator.