What causes errors during the import process?

During the import process, different kinds of errors are likely to occur at different phases.

Import process

IXIASOFT CCMS processes files in the following phases during an import:

  1. Validate the DITA XML in the files
  2. Validate the references in files
  3. Import the content and check it in
  4. Associate the imported content to branches (only applies to IXIASOFT Dynamic Release Management (DRM) deployments

Errors related to file validation

Errors in this phase happen because files are either not well-formed DITA, or their structure does not match the DTDs in IXIASOFT CCMS. If any of the files cannot be validated against the DTDs in IXIASOFT CCMS, the import is canceled and an error message is displayed.

Errors related to reference validation

Errors in this phase happen because files that are referenced are not included in the content uploaded, nor are they already in IXIASOFT CCMS. If any links or references are broken, the import is canceled and an error message is displayed. IXIASOFT CCMS also checks for duplicate IDs and key definitions.
Note: These errors also occur as a consequence of file validation errors. If a file could not be validated against a DTD, it is dropped from the import. Any file that referenced the invalid file is then considered to have a broken link because the invalid file is 'missing'.

These errors resolve themselves once the invalid files are fixed and pass validation.

Errors related to importing

Errors in this phase often happen because of configuration issues or the import process was interrupted. For example, if the configuration for locking and releasing imported files is not properly configured, the new content is not checked in properly after the import.

IXIASOFT CCMS can sometimes detect these errors and try to roll back the import by deleting the imported content. However, this rollback might not completely reverse the import. There is no guarantee IXIASOFT CCMS can return the docbase to its initial state. If the connection is lost during the import process, IXIASOFT CCMS might fail to import the content and then also fail when rolling back the import.

In some cases, IXIASOFT CCMS might not detect any errors. Users might only find the full scope of the errors later.

Errors adding the imported content to branches

Errors in this phase often happen because the server runs out of memory while associating the content with the DRM branches that users select. At this phase in the import process, error messages that identify issues do not appear. Instead, users might encounter the following issues:

  • Objects without a primary version
  • Containerref elements in the wrong place