Fix DITA post-processing failures from B-tree index errors in AEM Guides
Post-processing of DITA and DITAMAP files in Adobe Experience Manager (AEM) Guides can fail because of inconsistencies in the B-tree reference index, often after you delete and re-upload content in the DAM. To resolve the issue, upload and extract the content into a new location in the DAM.
Description description
Environment
Adobe Experience Manager (AEM) Guides
Symptoms
Post-processing failures can occur in AEM Guides when working with DITA and DITAMAP files that have been deleted and re-ingested into the DAM. This issue is typically seen when the expected properties are missing from the jcr:content node of affected files, and repeated attempts to open or save these files trigger the same error.
The problem is often linked to the method used to delete the content, especially if deletion was performed outside the standard AEM user interface, which can leave the B-tree reference index in an inconsistent state. As a result, post-processing cannot complete successfully, and the files remain in an error state.
Resolution resolution
Follow these steps to resolve the issue.
-
Delete the affected ZIP file and all extracted content from the DAM.
-
Upload and extract the ZIP file into a new folder or a different path in the DAM (do not reuse the original folder).
-
After extraction, verify that post-processing completes successfully for the files in the new location.
-
(Optional) Use the following endpoints to check and attempt to repair the B-tree reference index:
- GET
/bin/fmdita/validatebtree?operation=validate(reports broken content references) - GET
/bin/fmdita/validatebtree?operation=patch(attempts to patch broken references)
Note: These operations may provide diagnostic information but may not always resolve the issue.
- GET
-
Confirm that content deletions are performed using the AEM user interface, not directly through CRX/DE, to avoid index inconsistencies in the future.
-
If the issue persists after following these steps, gather complete error logs covering the upload and extraction process, and contact Adobe Support for further assistance.
To verify resolution, check that post-processing completes without errors and that the expected properties are present on the jcr:content node of the ingested files.