There exist different Firm Codes for different CmContainer types. 1. 1xx.xxx = CmDongle Firm Code, only importable into CmDongles (Hardware) 2. 5.xxx.xxx = CmActLicense Firm Code, only valid as CmActL more
To start the CodeMeter daemon manually, please proceed as follows: 1. Open the System Settings - General LogIn Items. 2. you will find a CodeMeter Icon 3. Deactivate the CodeMeter Deamon via the swits more
To program the Firm Access Counter (FAC) using CodeMeter License Editor, you must first create a Context File (*.WibuCmRaC) of the affected CmContainer and Firm Code. As always, your Firm Security Box more
If the CodeMeter service does not start, this could also be the case for security reasons. In this case, an encrypted file in the format "LicenseLock .log" is stored in the CodeMeter logs directory, b more
The LicenseLock-*.log file The file LicenseLock-*.log is created, if the Firm Access Counter (FAC) has been modified according to AxProtector encryption settings and the Firm Access Counter has reache more
To create a CmDust.log, depending on your operating system, please proceed as follows: Windows 1. Connect CmDongle. This step is omitted if using CmActLicense. 2. Open CmDust using the "Start All Prog more
If the CodeMeter service (CodeMeter.exe) stops automatically after a few minutes, this indicates that the self-diagnosis of CodeMeter strikes because a process attached to CodeMeter is detected. For e more
Especially for Linux systems without graphical user interface, it is necessary to configure CodeMeter runtime settings directly in the Server.ini file of CodeMeter. To make corresponding changes in th more
In general, it was examined which possibilities our driver software "offers" foreign code to potentially carry out manipulations on systems. Please note that the security of protected/encrypted applic more
In case of trouble with the WibuKeyShellExtension there might also be other difficulties. Therefore, we recommend a clean uninstall and reinstall as described in KB-0016. If the difficulties refer exc more
This error occurs because WibuKey version 6.40 conflicts with software that is protected with AxProtector version 9.0. You need to perform a clean uninstall of WibuKey and a subsequent reinstall of Wi more
Problem Some notebooks and newer PCs do not supply the required LPT interface providing enough power. This can cause a timeout problem. Solution A timeout occurs, if the WibuKey driver cannot access t more
Problem Your firm license file wkfirm.wbc or wkfirm.dat has been overwritten. Solution Copy your firm license file (youir own License file) wkfirm.wbc into the directory [..\WIBUKEY\Devkit\bin]. WkFir more
There is the possibility to run the WibuKey installer on Windows in a silent mode and with customized settings. To do so, please follow this short instruction: - Unpack the WibuKey Runtime Kit you wan more
Problem When installing the German Development Kit (SetupDE.exe) this error message displays, if in the Regional Options the location is not set to "Deutsch (Deutschland)", but to "Deutsch (Österreich more
In this case, please check the following: a) Is the WibuBox 'locally' recognized on the server in the WibuKey tool of the control panel? b) Has the service 'WibuKey Network Server' actually been start more
With additionally inserted parallel ports via PCI card, it may happen that WibuBoxes won’t be connected by the WibuKey software. In this case, the E/A area has to be configured manually. Please do as more
Reservations are always made when servers are accessed via 'Broadcast' or 'DNS Name'. Normally the reservations are used several times. However, if several reservations for the same entries come from more
This seems to be a problem of the shell extension which is responsible for the "Mouse Menu". At "C:\Program Files\WIBU-SYSTEMS\System" you will find a repair script that can fix this. Run the file "Wi more