Page History
| Table of Contents |
|---|
Overview
iDNA Applications collects design data in order to surface insights and complexity about the various applications in your environment. To determine if there are issues with design collections either
...
Security and network issues should be relatively easy to solve. After troubleshooting, the databases need to be re-scanned manually using the re-scan options on the same page.
Troubleshooting DXL Exporter Issues
Sometimes, failures are caused by the DXL Exporter task that runs on the IBM/HCL Domino Server. iDNA depends on this separate task to gather design information from databases. It is not uncommon for the DXL Exporter to have problems with what it considers corrupt data in design elements.
Clean Abort
Normally that results in a clean abort of the scan on Domino side with an Error message like this:
...
Inconsistencies like that can usually be fixed by opening up the database in question and navigating to the document identified by its note ID in the XML (e.g. 0x57A in the error message above) and simply re-saving it. To find a document by note ID, several 3rd party development tools are available (e.g. Noteman by MartinScott).
DXL Crash
More severe issues during DXL export will lead to a crash of the DXL exporter. Even though it's not caused by iDNA, but the interaction between the DXL task and the Notes database, iDNA helps buffering the impact of such a crash with its multi-process scan architecture based on Docker.
In such a case, an error message would show up in the column "System Status" and provides additional information to the problem. Database compact and fixup with recovery options are recommended to approach solving these issues. If the problem persists, opening a PMR with HCL might be requried.
Initiating a Re-Scan
The best practice is to simply re-scan failed databases. Therefore:
...
You can make use of further filter options in this view to restrict the re-scan scope further down to DXL Exporter crashes.
Troubleshooting Other Issues
Insufficient access rights are another frequent reason for the iDNA Applications Design Collection to fail. To troubleshoot these kinds of issues, the access rights of the corresponding databases or servers have to be adapted for the ID that is used by iDNA Applications.
...