Errors appear in the log files after updating the index of Assets Server

After updating the index of Assets Server, the following errors might appear in the log files:

ERROR com.ds.acm.ak - NEW CONFIGURATION IS INCORRECT: Compass settings of the field language were changed. It is incorrect to modify the field.

WARN com.ds.acm.warnings.Server - warning: Detected illegal changes in new asset info

com.ds.acm.al: New configuration is incorrect, see log for details. Please review asset info configuration.

These errors are generated by a safety feature that is in place during the Assets Server service startup which compares the full-assetInfo.xml file (created during the last successful startup) with the new-assetInfo.xml file (constructed from the (internal)default-assetinfo file and the possible (custom) configured custom-assetinfo file).

If the compare results in a difference, the above errors are thrown in the Assets Server log with a description where this difference is found.

This safety feature is in place to protect the system from starting with an incorrect assetinfo file.

A common scenario for this situation to occur is when changes have been made to the configuration of the assetInfo in the custom-assetinfo.xml file. It may also occur after upgrading Assets Server to a newer version with an updated default assetinfo.

It is important to be aware if recent changes have been made to your custom-assetInfo.xml:

• Yes, I just updated the configuration of the custom-assetInfo file which resulted in this log message. Please read the log message carefully; it might describe where a possible configuration error occurred.

• No, I just upgraded my Assets Server version (with a new/changed default assetinfo file) which resulted in this log message.

Solution 1

Update the asset index once more.

Solution 2

Info: Performing the described step requires direct server access. Depending upon how your system is hosted and the level of access you have to that system, coordination may be required with your Partner or WoodWing Support team. For a full overview of the steps that need to be done by WoodWing and how to request them, see WoodWing Cloud - Change management.

Do the following:

Step 1. Stop your Assets Server Cluster nodes.

Step 2. On each node, access the <Assets Server location>/Elvis Hot Data/elvis-data/assetInfo/ folder and remove the following files:

• full_assetinfo.xml
• new_assetinfo.xml

Note: Make sure you do this on every node (including the nodes that act as the Processing Server and job runner).

Step 3. Start the Assets Server Cluster.

New files will be created and the errors should not appear anymore.