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 f more
The AxProtector option '-a' was used in the past to place the AxEngine at a previously reserved area during encryption. This was necessary when the application did not provide enough space to accommod more
This message occurs during encryption with AxProtector, if there is not enough space in the application to accommodate the AxEngine. To fix this, you need to create your application with a larger File more
AxProtector .NET provides several attributes via WupiEngineNet.dll that can be used to target the protection of specific namespaces, classes and methods. The attributes are called Protection and Licen more
When using AxProtector .NET elements can be specifically excluded from obfuscation by using attributes. For this purpose, the obfuscation attribute from the System.Reflection namespace can be used. Th more
Please proceed as follows: Call the encrypted application. Please adjust your proxy information. java -Dhttp.proxyHost=proxy.company.local -Dhttp.proxyPort=8080 -jar application.jar Alternatively you more
The date is set to this value after the encryption to guarantee that several encryptions of the same application are binary identical - otherwise the modification date would be different. Alternative more
The error 1001 means "FileNotFound". It occurred since your WkFirm.wbc file has not been found. The WkFirm.wbc file is required for programming licenses and encrypting applications. You should have re more
With AxProtector Java 10.20, the encryption of a Java application that contains an 'Index.list' will abort with an error. For example, if you were using AxProtector 10.10 and a JAR archive with an 'In more
Problem: Using an encrypted "fat binary", i.e. an application that contains 32-bit and 64-bit components, can cause problems on macOS. Solution: The application should be split for use/encryption to c more
To import the update into your FSB (Firm Security Box), please proceed as follows: I. Create context of FSB 1. Open Webmin of the CodeMeter License Central with :10000 behind the LC-IP in the web brow more
Components as pure CodeMeter License Central Feature. Components serve to group different products and make it easier to sell them all at once. Afterwards you have only programmed different Product It more
There are several entries in an FSB (Firm Security Box). Depending on the type of Firm Code different entries have to be monitored. For CmDongle (1xx.xxx) or CmActLicense (5.xxx.xxx) Firm Codes these more
When CodeMeter License Central 3.21 is installed, a broadcast is set by default in the Server Search List. This results in noticeably slower activation, since the Firm Security Box (FSB) access always more
Encrypting may produce arbitrary patterns, and, as a result, an anti-virus program may detect these as a potential virus. Short-term actions You may check the settings of the anti-virus program. Event more
There is generally no single admin account in the CodeMeter License Central graphical user interface. The admin privileges in CodeMeter License Central can be assigned from an existing admin to any ot more
This error occurs, if you have not checked the parameter "Firm Item must exist" in the transfer scheme, but you do not have an "Unlimited" FSB (Firm Security Box). Only if you have an "Unlimited" FSB, more
This error message means that an attempt has been made to import an update item that refers to license properties that do not exist. When you create the update item, you specify that it is an update a more
The licenseCentral.log log file displays the following error during activation attempts: java.lang.reflect.InvocationTargetException: null ... Caused by: java.lang.StackOverflowError: null This is due more