Please check the format settings on the web server hosting the WebDepot.
Here the format UTF-8 (without BOM) must be used.
For example, the UTF-8 BOM format leads to checksum problems.
Some programs insert a byte order mark (BOM) at the beginning of files in UTF-8 files.
The BOM consists of the byte sequence EF BB BF, which usually appears in non-UTF-8 capable text editors and browsers as ISO-8859-1 string ï "¿ and is responsible for compatibility problems.
To avoid such problems, files should be saved in UTF-8 format without BOM.
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 action when you create the license entry. Below this, you must enter another item as a reference (which is to be updated).
If the update is to be imported, the license identifiers of the referenced item are used to check whether the update can be imported. If the license identifiers cannot be found in the CmContainer to be updated, the error "No identifier found for update" occurs.
In this case, you have to take a look at the license identifiers of the reference item. You can see them by editing the item and changing the view (bottom left) to "Advanced".
Keep in mind, that all item properties are copied when an order is created. However, only the ID of the reference item is saved. This means that subsequent changes to the license identifiers of the reference item will affect orders that have already been created.
The licenseCentral.log log file displays the following error during activation attempts:
Caused by: java.lang.StackOverflowError: null
This is due to insufficient stack memory of each thread.
The stack memory can be increased to avoid this error. Please proceed as follows: