The DITA connector has the following error codes:
- The format
{value}indicates a placeholder. - Get in touch with a Fluid Topics representative for additional assistance about an error.
| Error code | Error message | Fix |
|---|---|---|
DITA-0001 |
{error} |
An xml:lang value is invalid. Review the content, and publish again. |
DITA-0002 |
Attachments list contains duplicate entry for {attachment_filename}. |
Review the DITA map's attachments, and publish again. |
DITA-0003 |
No title found for topic id "{topic_id}" (path : {path}) |
Review the topic, and publish again. |
DITA-0004 |
Ditaval parsing error "{ditaval}": {error} |
Review the DITA map's DITAVAL elements, and publish again. |
DITA-0005 |
Invalid dita-ot "{dita_ot_path_name}" archive |
The custom DITA-OT is invalid. Back up the custom DITA-OT, and reset to the default DITA-OT from the Sources menu. Try publishing again, and if the upload works, run the custom DITA-OT locally to diagnose issues. |
DITA-0006 |
Dita-OT is writting more than 100MB of logs. Please review it to avoid this amount of logs |
Download the logs, and try to diagnose the issue found by the DITA-OT. The DITA-OT may be running on a loop, and creating the same logs. |
DITA-0007 |
The file "{filepath}" generated by dita-ot is empty. Please check dita-ot report. |
Review the DITA-OT report, back up the custom DITA-OT, and reset to the default DITA-OT from the Sources menu. Try publishing again, and if the upload works, run the custom DITA-OT locally to diagnose issues. |
DITA-0008 |
Found no top maps or control file, was it intended? |
DITA archives must have a top map (a map without a parent map), or a control file at the root of the archive. |
DITA-0009 |
Failed to parse file identified as a ditamap: {ditamap} is xml invalid Stopping to prevent unintentional publish of non-top ditamap Ditamap error: {error} |
Review the DITA map's syntax using an XML editor, and publish again. |
DITA-0010 |
Invalid metadata in {map}: {error} |
Review the map's metadata, and publish again. |
DITA-0011 |
Invalid metadata in {topic}: {error} |
Review the topic's metadata, and publish again. |
DITA-0012 |
Original ditamap file is missing. If you're using a custom DITA-OT, make sure temporary files are preserved after processing |
If using a custom DITA-OT, back up the custom DITA-OT, and reset to the default DITA-OT from the Sources menu. Try publishing again, and if the upload works, run the custom DITA-OT locally to diagnose issues. |
DITA-0013 |
A resource has neither originId nor filepath nor instance |
The control file requires either the use of the <filePath>, <originId>, or <instance> element. Edit the control file, and publish again. |
DITA-0014 |
The resource with {origin_id} as originId cannot contain an originId and an instance |
Review the control file to use either <originId> or <instance>, and publish again. |
DITA-0015 |
The resource filepath is mandatory when an instance does not contain an originId |
The control file requires either the use of the <filePath>, <originId>, or <instance> element. Edit the control file, and publish again. |
DITA-0016 |
A instance has neither filepath nor originId |
The control file requires either the use of the <filePath>, <originId>, or <instance> element. Edit the control file, and publish again. |
DITA-0017 |
A resource with an originId ("{origin_id_value}") cannot be associated with ditamap containing ditaval ("{ditaval}"). |
|
DITA-0018 |
Original ditamap file is not in the tmp directory. |
The DITA-OT writes intermediate files generated during the transformation process to a temporary folder. Back up the custom DITA-OT, and reset to the default DITA-OT from the Sources menu. Try publishing again, and if the upload works, run the custom DITA-OT locally to diagnose issues. |