Diagnosing a Failed Export:
Once the Finish option has been selected, the export will complete, and it will display the link to download a zip file. This zip file will contain the files necessary to assist with diagnosing the failure.
Among other files, the zip file will contain:
•summary.xml
•recoverable_urn.xml
If the Retry option was selected more than once, there will be multiple versions of the above files (e.g., summary_1.xml, recoverable_urn_1.xml).
To troubleshoot the documents that failed to export:
• Loose files
Verify access to the document from its source location. If it is there, check permissions and confirm the access to the file.
Check the server.log under System > Logs > View Logs tab for error messages surrounding the file(s) being retrieved.
• Documents from a PST file
Warning: Before continuing, verify the source location is not being accessed from any other window (for example, Windows Explorer). Then, try restarting the EsaPstRetrieverService on the appliance. After the restart, re-run the search and see if the document is retrievable.
• Documents from an NSF file
Warning: Before continuing, verify the source location is not being accessed from any other window (for example, Windows Explorer). Then, try restarting the EsaNsfRetrieverService on the appliance. After the restart, re-run the search and see if the document is retrievable.
4. If you are still unable to determine why the files did not export, please contact eDiscovery Support.
• Supply the latest summary.xml and recoverable_urn.xml files.
• Upload the Clearwell logs under System> Logs > Send Logs to Clearwell tab, and indicate the name of the eDiscovery case that had the failed export.