The error 106 refers to an "invalid handle" and occurs if a handle was used CodeMeter does not know.
This may, for instance, happen in the following cases:
1. You use a protected software or a software applying CodeMeter Code API/Wupi API and while doing so restart the CodeMeter service. This renders all handles invalid and reusing handles in your software result in error 106.
This error message results from a security feature activated on default, i.e. the code integrity check. In AxProtector you are able to activate or deactivate this feature. In the AxProtector GUI you find this option on the navigation page "Security options | Advanced". For the commandline use the parameter -cav.
The code integrity check covers your protected application and DLLs to ensure at runtime, that the files are your original files and no manipulated files are used. In addition, for every second runtime check also the memory integrity of the process space of your application is checked. If then, for example, at runtime, a third party program modifies something in the memory of the process room, for security reasons the check triggers the exit of your application, for example, to prevent a reverse engineering of other manipulations of your application at runtime. Please find a description and more information in the separate CodeMeter Developer Guide documentaion in sections "Automatic Software Protection using AxProtector | AxProtector Tab | Windows Application or DLL | Security Options | Advanced Security Options" and "Automatic Software Protection using AxProtector | Commandline Options for AxProtector | Options for Encrypting and Decrypting".
If the code integrity check falsely strikes, this may also may be triggered by an anti-virus programs. These may also check modifications in memories of running applications. Then it is recommended to exclude your protected application from the anti-virus check and to specify the application as exception.
If the error 229 occurs. the problem does not involve the license update file (*.WibuCmRaU) but the license request file (*.WibuCmRaC) as basis for programming the update.
Exactly from this context file a previous update file must have been already programmed and imported into the CmContainer. On a second import of the update file the error occurs because in the meantime the CmContainer already has a different status due to the first import.
Each CmContainer holds an update counter, i.e. the "Firm Update Counter" (FUC), which has a specific counter status. If a context file is created from the CmContainer, the FUC holds the actual count.
The subsequent programming of the update file involves an increment of the FUC by a defined number. The number of counter units depend on the Product Item Options programmed. In addition, for security reasons, the update file also holds the old, i.e. to be expected, counter status to enable a validation of the CmContainer status. On importing the update file it is first checked whether the CmContainer has the expected counter status. If the validation is successful, the FUC in the CmContainer gets a new FUC value. However, if the counter does not match the expected value, the error 229 is issued and the update process is stopped.
To avoid this behavior, please make sure that for each new update programming you must use a current license request context file.
This error occurs because either the CmFirm.wbc file is missing completely or does not contain your Firm Code. You must import this file to your system.
In addition to the Firm Security Box (FSB), programming licenses requires the CmFirm.wbc file with your Firm Code. You received this file from Wibu-Systems when you became a customer. You might find this file on another system, e.g. located in "%ProgramData%\CodeMeter\DevKit".
You can open the CmFirm.wbc file using a text editor and check for your Firm Code, i.e. not only the Test-Firm Code, e.g. 6000010, is specified.
If the required CmFirm.wbc file is not available, please contact Wibu-Systems Sales.
For importing the correct CmFirm.wbc file, please proceed as follows:
1. Open CodeMeter Control Center
2. Navigate to the menu item "File | Import License" and select the CmFirm.wbc file.
Alternatively drag & drop the file onto CodeMeter Control Center. This however requires that the CmFirm.wbc file has been locally saved before.
Error 231 occurs when trying to assign a license to a CodeMeter License Server whose license access permissions exclude the client.
Please open CodeMeter Control Center on the server and use the WebAdmin button to open the WebAdmin web interface.
Navigate here to "Settings | Server | License Access Permissions".
There are two different modes for the license access permissions:
- Simple: A simple whitelist that defines which clients may occupy a license.
- Advanced: A set of rules with Active Directory integration that allows more complex configurations (Windows only).
In most cases, the simple mode is sufficient.
Now check which clients are already registered and, if necessary, add all clients that should have additional access to the licenses. You must use either the IP or DNS name of the client to do this.
If you want all clients to have access and there should be no special restrictions, use the simple mode and clear the list completely.
After you have made the desired changes, restart the CodeMeter service.
To do this, you can use the menu option "Action | Restart CodeMeter Service" in CodeMeter Control Center.
If the problem persists, create a CmDust.log of client and server and send it to us.
Event 91 occurs, if an attempt is made to re-establish encrypted communication with a CmDongle too often within a certain time period.
For security reasons the CmDongle limits how often an encrypted communication is restablished within a certain time period to make the automatic analysis of the communication with common hacking tools more difficult. If event 91 occurs, this means that the dongle has locked itself to prevent further attempts to establish an encrypted communication. This lock is valid for 5 minutes. During this time, the CmDongle has to stay connected without trying to establish a new communication. So just leave the dongle connected for a while and wait until the lock is released.
The limit is chosen in a way that the lock should not engage during normal use. So, if this event occurs, it means that something has gone wrong. Mostly due to a faulty USB port or controller. It is best to test on another port or PC. If it happens again on another PC, it is possible that the CmDongle could have a technical defect. In this case, you should replace the CmDongle. Please make sure that you do not use 3rd party software which could influence the USB communication and therefore disturb/prevent the encrypted communication.
This behavior occurs, when the number of transactions allowed by your Firm Security Box (FSB) is used up. You cannot use your Firm Code any more to program an empty CmContainer.
In order to provide you with additional transactions, we require a license request (Context) file of your FSB sent to sales(at)wibu.com.
If you are using a Firm Code 1xx.xxx or 5.xxx.xxx (i.e. no Universal Firm Code with 6.xxx.xxx) we need a Context File, which you can send to firstname.lastname@example.org
To create the Context File of your FSB, please proceed as follows:
1. Connect the FSB to the computer.
2. Open CodeMeter Control Center.
3, Select the FSB in the left Licenses tab.
4. Click the "License update"-button.
Licenses are read and the CmFAS Assistant opens.
5. Select the options "Create license request | Extend existing license | Firm Security Box Item (99)" on the subsequent wizard pages.
6. Specify the path and file name to save the context file under any name to your chosen location.
This error occurs, if your CodeMeter Runtime installation still contains some old components.
Please check, if the file 'C:\Program Files (x86)\CodeMeter\Runtime\bin\WibuCm32.dll' is still on your system and delete it if necessary.
Then uninstall CodeMeter completely again.
If you find several entries for the CodeMeter runtime in the Control Panel, please uninstall them all.
Finally restart your system once and reinstall the current CodeMeter Runtime.