Message shown above is the Windows display.
On text-mode systems, message contents are
the same but appear in a text message box.
|
Registration Issues |
A PxPlus license registration can become invalid for various reasons, such as file tampering or corruption, moving or copying the system Activation Keys control file ACTIVATE.PVX, or expiration of the key itself.
Starting with PxPlus 2017, the system can help to recover and update your registration keys using the built-in Online Registration process for any of the following:
A list of possible registration issues and resolutions is provided below. Use these links to jump to a particular issue:
Upgrading Software from a Prior Version
System Cannot Connect to PVX Plus Server
Missing OpenSSL Libraries on Linux
WindX and Host Version Difference
PxPlus Directories Do Not Have Full Permissions
If you experience an issue that requires additional assistance, submit a Helpdesk ticket to PVX Plus Support at https://helpdesk.pvxplus.com. Select the Open a New Ticket button or top menu bar option.
Enter your support request and include the following:
If the system detects a valid ACTIVATE.PVX file that has been copied, it will issue the following message:
|
|
If you have moved the software and wish to re-register the software on the new machine, select Yes. The system will then attempt to connect to the PVX Plus Technologies server.
If the registration matches the one currently associated with the license, a new key will be issued.
If the registration does not match the machine currently registered, the registration process will fail, and you will receive the following message:
To register your product on the new system, you will need to request a license move. For steps, see Moving PxPlus License to New System.
If the system detects a valid ACTIVATE.PVX file that has expired within the last two weeks, it will issue the following message:
Select Yes to have the system contact the PVX Plus Technologies server to see if the expiry period has been extended.
If the registration matches the machine currently associated with the license and the expiry date has been extended, a new key will be issued, and your registration will be updated.
If the registration has not been extended, you will receive the following message:
To renew the license or purchase a new license, contact PVX Plus Sales at sales@pvxplus.com.
If the system detects a valid ACTIVATE.PVX file but the version is more than three versions back from the .exe you are trying to use, it will issue the following message:
Select Yes to have the system contact the PVX Plus Technologies server to see if the license is entitled to a newer version.
If the registration matches the machine currently associated with the license and the version number on the server is different, a new key will be issued, and your registration will be updated. You will then receive the following message:
If the version number has not changed, you will receive a message similar to the following:
To upgrade the license or purchase a new license, contact PVX Plus Sales at sales@pvxplus.com.
Depending on the version of PxPlus installed, the PxpKeys directory resides in the PVX Plus Technologies directory by default and contains the system Activation Keys control file ACTIVATE.PVX.
If PxPlus was not installed in the default PVX Plus Technologies directory, the PxpKeys directory may not have been created. As a result, the activation program cannot run, since it cannot locate the ACTIVATE.PVX file. See Activation Messages.
If this occurs, submit a Helpdesk ticket to PVX Plus Support at https://helpdesk.pvxplus.com. For details on what to include, see Submitting a Helpdesk Ticket.
If your system cannot connect to the PVX Plus Technologies server, submit a Helpdesk ticket to PVX Plus Support at https://helpdesk.pvxplus.com. For details on what to include, see Submitting a Helpdesk Ticket.
On Linux, if you are having problems connecting to a secure server using TCP, this may be due to the system's inability to find the OpenSSL system libraries. This may also cause issues when running the online registration process, getting updates, or performing any form of network/internet request using a secure connection.
See Linux Issues.
The easiest way to test whether the libraries can be found is to attempt opening a secure connection to the target system or to any internet server. To do this, issue the following command from the PxPlus Command line:
OPEN (1) "[tcp]www.pvxplus.com;443;secure"
If the libraries are not found, the following error will occur:
Error #13: File access mode invalid
Last IO to [tcp]<a href="http://www.pvxplus.com;443;secure,">www.pvxplus.com;443;secure,</a> channel 1
Unable to locate SSL library (ssleay or libssl) (err/ret=9/9)
This indicates that the OpenSSL libraries cannot be found. However, on most Linux systems, they do exist, but the operating system may not have created the proper linkage to the version of OpenSSL you are running. The library files often are suffixed with the specific version of OpenSSL being used, and for PxPlus to use them, it needs a link to the correct library.
Since PVX Plus ships a "generic" version of PxPlus for multiple versions of Linux, generic names are used (without the version number) in the SSL interface. Most Linux systems include these by default, but some do not; therefore, you must define which OpenSSL library version to use.
If the generic link does not exist, you can fix this by first finding the installed SSL libraries (libssl.so and libcrypto.so) on your Linux server. Generally, they will be in one of the following locations:
32-bit systems: /lib -or- /usr/lib
64-bit systems: /lib64 -or- /usr/lib64
To find which libraries are installed, you can use the operating system 'ls' command:
ls -l /usr/lib/libssl*
This will display something similar to the following:
-rwxr-xr-x 1 root root 470376 Aug 8 21:38 /usr/lib/libssl.so.1.0.2k (This indicates you have version 1.0.2k of the OpenSSL libraries installed.)
For PxPlus to find this library, you need to create a symbolic link within the system library files to the .so file:
ln -s /lib/libssl.so.1.0.2k /lib/libssl.so
ln -s /lib/libcrypto.so.1.0.2k /lib/libcrypto.so
To give you an idea of what this will look like, the following is the 'ls' of a Centos 7 library directory:
[root@v1153828 ~]# ls -la /usr/lib64/libssl*
-rwxr-xr-x 1 root root 370584 Aug 12 11:55 /usr/lib64/libssl3.so
lrwxrwxrwx 1 root root 16 Sep 18 00:49 /usr/lib64/libssl.so -> libssl.so.1.0.2k
lrwxrwxrwx 1 root root 16 Sep 18 00:47 /usr/lib64/libssl.so.10 -> libssl.so.1.0.2k
-rwxr-xr-x 1 root root 470376 Aug 8 21:38 /usr/lib64/libssl.so.1.0.2k
You can see it is set to use OpenSSL version 1.0.2k.
Ensure that the WindX client version and the host PxPlus version are the same.
For example, if the host is running PxPlus 2025, the WindX client should also be running PxPlus 2025 and not a previous version.
Modify the properties of the PVX Plus Technologies directory (Windows) or the PxPlus directory (UNIX/Linux) and all its sub-folders to give full permissions. See Permission Issues.
