Skip to main content
Troubleshooting eDiscovery Download Client errors
Updated over a year ago

This topic lists the errors that you may encounter while downloading data using the eDiscovery Download Client along with their reason and resolution.

EDISCOVERY_100

Reason: TheeDiscovery Download Client was unable to complete the requested operation.

Resolution: These errors are often temporary and should auto-resolve in some time. If the error still persists, contact Support.

EDISCOVERY_101

Reason: An internal process of the eDiscovery Download Client failed to load the requested data.

Resolution: These errors are often temporary and should auto-resolve in some time. If the error still persists, contact Support.

EDISCOVERY_102

Reason: The client was unable to connect to inSync Cloud.

Resolution: The client will automatically retry the operation. But if the error continues to persist, contact Support.

EDISCOVERY_103

Reason: The client was unable to connect to inSync Cloud due to an error in the proxy settings.

Resolution: Open the eDiscovery Download Client and check if the proxy settings are as expected.

EDISCOVERY_104

Reason: There was an issue while downloading data from inSync Cloud.

Resolution: These errors are often temporary and should auto-resolve in some time. If the error still persists, contact Support.

EDISCOVERY_105

Reason: Invalid download location path.

Resolution: Go to Legal Hold > eDiscovery DownloadClients, search for the client, and check if there is an error in the download path.

EDISCOVERY_106

Reason: The client was unable to download the data due to insufficient permissions.

Resolution: Make sure that the download location is valid and accessible. This error often occurs when you try to download data to an external drive.

EDISCOVERY_107

Reason: Download failed due to insufficient storage on the device.

Resolution: Ensure that you have enough free space on your device to download all the required data.

EDISCOVERY_108

Reason: Job failed due to multiple concurrent errors.

Resolution: Go to the download job folder and check the error logs. You should be able to identify the issue and resolve it. For any assistance in debugging the issue, contact Support.

EDISCOVERY_109

Reason: The eDiscovery Download Client was unable to connect to inSync Cloud due to an authorization error.

Resolution: Check if the client is open on the device. If yes, then close the client and relaunch it. If the error still persists, contact Support.

EDISCOVERY_110

Reason: Either one or multiple files failed the integrity check.

Resolution: Contact Support.

EDISCOVERY_111

Reason: The job failed as the Zip file was deleted before the download job was complete.

Resolution: Click Retry Job to initiate the download from start.

EDISCOVERY_112

Reason: The job failed as the Zip file was modified while the download was in progress.

Resolution: Click Retry Job to initiate the download from start.

EDISCOVERY_113

Reason: Unable to zip all the downloaded files.

Resolution: Click Retry Job. If the error still persists, contact Support.

EDISCOVERY_300

Reason: Network failure while connecting to inSync Cloud.

Resolution: Ensure that the device is connected to the internet and the connection is not dropping intermittently.

EDISCOVERY_301

Reason: The activation token did not match.

Resolution: Verify the activation token and try again.

EDISCOVERY_302

Reason: A client with the same name already exists.

Resolution: Use a different name for the client. This error can also occur if you have made any hardware upgrades to your device, or have upgraded the operating system.

EDISCOVERY_500

Reason: The eDiscovery Download Client was unable to connect to inSync Cloud or internal error occurred at server side.

Resolution: Ensure that the eDiscovery Download Client is in a connected state. Open the client, and see if there is a green tick on the client UI. If the error persists, contact support.

EDISCOVERY_501

Reason: inSync Cloud could not find any client with the said name and details.

Resolution: Check if the client is still installed on the device. If not, reinstall the client and trigger a new job.

Did this answer your question?