Page History
...
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). More details on fixing the issue can be found in the following document:
| View file | ||||
|---|---|---|---|---|
|
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 requriedrequired.
Initiating a Re-Scan
The best practice is to simply re-scan failed databases. Therefore:
...
Bad or hidden database design (often with third-party tools) will also cause failures in Design Collection. With tools like Noteman or , Ytria scanEZ or HCL Notespeek one can usually locate these design documents and determine what may be wrong with them. On the following websites you can search for details on the error codes that are shown in the Collection grid:
...