Reprocessing Failed Items

•Password protected compound document

The compound document will be copied to the reprocess folder ($Repository\$Files) for reprocessing.

•Password protected archive

The archive document will be copied to the reprocess folder for reprocessing.

•Archive contains password protected document with “Treat archive as attachment container” option selected

The parent archive is logged into Law successfully

The password protected document will be copied to the reprocess folder for reprocessing.

•Archive contains password protected document without “Treat archive as attachment container” option

The parent archive is not logged into Law
The password protected document will be copied to the reprocess folder for reprocessing.

•Archive embedded with password protected archive with “Treat archive as attachment container” and “Include embedded archive” options
The parent archive is logged into Law successfully.
The embedded password protected archive will be copied to the reprocess folder for reprocessing.

•Archive embedded with password protected archive with “Treat archive as attachment container” option and without “Include embedded archive” option

Only the parent archive is logged into Law successfully.

•Password protected archive embedded with another archive with “Treat archive as attachment container” and “Include embedded archive” options

The password protected archive will be copied to the reprocess folder for reprocessing.

•Archive embedded within email item.

The parent archive and email item is imported into law successfully.

The password protected document will be copied to the reprocess folder for reprocessing.

•Emails with password protected attachments

The parent document (Email) is processed successfully.
The password protected attachment(s) will be placed into the reprocess folder for reprocessing.

You can determine if reprocessing is needed by either checking your prior ED Loader Session Logs for processing errors/warnings or select the Failed Items tab.

1.Review the Session Log by opening the Session Viewer. For more information on the Session Viewer, see: Session Browser and Session Viewer.

•Look for records listed in the Incomplete or Commit tabs.

•If records are listed in either of these tabs, they were not imported.

•Records appearing in the Incomplete tab might be able to be resolved by resuming the ED Loader session. If this does not work, try reprocessing the files.

•Records appearing in the Commit tabs will need to be re-processed.

•The Insert feature may be used if maintaining order is necessary.

2.Review the ErrorMsg field in the CloudNine™ LAW case database to identify errors and determine what action will take place to resolve the error

•Once the Failed Items tab has been selected then LAW will search the “$Repository” in the case directory for native files that are copied to "$Repository \$Files", and the metadata information is copied to the "$Repository \$Metadata" folder.

•If there are no records in either folder then you will get the prompt "Failed item repository not found."

•After selecting OK, LAW Electronic Discovery Loader will have Failed Items grayed out.

•If there are records to be processed then LAW will scan the $Repository for mailstores.

•If no mail stores are present then following is displayed.

After selecting OK, LAW Electronic Discovery Loader displays $Files to be processed and the Source Path to the files in $Repository.

Browse to the case folder/$Repository folder. The native files are copied to $Repository \$Files, and the metadata information is copied to the $Repository \$Metadata folder.

Open the $Files folder. All files will be listed with a unique identifier that corresponds to the metadata referenced in the $Metadata folder. Opening the file in the $Metadata folder in Notepad will provide the following metadata values:  FolderPath, EntryID, SourceID, LawPath, EMailClient, ConversationIndex, ThreadID, ItemGUID, ReprocessedCount, ParentID, SourceFolderPath, SourceFileName, and FileName. The following example has two Windows Explorer windows ($Files and $Metadata) and a $Metadata file open in Notepad.

The $Metadata file can be used to locate the FileName that matches the corresponding unique identifier in the $Files folder.

1.Open the record in $Files using the correct password.

2.Change the security settings disabling the need for a password.

3.Then save the record into the same $Files folder and with the original unique identifier as the filename.

For records that fail due to processing errors or metadata extraction errors, confirm that your Windows login has read/write permission to the case folder and all subfolders and files, %Temp%, and %appdata%. Ensure that there isn't another program that is trying to access your source files during import.

If metadata extraction errors caused a record not to import then you may want to turn off metadata options during import and process post import by Extracting Custom Metadata

Select Failed Items in LAW Electronic Discovery Loader.

Change any import settings that need to be altered and select Start.

The Failed Items that have been resolved will now be imported into the database in the corresponding folder with the rest of the files from that source.

If the item is re-processed successfully, then the backed up file and its metadata info will be deleted from the “$Repository” folder.

If the item was an attachment, then the Parent document id will be added to the ErrorMsg field. This can be used to manually attach the item back to its parent.