7200 to 7499
Authorization Status Codes
This section lists the status codes you can receive when authorizing your product.
7201: An error in one of the authorization libraries prevents further processing
One of the authorization libraries has produced an error that prevents further processing.
Try restarting the services or reinstalling PSQL and try authorization again. If this error persists, check the log file to determine the library name reported and contact PSQL Support.
7212: Invalid product key for authorization
The product key specified is invalid. Type, or paste, a valid product key and try to authorize the key again.
7213: Product key does not pass checksum validation for authorization
The product key appears to be a valid key, but failed to pass a checksum validation. A common reason is that the key was typed incorrectly. Another possibility is that a transmission error prevented the checksum validation.
Ensure that a valid product key is specified and try again to authorize the key.
7215: Unable to determine machine ID. Verify you are logged on with administrator permissions and retry.
The system encountered an error while trying to calculate the machine ID for the current session.
Ensure that you are logged on as an Administrator with full access rights and try authorizing or deauthorizing the key again. If you are using Windows Vista or subsequent Windows operating systems, turn off UAC. If you are authorizing or deauthorizing the key remotely, try the operation locally.
7218: Debug entry logged pertaining to acquiring the machine configuration
The system encountered difficulty while trying to acquire the machine configuration and has logged information to the PSQL logging repositories.
Ensure that you are logged on to the operating system as an Administrator with full access rights and try again to authorize or deauthorize the key. If you are using Windows Vista or later operating system, turn off UAC. If you are trying to authorize or deauthorize a key remotely, try the operation locally.
If you encounter this situation in a Windows operating system, ensure that WMI is working properly because it is the utility that acquires the machine configuration.
If you encounter this situation on a Linux operating system, ensure that the dmidecode utility is installed on the system and restart the PSQL daemon.
7221: Authorizing or deauthorizing a key requires database engine to be running
The PSQL database engine must be running before you can authorize or deauthorize a key. See Starting and Stopping the Database Engine in PSQL User's Guide for details on starting the engine.
7222: DTI call could not be completed or there is a problem connecting to the engine
The authorization call to DTI could not be completed or there is a problem connecting to the engine.
Try restarting the engine or services and try authorization again. If the problem persists, try reinstalling PSQL and try authorization again.
7223: DTI returned invalid license string
The string returned during authorization was empty or invalid.
Make certain that the PSQL is running and try authorization again.
7224: User lacks the appropriate rights to authorize or deauthorize a key
The target engine tests for appropriate permissions prior to authorizing or deauthorizing a key. Target engine testing failed due to inappropriate permissions.
Ensure that you are logged on as a user with Administrator permissions and try again to authorize or deauthorize the key. If you are using Windows Vista or subsequent Windows operating systems, temporarily turn off UAC.
If authorizing on Terminal Services, ensure that the setting for “Restrict Administrative Functions from a WTS Client” is off. In PCC, open the properties for the MicroKernel Router under Local Client. On the Properties dialog, ensure that the option “Restrict Administrative Functions from a WTS Client” is not selected.
This error can also be seen if you are running the PSQL Workgroup Engine as an application on Windows Vista or subsequent Windows operating systems and not running as an Administrator. Try closing the Workgroup Engine and then restarting w3dbsmgr.exe using the “Run as administrator” option. Another option is to uninstall the Workgroup Engine and reinstall it to run as a service.
7226: Deauthorizing a key requires an authorized key
Deauthorizing cannot occur because no key is available. A product key must be authorized before it can be deauthorized. Ensure that the product key you want to deauthorized has been authorized. The key may have been removed without first being deleted.
With License Administrator, verify the key that you want to deauthorize. See To Refresh the License Information List and To Display License Information, both in PSQL User's Guide. Try the deauthorization again and specify a valid key.
7235: Product authorization is not supported on this version of PSQL
This version of PSQL does not support authorization. Try authorization from a machine running PSQL v10.13 or later.
7239: Internet connection cannot access authorization server
The Internet connection cannot access the authorization server to obtain data needed for key validation.
Possible causes include, but are not limited to, the following:
•
A network problem is preventing connection to the authorization server.
•
In your local system registry, authorization server information may be corrupt or missing.
•
Security issues, such as firewall protection, are preventing connection to the authorization server. Configure your firewall or proxy server to allow access to elspv.pervasive.com and bkpelspv.pervasive.com. Additional details can be found in a knowledge base article.
•
The authorization server is down. To confirm, paste elspv.pervasive.com into a browser. If the server is running, it returns a message resembling “NEW ELS MAIN SITE AMS09 version 1.5.2 Build 70 - 11.30.0.14.”
If these explanations and solutions do not address your problem, contact PSQL Technical Support.
7241: Authorization service support files not found
This status code applies only to Linux. The service files that process the Internet authorization and deauthorization processes were not found.
Verify that the web service file elsdid is located in /usr/local/psql/bin and that the file has execution permissions. Try restarting the services or reinstalling PSQL and attempting authorization again.
7252: Authorization key is invalid for the target machine
The authorization key data entered is not valid for the target machine. The key may have been malformed during the offline authorization process.
Try entering the authorization key data again or try offline authorization again.
7254: Key cannot be authorized because it contains invalid license data. Contact your product key vendor.
A failure occurred during authorization of the key. Contact your product key vendor for assistance with troubleshooting.
7260: The offline data does not pass validation
The offline data failed to pass an internal checksum validation. A transmission error may have prevented the checksum validation. Try performing offline authorization again.
7261: Error encountered while saving the offline authorization request data file
An internal error occurred while saving the offline file of authorization request data. Make sure that the directory has appropriate permissions and the target folder exists. Try saving the offline file again.
7262: Error encountered while loading the offline authorization key data file
An internal error occurred while loading the offline file of authorization key data. Make sure that the directory has appropriate permissions and the target folder exists. Try loading the offline file again.
7264: Product key is invalid
The product key entered is invalid. Type or paste a valid product key and try again.
7265: Authorization of the authorization key data must be on the same machine where the authorization request data was generated
The target machine used for offline authorization is invalid. Make sure you are using the same machine for offline authorization as the machine on which you created the authorization request data file.
This status code can also be seen when the offline authorization utility licgetauth.exe is run on a Vista or later Windows OS machine without administrator privileges. To avoid this problem, run the utility from a command prompt window using the Run as an Administrator option.
7267: This stage of the offline authorization is invalid or inconsistent with the requested offline operation
The offline file is not consistent with the offline operation. Try starting the offline authorization from the beginning.
7268: Offline authorization must be performed locally
Offline authorization cannot be performed remotely. Perform offline authorization using a machine with a local Internet connection.
7269: An internal error occurred while trying to process the offline operation on the local machine
During offline authorization an internal error prevented processing. Try offline authorization again.
7300: Local licensing component incompatible with remote licensing server
The licensing component on the local machine is incompatible with the remote licensing server. An older version of the licensing component on the local machine can result in this status code being returned. Contact the product key vendor for a compatible version of the local licensing component.
7305: Product key not found in authorization database
The product key appears to be valid and has a valid checksum but cannot be found in the authorization database on the remote authorization server. Ensure that the product key is valid. If it is, and this problem persists, contact PSQL Customer Support.
7306: Product key is not in a valid state
The system is unable to decrypt the key because the key state is invalid. This error can occur if the system is unable to decrypt the key provided, or if after the key was decrypted the key no longer matches the key’s profile.
Make sure that the key you are using is correct or try using a new key. Contact PSQL Customer Support to report this situation.
7310: Product key has been disabled in the authorization database
The product key specified has been disabled in the authorization database on the remote licensing server. A product key may be disabled for various reasons. Contact PSQL Customer Support.
7311: Product Key is not a valid length
The product key entered is not the correct length. Product keys are either 25 or 30 characters in length, depending on the version of PSQL you are authorizing. Type or paste a valid product key and try again.
7313: Product key is already used on a different machine
The product key has already been authorized on a different machine. First deauthorize the product key on the old machine, then try to authorize the key again on the new machine.
This status code can also result when you try to deauthorize a key on the machine where the key resides. A common cause is that changes to the hardware signature from when the key was authorized now prevent its deauthorization. In that case, repair the key.
7314: This key cannot be deauthorized because it was authorized on a machine with a different machine signature. Either it is being used on a different machine or, more likely, the hardware signature of the original machine has changed. If you are cloning or copying a key licensed for use on only one machine, please purchase another valid license key. Otherwise, repair the key, then try again to deauthorize it.
The signature of the machine on which the key was originally authorized does not match the signature of the machine on which you are attempting to deauthorize the key. This happens in two situations: when a key is copied to another machine and when, due to hardware updates, a machine signature changes. In the first case, you need to purchase an additional permanent key. In the second case, you need to repair the key. After the correct action, reattempt the deauthorization.
7315: Product key is already used on this machine
The product key has already been authorized on the machine. Authorization is not required because it has already been performed.
A key can be on the machine but not in the authorization database on the remote licensing server. If so, clear the key on the machine using the “clear” option with the clilcadm utility, then authorize the key. See License Administrator Command Line Interface in PSQL User's Guide.
7317: Deauthorizing a key requires an authorized key
Deauthorization cannot occur because no key is available. A product key must be authorized before it can be deauthorized. Ensure that the product key you want to deauthorize has been authorized. The key may have been removed without first being deleted.
With License Administrator, verify the key that you want to deauthorize. See To Refresh the License Information List and To Display License Information, both in PSQL User's Guide. Try the deauthorization again and specify a valid key.
7334: Key has no machine signature associated with it
The authorization database on the remote licensing server lists no machine associated with the key. This situation can happen if you copy a VM image that includes a key already authorized, then you deauthorize the key on the original image and attempt to deauthorize the key on the copied VM image.
To prevent this status code, deauthorize the key before you copy the VM image. To remove a key on the copied VM image, clear the key using the CLI License Administrator. The “clear” option removes the key from the local machine without deauthorizing it. After you clear the key, authorize it on the copied VM image.
7335: Operation is not allowed on a Multimachine Key
The operation attempted is not allowed on keys designated as Multimachine. Make certain you are using the correct key with the correct action.
7336: Authorization server prohibits authorization from within a Virtual Machine session
In most circumstances, it is possible to authorize from within a virtual machine session. The only time this error message can appear is if the product key being authorized dates from the early PSQL v10 product line. If it appears, contact your product key vendor or try the authorization again outside of a virtual machine session.
7338: Authorization not allowed in debug mode
The product key cannot be authorized from within a software debugger. Exit the debugger and try the authorization again.
7340: Product key cannot be authorized because the maximum usage count has been reached. Contact your product key vendor.
The product key has already been authorized the maximum number of times allowed by the usage count.
A usage count allows you to authorize a product key again in the event of unforeseen circumstances on a particular machine. For example, if you had to replace the storage disk, you would have to reinstall the product and authorize the product key again on the same machine.
7341: Product key cannot be authorized because the maximum number of authorizations has been reached. Contact your product key vendor.
The product key has already been authorized the maximum number of times allowed.
Product keys have limited number of times they can can authorized and deauthorized. Contact your product key vendor if you need to authorize the product key again.
7342: Product key cannot be deauthorized because the maximum number of deauthorizations has been reached. Contact your product key vendor.
The product key has already been deauthorized the maximum number of times allowed. Product keys have limited number of times they can be authorized and deauthorized. Contact your product key vendor if you need to deauthorize the product key again.
7343: Product key cannot be repaired because the maximum number of repairs has been reached. Contact your product key vendor.
The product key has already been repaired the maximum number of times allowed.
Product keys have limited number of repairs allowed. Contact your product key vendor if you need to repair the product key again.
7346: Product key has been authorized on the maximum number of machines allowed. Contact your product key vendor.
The product key you are trying to authorize has already been authorized on the maximum number of machines allowed for the product purchased.
Deauthorize the key on one of the machines where the key has already been authorized before you try to authorize the product and use this key or contact your vendor to purchase additional licenses.
7347: Maximum number of offline authorizations has been reached. Contact your product key vendor.
The maximum number of offline authorizations allowed for the product key has been met.
Product keys have limited number of offline authorizations allowed. Contact your product key vendor if you need more offline authorizations.
7348: Temporary License key cannot be deauthorized
Temporary (non-removable) license keys may be authorized only once and cannot be deauthorized.
7349: Temporary License key has already been authorized
The temporary license has already been authorized and cannot be authorized again.
You are allowed to authorize a temporary license key once. A temporary license cannot be added to a machine that already uses it.
7365: Record changes were blocked due to multi-user access
Changes to the target record were not committed because of multi-user access. Refresh, verify the record, then resubmit your changes.
7366: Authorization server is busy
The authorization server is currently busy. Please try authorizing again later.
*Tip: For troubleshooting tips see the Knowledge Base on the PSQL Web site and search for “product authorization”.
7367: Multi-user access is preventing the operation from being completed
The requested operation cannot be completed due to multi user access conflicts. Wait a few moments and try the operation again.
7369: The server is currently unavailable. Please try again later.
The requested server is inaccessible at this time. Try accessing the server again in 20-30 minutes.
7380: The Country or City is in the embargo list
The system detected an IP address from a country or city that is on the restricted embargo list. Please contact PSQL Customer Support if you feel you reached this message in error.
7422: Login failed. The user credentials are invalid.
The credentials for the user are not recognized. Check the user credentials and try logging in again.
7423: Permission for requested operation has been denied
The current user does not have permission for the requested operation. Try logging in as a user with appropriate permissions, or request appropriate permission.
7424: User account is inactive
The requested user account is inactive. The user account needs to be authorized, or an active user account needs to be selected.
7449: Key cannot be set to active because of a pending issue with the key vendor. Contact your product key vendor.
The license data prevents this key from entering the active state. Contact your product key vendor.
7450: OEM ID does not exist
The OEM ID no longer exists. Select another OEM ID to use, or contact PSQL Support for assistance.
7451: OEM account is inactive
The account for the OEM is no longer active. Select an active OEM account, or contact PSQL Support for assistance.
7452: OEM user is inactive
The OEM user is no longer active. Select an active OEM user to use, or contact PSQL Support for assistance.
7456: Invalid OEM user ID for the requested record
The record you are trying to access has a different OEM user ID associated with it than the OEM user ID currently logged in. Make sure that you are accessing the correct record, or that the OEM user ID logged in is correct.
7457: OEM product (Workgroup/Server) is not an authorized product
Products are authorized to OEMs based on their contractual agreement with Actian Corporation. The requested product is not authorized for the current OEM. Select an authorized product to continue.
7458: Maximum number of resets or repairs for the product key has been reached
The maximum number of operations (resets or repairs) for the product key has been met. Product keys have limited number of resets and repairs allowed. Contact your product key vendor if you need to perform one of these operations again.
7471: Maximum number of seats for this OEM has been reached
The maximum number of seats for the OEM has been met.
OEM accounts have a limited number of seats based on their contract with Actian Corporation. Contact PSQL Customer Support if you need to add seats to the OEM contract.
7472: Maximum number of licenses for this OEM has been reached
The maximum number of licenses for the OEM has been met.
OEM accounts have a limited number of licenses based on their contract with Actian Corporation. Contact PSQL Customer Support if you need to add licenses to the OEM contract.
7473: Maximum number of seats for this OEM account has been reached
The total maximum number of seats has been met. Accounts within an OEM have a limited number of seats based on their contract with Actian Corporation. Contact Actian Corporation if you need to add seats to the account.
7474: Maximum number of licenses for this OEM account has been reached
The total maximum number of licenses has been met.
Accounts within an OEM have a limited number of licenses based on their contract with Actian Corporation. Contact Actian Corporation if you need to add seats to the account.
7475: Invalid value for user count, session count, or data in use
The requested value is either not defined or is greater than the maximum limit currently available.
7477: The OS Platform type is invalid for this account
The operating system requested for the product key is invalid for the current account. Make sure that you are using the correct account and select a valid operating system.
7478: Product type is invalid for this account
The product type requested for the product key is invalid for the current account. Make sure that you are using the correct account and select a valid product type.
7479: Upgrade type is invalid for this account
The product type requested for the product key is invalid for the current account. Make sure that you are using the correct account and select a valid product type.