Import error: equivalence.xml is not properly configured

This error occurs when you have a specialized document type in your deployment and the equivalence.xml is not configured for it.

Description

You receive a message in the Import Errors dialog similar to this:

Error importing file: equivalence.xml is not properly configured to handle fileType objects.

Solution

Check equivalence.xml in Repository/system/conf to make sure it is configured to handle the type of file that had the error.

When your deployment has specialized document types (such as custom topic or map types), equivalence.xml must be configured so that these specialized document types are treated as equivalent to the generic topic or map types.