Discovery of all the subSources failed during a load file import

Article: 100009450
Last Published: 2018-12-11
Ratings: 0 0
Product(s): eDiscovery Platform

Problem

Load file import using an exported load file from an external package may error under certain circumstances.

When Clearwell imports from a CSV/DAT Load File it gives the option to select one of many Load Files from the source directory via the "Now Viewing:" drop down menu. While this drop down does allow only one Load File to be viewed within the Clearwell interface, it does not mean that this is the only Load File that will be discovered/processed. Clearwell will discover/process any and all Load Files found in the chosen "Top level source directory:". However only the selected "Load file type:" will be discovered/processed (Only multiple CSVs or DATs can be discovered/processed at the same time).

Error Message

Error #80000 Common Services Error : Discovery of all the subSources failed

[#560202] Reason: Duplicate entry 'Load File DOCID' for key 'DOCID'

Cause

Scenario 1:

This error can be caused by the filename field or other fields in the load file containing the text qualifier character in the field or filename. This is caused by an export package not adding an escape character to the text qualifiers contained within fields.

Scenario 2:

This error can be caused by duplicate entries in the load file, which produces an error in the case log (<case-name>-remotejob.log):
ERROR [esa.imports.ParallelLoadFileDiscoveryIterator$LoadFileDocumentDiscoverer] (LoadFileDocumentDiscovererThread_1:) CaseName:[case-name] [#560202] Reason: Duplicate entry '[BegDoc#]' for key 'DOCID'

Case log path on Clearwell server: \CW\v7xx\data\esadb\case-logs\<case-name>\<case-name>-remotejob.log

Scenario 3:

This issue occurs when the directory that contains the Load File, being discovered/processed, contains multiple copies/versions of the same Load File.

Solution

Scenario 1:

Either add escape characters into the loadfile, or replace text qualifier characters and rename filenames if acceptable.

Scenario 2:

Load file provided would need to be corrected and duplicate entries removed.

Note * If EDP created the load file, the Duplicate entry for key DOCID error could be cause by the export option "One row per custodian". This results in multiple rows in the export-generated CSV file with the same DocID value. This causes a problem when the CSV file is used in a load file import and the DocID field is being used as the unique document identifier field.

Scenario 3:

Go to the directory where the Load File being discovered/processed is located and remove all copies/versions except for the one that is to be discovered/processed and then re-run the discovery/processing.

 

 

Was this content helpful?