Home CMS Documentation Home CMS 10 DITA Processing Pipeline Troubleshooting DITA Collections DITA Publishing Issues DITA Publish Log Errors

DITA Publish Log Entries Flag Errors

Condition

When users execute a DITA-OT publish on a DITA asset collection, the system generates DITA publish log entry errors.

In some scenarios, the DITA logs contain errors but the Has Errors column doesn't flag those errors in the Post Processing Status Console dialog within the Logs tab.

***Troubleshooting DITA Publish Errors***

Cause

A spectrum of issues can cause the DITA-OT transformation process to generate DITA publish log entry errors. These issues can vary depending on factors involved. Keep in mind that these steps provide general guidelines and direction for pinpointing and resolving a wide range of issues that may cause DITA log entry errors.

Important

The Has Errors column only indicates conflicts when the DITA-OT transformation process encounters a fatal error that halts the entire process. If the Has Errors column indicates no conflicts, the log may still contain errors and warnings that did not halt the DITA-OT process.

Error Issue Diagnosis

Administrators can double-check the DITA publishing pipeline setup and run debug mode. Users with asset editing and publishing permissions can execute DITA publishes, and review log and temp entries.

Identify the issue that causes the DITA publish log errors.

To diagnose the issue:

Double-check your DITA publishing setup.
Ensure the appropriate settings were in place when the system executed the DITA publish.
See the DITA Publishing Pipeline Troubleshoot Checklist to double check your DITA administration settings and DITA publishing settings.
Run debug mode to include debugging details in the next DITA publish log.
See Running DITA Debug Mode for details.
Check the DITA log to see if you run into the same previously experienced errors.
These errors may provide details about where the conflict resides and what the conflict entails.
See Checking DITA Publish Logs for Errors for details.
Check the CMS publishing log for errors and to review the asset files included within the DITA publish post processing.
See Running the DITA-OT Locally Outside the CMS for details.
Check the DITA output directory to review the output file results within the CMS site directory.
See Checking DITA Publishing Output Directory for details.
Note
If the DITA logs indicate the DITA-OT transformation process failed in the Has Errors column, then skip this step.
Review the DITA temp folder for discrepancies within the temporary files that may relate to the issue.
See Checking DITA Temp Folders for details.
Interpret the log entry errors to determine what the conflicts entail.
See Interpreting DITA Log Errors for details.

Address Error Issues

Administrators can modify the DITA publishing pipeline setup and settings related to the DITA-OT. Users with asset editing permissions can resolve conflicts with DITA asset content and their dependencies, and they can modify settings applied at DITA publish time.

Use the information you gathered from troubleshooting to resolve DITA log entry errors.

The following list provides potential solutions to address your issue. Keep in mind that you may uncover alternative solutions not provided in this list.

If your issue relates to the DITA publishing setup, then adjust your setup settings as needed.
If your issue relates to a dependency error, where you can resolve the issue by restoring a missing file or by modifying the dependency reference in your DITA asset content, then apply fixes to the affected DITA assets as needed.
If your issue relates to a DITA specification validation error, where you can resolve the issue by making changes to your DITA asset content, then check out the affected DITA assets and apply fixes as needed.
If your issue relates to DITA-OT output formats, where you can resolve the issue by changing the output format, then do one of the following:
- Choose another output format provided by the standard DITA-OT that resolves the issue.
- Provide your own custom output format plugin that resolves the issue.
If your issue relates to DITA-OT parameters, where you can resolve the issue by changing parameter settings, then modify parameters for the CMS DITA-OT as needed.
If your issue relates to the DITA-OT version, then do one of the following:
- Install a different DITA-OT version that better suits your organization's needs than the currently installed version.
- Install a custom DITA-OT engine that suits your organization's needs.
- If your issue is an unresolved DITA-OT bug, report the issue via GitHub: DITA-OT Issues.
If your issue relates to something else, or if the solutions above do not suffice, then contact Ingeniux Support.

After implementing your solution, republish the DITA asset collection, and then review the DITA logs to see if the output DITA logs contain errors. If you still encounter issues, try another solution, or contact Ingeniux Support.

DITA Publish Log Entries Flag Errors

Table of Contents Release Notes Search

Table of Contents