Page History
...
The best practice is to simply rescan re-scan failed databases several times. Therefore:
- Click on the Status column to display its column/filter options
- Select the Filter tab
- Deselect OK so that only FAILED databases will be displayed
- Make sure that Filtered results is selected in the Re-scan Database Designs field and click on Start
| Note |
|---|
Re-scanning databases is a multistep process, that will take up to 2 days before the newly re-scanned databases will appear in the interface. Do not re-scan all databases unless absolutely necessary as it may run over several days and put significant strain on the appliance and infrastructure. In some cases several re-scans might be required. |
You can make use of further filter options in this view to restrict the re-scan scope further down to DXL Exporter crashes.
Further Issues
Insufficient access rights are another frequent reason for the iDNA Applications Design Collection to fail. To troubleshoot these issues the access rights of the corresponding database or server has to be adapted for the ID that is used by iDNA Applications.
Bad or hidden database design (often with third party tools) will also cause failures in Design Collection. With tools like Noteman or Ytria scanEZ one can usually locate these design documents and figure out what may be wrong with them. On the following websites you can search for for the details on the error codes that are shown in the Collection grid: http://www.codestore.net/errors.nsf/all/ https://invorx.com/lotus-notes-error-messages/
Sometimes iDNA Applications appliance cannot reach the server where the database resides due to network issues. In these cases a simple re-scan of the affected databases can fix the issue.
If you are not able to troubleshoot your database design issues with the means described in this article, please consult support.panagenda.com.