License activation and troubleshooting
- 1 Single User (local) License
- 2 Floating (Network) Licenses
- 3 Enhanced configuration
- 3.1 Offline (File-based) activation
- 3.2 Offline (File-based) deactivation
- 3.3 Deactivate or move a license to another computer (single user or floating)
- 3.4 Delete a corrupt license container
- 3.5 Find out your ticket id (license key)
- 3.6 What does a specific Error Code mean?
- 3.7 Creating a CmDust.log file
- 3.8 Finding the CmAct files
- 3.9 查找 CmAct 文件
- 3.10 License activation, Ports and Firewalls
The content of this page will be moved to separate articles; you will find the links in the old sections below.
If this document doesn’t help to solve your problem, please contact https://kistlergroup.atlassian.net/wiki/spaces/JBEAM/pages/416153601 .
Single User (local) License
The content of this section has been moved to: https://kistlergroup.atlassian.net/wiki/spaces/JBEAM/pages/742391809 in general, especially https://kistlergroup.atlassian.net/wiki/spaces/JBEAM/pages/677642241 and https://kistlergroup.atlassian.net/wiki/spaces/JBEAM/pages/680591361.
Floating (Network) Licenses
The content of this section has been moved to: https://kistlergroup.atlassian.net/wiki/spaces/JBEAM/pages/728498177
Enhanced configuration
Offline (File-based) activation
The content of this section has been moved to: https://kistlergroup.atlassian.net/wiki/spaces/JBEAM/pages/742391809 in general, especially https://kistlergroup.atlassian.net/wiki/spaces/JBEAM/pages/680591361
Offline (File-based) deactivation
The content of this section has been moved to: https://kistlergroup.atlassian.net/wiki/spaces/JBEAM/pages/742391809 in general, especially https://kistlergroup.atlassian.net/wiki/spaces/JBEAM/pages/693043201
Deactivate or move a license to another computer (single user or floating)
The content of this section has been moved to: https://kistlergroup.atlassian.net/wiki/spaces/JBEAM/pages/742391809 in general, especially Deactivation/ Moving
Delete a corrupt license container
First locate your CodeMeter installation folder and execute the cmu32.exe file with the following parameters. Do this in Windows Command Prompt (cmd) and use the following parameters:
"c:\Program Files (x86)\CodeMeter\Runtime\bin\cmu32.exe" --lt-cleanup --container -s <container-serial>Make sure you do not omit the quotation marks when copying the above command line!
Only replace the placeholder <container-serial> with the damaged container ID, e.g. 130-557054596
Find out your ticket id (license key)
To get the license key of an activated license do the following steps:
Open the app CodeMeter Control Center
If there are multiple ones, select a Wibu Container and open Webadmin
Click on the product code of the jBEAM license you want to analyze (usually there should be only one)
Copy the license key (entry Extended Protected Data #127; hexadecimal encoded ASCII) to the clipboard
Convert it to ASCII, e.g. with an online converter like https://coding.tools/hex-to-ascii
What does a specific Error Code mean?
There are several situatiations, where the activation or usage of a license may fail. In these cases usually an error code like the following may displayed:
Error
Internal error during license transfer. Please contact the support.
0x18088006
CodeMeter License Central WebDepot v19.07.210.616.ws
…There is a list of all error codes available at software-licenses.kistler.com/testtools/errorCodes.php. On this page you will usually also find a description and help for the particular error.
Please note that the German version of the page currently offers significantly more information than the English version.
Creating a CmDust.log file
For tracking down Sometimes it is useful to create a CmDust.log file to detect problems in the license background processes.
(if you are using a CmDongle, connect your CmDongle).
Search for and start the CmDust application in the Windows start menu: Start -> All Programs -> CodeMeter -> Tools -> CmDust or simply type “CmDust”.
A command line window opens automatically and closes again after a few seconds.
Shortly after it, a new explorer window will open and point you to the newly created file "CmDust-Result.log" in your user directory.
Then please send us this small "CmDust-Result.log" file by e-mail. (ZTZ-License@kistler.com)
Finding the CmAct files
In some cases it is necessary to analyze the so-called CmAct files in addition to the CmDust.log file to diagnose license problems.
These files are located in the following directories, depending on the operating system used
Windows: Windows: C:\ProgramData\CodeMeter\CmAct
Linux: /var/lib/CodeMeter/CmAct
MacOs: /Library/Application Support/CodeMeter/CmAct
It is best to zip the contents of the entire directory and send it to us. (ZTZ-License@kistler.com)
License activation, Ports and Firewalls