Troubleshooting Licenses
This section describes how to troubleshoot issues with licensing.
- 1 Troubleshooting Linux issues
- 2 Troubleshooting Activation Keys Issues
- 3 Troubleshooting Reported Licensing Errors
- 3.1 Inspecting existing licenses
- 3.2 Verifying the Connection to a License Server
- 3.3 Inspecting the License folder
- 3.3.1 Local License Files
- 3.3.2 Server Connection Files
- 3.3.3 License Server License Files
- 3.3.4 Floating License Files
- 3.4 Generating a Diagnostic File
- 3.5 Hosting a License Server on a Computer Already Having Node-locked Licenses
- 3.6 Checking License count from a license server
- 3.7 Vortex License Manager Shows Duplicated Products
- 3.8 Generating Floating Licenses Files on an older machine
- 3.9 Contacting CM-Labs Customer support
License Folder
You can find any license files that the Vortex License Manager generates in the C:/CM Labs/Licenses folder on Windows or /opt/cmlabs/licenses/ on Linux. You may need special user privileges to write files in those locations. If you do not have privileges to write files in license folders, the license manager application alerts you that it cannot write files at that location.
A Vortex license server and a local install of Vortex Studio uses the same folder for licensing.
License File
Vortex license files have the extension .lic. They can be viewed in a text editor for trouble shooting. Most licenses file generated ends up in the license folder.
License files can also exist in the Vortex Studio bin folder, in the server folder of the RLM server binaries or an embedded Vortex Studio application folder.
License files in Vortex Studio folders are provided by CM-Labs and removing them will cause Vortex applications to stop working. If those files are deleted by mistake, you will need to reinstall Vortex Studio.
Troubleshooting Linux issues
Before going any further, the license manager requires root permissions in order to run some commands.
The license manager must be run as root.
Troubleshooting Activation Keys Issues
Cannot connect to Activation Server
To generate a license file using an activation key, you must be able to connect to the RLM activation server via the internet.
The activation server URL is http://hostedactivation.com/cmlabs.
Verify the Connection to the Activation Server
To Verify the Connection to the Activation Server on Windows
The connection status to the activation server is available via the Vortex License Manager.
Launch the Vortex License Manager.
The status of the activation server is displayed with icons on the status bar.
A warning will be shown should there be an issue.
Verify the Connection to the Activation Server on Linux
Execute the following command:
./VortexLicenseManager --statusThe status appears on the screen.
Fixing Connection to the Activation Server Issues
If you have no connection to the activation server, check your Internet connection.
If the machine cannot access the Internet, see Generating Node-Locked License Files for Another Computer to generate license files from another machine.
If the machine has limited access to the Internet, it needs to be able to reach the activation server at http://hostedactivation.com/cmlabs .
If your connection is good, the problem is likely an issue with the activation server. Try again later.
The license file was deleted from the computer
If for some reason a license file was deleted on a given PC, it can be regenerated using the same activation key on the same machine even if the key was already activated.
Reusing an activation key is only allowed on the same machine originally used for license file generation.
Troubleshooting Reported Licensing Errors
Vortex Studio applications are giving you licensing errors. The first step is to inspect the available licenses.
Inspecting existing licenses
Launch the Vortex Studio License Manager application to see any existing Vortex Studio licenses that are currently available appear.
For more details, see Inspecting Existing Licenses
The window also shows any detected license errors. See below.
Verifying the Connection to a License Server
When you connect to a license server, a special server.lic license file is generated in the license folder. The license file indicates the computer that hosts the license manager. If the host is valid but a license server is not running, Vortex Studio can encounter performance issues (license checks gets very slow as each time the connection times out).
The Vortex License Manager application can detect that the host is valid while the license server is not running, and alert you.
If you are not connected to the license server, please see Connecting to a License Server.
Detecting Server Connection Errors
Vortex Studio-based applications (i.e., Vortex Studio Editor, Vortex Studio Player, Vortex Studio Director and Simapp) all report server connection errors. In Windows, when an application detects a server connection error, it prompts you to start the Vortex License Manager application.
To diagnose a server connection error, use the Vortex License Manager.
To Diagnose a Server Connection Error (Windows)
Launch the Vortex License Manager. If the application detects a server connection error, an error message appears.
Make sure the server is running at the specified location.
If the
hostname:portis invalid, delete the file.
To Diagnose a Server Connection Error (Linux)
Launch the Vortex License Manager with the following parameters:
./VortexLicenseManager --listThe command lists all license files and their available product. If the application detects a server connection error, the following message appears:
License server at address <your machine>:<port e.g. 5053> is not running. Please start the server or delete the <file name> license file to remove the reference to this server.Make sure the server is running at the given location.
If the
hostname:portis invalid, delete the file.
Fixing Server Connection Errors
When there is a server connection error, the application prompts you to do the following:
Check that the license server is running on the machine with the hostname specified in the error message.
The server should be started on that machine.
If the server is running, check if the machine is reachable from the client machine.
Delete the file that refers to the license server.
When running a license server behind a firewall, please make sure your firewall settings are properly configured to allow communication with the license server.
Check firewall settings, the license server needs 2 ports
5053
the default RLM server port, which by default change every time it restarts.
For more information about this, please refer to the License Servers section.