7064 to 7140
License Administrator Status Codes
This section lists the status codes you can receive when using the License Administrator.
7064: No license obtained for the product
A session tried to release a license (for user count, session count, or data in use) but the session either had not acquired a license from the server or had acquired a license for a different product.
7065: A product has not been obtained
An application attempted to obtain the license (for user count, session count, or data in use) for a product, but no license has been authorized. Ensure that a license has been authorized for the product before attempting to obtain the license information.
7101: Invalid character in the license string
The license key you attempted to authorize contains one or more invalid characters. All alphanumeric characters (upper or lower case) are permitted except for “i” and “o.” Lower case letters are automatically converted to upper case.
Correct any invalid characters in the license key and authorize the key again.
7102: Illegal license type is defined
The license key an application attempted to authorize is not valid because the Product Type is invalid. The permissible types are permanent and temporary, and increase licenses for user count, session count, or data in use.
Ensure that you have a valid license key issued by Actian Corporation or by your application vendor if the PSQL database engine is embedded in an application.
7108: License key length is too long
The length of the license key you attempted to authorize exceeds the maximum length allowed for a key (30 characters). Ensure that the license key contains 30 characters.
7109: No such license exists
The license key you are trying to deauthorize does not exist. The license key may have already been deauthorized.
If you are using the License Administrator GUI to deauthorize the key, press F5 to redisplay the list of authorized licenses. Check the refreshed list for the license key you were trying to deauthorize. If the license key still appears to exist, exit, then restart License Administrator.
7110: Only temporary licenses are installed on the system and all of them have expired
All of the installed licenses are temporary ones that have expired. The values for user count, session count, or data in use no longer apply. You need to install a valid license, temporary or permanent, to provide new values for user count, session count, or data in use.
7111: Temporary licenses cannot be deauthorized. The license becomes invalid after its expiration date.
You have attempted to deauthorize a temporary license. Temporary licenses cannot be deauthorized; they become invalid after their expiration date. Verify that the license you want to deauthorize is a type that can be removed.
7112: License is already installed
The license key you are attempting to authorize has already been authorized . You cannot reauthorize a license once it has been authorized unless you deauthorize it first. Temporary licenses cannot be deauthorized.
If you are using the License Administrator GUI to authorize the license, press F5 to redisplay the list of licenses. Check the refreshed list for the license you were trying to authorize. If the license still does not appear in the list, exit, then restart License Administrator.
7113: Invalid license key. Verify the provided key
The license key you attempted to authorize is not a valid license. Ensure that you have a valid license key issued by Actian Corporation or by your application vendor if the PSQL database engine is embedded in an application.
This status code is also displayed if your key is for a specific platform that does not match the platform on which you are attempting to authorize the license. For example, if your license key is for “Win64,” you cannot authorize the license for a Windows 32-bit operating system or on a Linux platform.
If you are using the License Administrator GUI to authorize the key, repaste or retype the key in the Key field, then click the button to authorize the key.
Special consideration for telephone authorization
If your machine configuration changes between generating the authorization request code and the receipt of your authorization key data string from PSQL Support, then this status code can indicate that the authorization key data string no longer matches your machine, even though the product key itself is valid. In this case, you have two options:
Return your machine to its previous configuration, then attempt to authorize your license key again.
Or
Follow these steps:
1
Rerun the Phone Authorization Wizard or the Command-line Phone Authorization Utility.
2
Contact PSQL Support with your original product key and the resulting new authorization request code.
3
Obtain a new authorization key data string for your changed machine configuration.
4
Use the new authorization key data string with your license key.
7115: Invalid product ID
The license key you attempted to authorize is not a valid license because the name of the PSQL product in the key is not PSQL v12 Server or PSQL v12 Workgroup. Only these two product IDs are supported at this time.
Ensure that you have a valid license key issued by Actian Corporation or by your application vendor if the PSQL database engine is embedded in an application.
7116: Buffer overflow
The buffer assigned for the DTI function or DTO method is too small. Increase the size of the buffer. Refer to the applicable function Distributed Tuning Interface Guide or to the applicable method in Distributed Tuning Objects Guide.
7117: License key is too long
The length of the license key you attempted to authorize exceeds the maximum length allowed for a key (30 characters). Ensure that the license key contains 30 characters.
7118: The server is not running. Unable to show, authorize, or deauthorize a license. Verify that the server is running and that network communications are functioning.
License Administrator is unable to connect to the remote server. This could indicate the following:
•
You may have started the License Administrator on a client where a database engine is not installed. Click OK to establish a connection to a server.
•
The server is not running. Follow the steps in Verifying Database Engine is Running in Getting Started With PSQL to ensure the server is running.
•
Network communications are preventing connection to the server. Use the ping command to the server to verify that network communications are working.
7119: The local server is not running. Unable to show, authorize, or deauthorize a license.
License Administrator is unable to connect to the database engine on the local machine (the machine on which License Administrator is running). Ensure that a database engine is installed and running on the local machine. Follow the steps in Verifying Database Engine is Running in Getting Started With PSQL to ensure the database engine is running.
7120: The license cannot be deauthorized
The license or licenses you are attempting to deauthorize cannot be deauthorized. Temporary licenses cannot be deauthorized; they become invalid after their expiration date.
Verify that the license you want to deauthorize is a type that can be deauthorized.
7122: Your trial license has expired
The temporary, trial, license you are attempting to authorize has expired, and one of the following is true:
•
no other licenses are authorized
•
other licenses are authorized but are no longer valid. (All installed temporary licenses, for example, have expired.)
The PSQL product cannot be installed without a valid license. Click Continue if you have a valid license to authorize. If you need an additional trial period, you can request a new trial license from Actian Corporation.
7124: An increase key for user count, session count, or data in use must have a vendor ID that matches the vendor ID of an authorized permanent key
An authorized permanent key is required before an increase key can be authorized. The software vendor ID number for an increase key must match the vendor ID number for an authorized permanent key. Increase keys obtained from Actian Corporation are universal. That is, they are compatible with any permanent key from any vendor.
Ensure that you have a valid permanent key authorized before authorizing an increase key. Also ensure that the vendor ID numbers match if the increase key was obtained from a vendor, or use an increase key obtained from Actian Corporation. Vendor ID numbers can be verified with the License Administrator utilities. See License Administration in PSQL User's Guide.
7125: An active permanent license already exists
The machine on which you are attempting to authorize a permanent license key already contains a permanent license key from the same vendor in the “active” state. You may not authorize more than one active permanent license key from the same vendor.
If a permanent license key has already been authorized from a vendor and is active, you may only authorize an increase for user count, session count, or data in use. Deauthorize the existing license key and then authorize the new permanent license key.
You may authorize another permanent key from the same vendor to the same machine if the existing permanent key is in a “failed validation” or a “disabled” state. That is, the existing permanent key is not active. If another permanent key is authorized while an existing key is in the “failed validation” state, the existing key changes state to “disabled.” The other permanent key then becomes the active key.
7126: Cannot increase the value beyond the maximum limit for user count, session count, or data in use
The license increase you are attempting to authorize would increase the value beyond the maximum limit for user count, session count, or data in use. You cannot increase the value beyond the maximum limit allowed by your license agreement.
7127: This key or a related key requires deauthorization. This version of the client cannot deauthorize a key.
The key or a related key you are trying to deauthorize requires that you have PSQL v10.13 or later installed. Upgrade to PSQL v10.13 or later and use the License Administrator utility to deauthorize the key.
7130: The PSQL product version for this key does not match the installed PSQL engine
The PSQL product version associated with the key you are trying to authorize does not match the PSQL product currently installed.
Make sure that the key you are using is correct and that you have the correct PSQL product installed.
7131: The OS platform for this key does not match the installed PSQL engine
The operating system associated with the key you are trying to authorize does not match the PSQL product currently installed.
Make sure that the key you are using is correct and that you have the correct PSQL product installed.
7132: The PSQL engine type for this key does not match the installed PSQL engine
The engine type (Server or Workgroup) associated with the key you are trying to authorize does not match the PSQL engine currently installed.
Make sure that the key you are using is correct and that you have the correct PSQL product installed.
7133: An associated UCI key is preventing the deauthorization of the permanent key. The UCI key may already be in the failed or disabled state, or it may be set to transition into the failed state the next time it is validated. Repair the UCI key and try again to deauthorize the permanent key.
An authorized permanent key cannot be deauthorized because of its associated user count increase key. The user count increase key is in a Failed Validation or Disabled state or will move into a Failed Validation state during the next validation.
First, determine why there is a problem with the UCI key. Fix the problem and validate the UCI key. After that, reattempt the deauthorization of the authorized permanent key.