View Exception Details for all Imports or a Data Set

Imports > Reports > Exception Details

Selected Data Set > Reports > Exception Details

Requires Imports - View Permissions and Project - Reports - View Permissions Permissions

While viewing the Reports tab for Imports, or the Reports tab for a given Data Set, you can click Exception Details to get more information about the reported Import exceptions. For the Imports Reports tab, this include exceptions reported for all of the Imports (that is, all Data Sets) in the Project. For a Data Set Reports tab, which includes a Scan Report Summary for a given Data Set, this includes the exceptions reported for that Data Set during Import.

Note: From Project Data, the Scan Data and Scan Details information is for all Imports (that is, all Imported Data). Imports can be performed by a user with permissions, such as an Organization Administrator. Keep in mind that not all of the imported data may have been added by the administrator to the Project Data, so the counts displayed may not match the counts shown in the Scan Report Summary and Details. Also, Exclusion Searches will have typically removed items such as Directories, Archives, and NIST files when documents were added to Project Data, and the Scan Report Summary identifies items such as Directories.

Exception Details

The Exception Details popup provides a list of exceptions, with the fields described in the following. Exceptions may include one or more files that have an unknown type but could still be added (file MD5 hash codes could be generated for them). The list may also include one or more files associated with a scan-related Error that prevents them from being added. You can also view errors by checking the parsingstatus metadata field, which contains a 5-digit error code and reason (for example, 00009 FILE_READ).

  • Doc Number – A three-part number representing the Document Number of the file in the format C.V.N, where C = a Data Collection (Data Set) number, unique per Organization, V = a Data Collection Checkpoint Value, unique per Data Collection, and N = a document number, unique within the Data Collection Checkpoint.
  • Import Path – The path to the file.
  • Code – The error code associated with the error. This is the parsingstatus code, padded.
  • Reason – The reason for the error, in the format reported by parsingstatus. This column is populated only for Data Set files that have exceptions. You can use the column filter to select a single reason in the drop-down and filter the list for that reason.
  • auxparsingstatus – A Warning for the file in the format reported by the auxparsingstatus field. You can use the column filter to select a single value in the drop-down and filter for that value. For example, for the email parent of a Modern Attachment, this field identifies modern_attachment_retrieve_warning when a Modern Attachment could not be retrieved during processing. For an archive file that has been successfully processed by unzip instead of 7zip, this field reports unzip_fallback_processed, and for a records extracted from an archive processed by unzip, this field reports unzip_fallback_extracted.
  • File Type – The official file type for the exception file. You can use the column filter to select a single value in the drop-down and filter for that value. See Supported File Types for Analysis for a list of possible file types based on Parsing Library (V2 is the library currently supported). When you have filtered the Reason or auxparsingstatus column for a specific value, the File Type filter drop-down includes only the values available in the filtered set of documents.
  • Size – The size of the file.
  • Date Processed – The date on which the file was processed. This is a time stamp based on the local system (Services Node) time.

Download an Exception Report or Document

You can perform download of the following:

  • For a selected file, you can click the icon (located to the far right) to download a document locally and view it using its native application.
  • For the current list of exceptions, you can click on the bottom toolbar to download the list to a CSV file (ScanReport.csv). If you have filtered the contents of the list, the download will uphold that filtering. The download file includes the columns shown in the Exception Details list (for example, Doc Number) and shows the Reason in the same format as the Warnings and Errors Summary (that is, with descriptive text instead of the official parsingstatus format in all caps). The Code column shows the error code without padding.

Warnings and Errors: Codes and Reasons

The following table identifies the list of supported Warnings and Errors. This table applies to Warnings and Errors reported in the parsingstatus metadata field and origparsingstatus metadata field. Each entry shows the Display Name shown in the Warnings and Errors summary, a description, the searchable Code/Reason, and the Type (Warning or Error).

An Auxiliary Warning, which applies to the auxparsingstatus metadata field, is listed in a separate table. OCR errors are listed in their own table as well.

This table does not include Success (code 00000, which identifies documents that were parsed successfully. Note that Success includes all populated or empty directories found on disk. (Directories that cannot be accessed are reported by 01011 DIRECTORY_ACCESS_ERROR.)

Note: If you are searching a given view for error information using the parsingstatus, origparsingstatus, or ocrstatus field (for example, parsingstatus::00005), note that the codes are 5 digits, and the reasons are not case-sensitive. You can search for the code, the text, or both in the field (since the fields make each term searchable).

After reviewing the Warnings and Errors, you may need to take additional steps to address problem files (for example, damaged, encrypted, or password-protected files). For example, you may need to configure password-cracking options and supply password files, repair a PST, decrypt an NSF file, or address a protected ZIP file. If files such as damaged files can be fixed or addressed, you can have them reprocessed from their original import location, or you can copy them to an export area to be externally reprocessed. You drill-through entries in the report, such as Damaged, Encrypted, Protected, or Archive Extraction Error, and, from the drill-through Search results, select files or all files and use the Reprocess option or, for external reprocessing, the Copy to External Area option.

 

Display Name for Warning/Error Description Searchable Code/Reason (parsingstatus field content) Type (Warning or Error)
Processing Failure An unknown failure prevented processing of the file.

You can attempt to reprocess, but the error may recur. Check the filetype, importpath, and size fields for more information that may help you decide next steps, if warranted. 		00001 FAILURE Error
No Data The file has no valid data (that is, no terms that are considered acceptable). It may have terms that do not meet the minimum or maximum term length, or that are on the Stop Words List.

Note that for a file with no content, the contentmd5 will be set to the filemd5.

The file may benefit from OCR processing, but reprocessing will not yield additional information.		 00005 NODATA Warning
Read Error The read operation on the file failed.

In many situations, you can try reprocessing, and if that fails, attempt to work with the file in question. Note that with Parsing Library V2, you will see this status for Microsoft PowerPoint 3.0 and 4.0 files (which are ID only). For these files, reprocessing will have no effect.		 00009 FILE_READ Error
Conversion Error The contents of the file could not be converted to the correct format during processing.

If you see this error, please contact Digital Reef Customer Support.		 00012 ICU_CONV_ERROR Error
Empty Email The email has no content, or the email body may be damaged or invalid.

You may see this error if the email has only attached photos or its subject line contains the message. A small number of these errors may be considered expected and not of concern. 		00015 NO_EMAIL_BODY Error
Open Error The file could not be opened or processed due to an unknown error. If this is a Lotus Notes NSF file (for Lotus Notes), the file may not be a valid NSF file.

Try reprocessing, and if that fails, attempt to work with the file in question.		 00016 FILE_OPEN Error
Zero-Length File The file has zero bytes of content.

A small number of these errors may be considered expected and not of concern.		 00017 FILE_ZERO_LENGTH Error
Unknown File Type The software could not determine the document type for this file.

Examine the filetype and docext fields. You can try reprocessing, but the results may not be optimal and you may see the Partial Text Extraction warning. 		00019 FILE_TYPE_UNDETERMINISTIC Error
Unsupported File Type For documents that were processed with Parsing Library V1 only, this parsing status indicated that the software was able to identify the file type, but the file type is not supported for full parsing.

Examine the filetype and docext fields. Reprocessing is not useful for files with this status. 		00021 FILE_NOT_SUPPORTED Error
System Error The system encountered an error.

Try reprocessing, and if that fails, attempt to work with the file in question. 		00024 SYSTEM_ERROR Error
Processing Halted The software had to halt document processing due to an error.

You can attempt to reprocess, but the error may recur. Check the filetype, importpath, and size fields for more information that may help you decide next steps, if warranted.		 00025 PROCESS_ERROR Error
Processing Timeout Processing of the file exceeded the timeout value.

Try reprocessing, and if that fails, attempt to work with the file in question.		 00026 TIMEOUT Error
Encrypted The file cannot be processed because it is encrypted. In general, this error applies to attachments extracted from Lotus Notes NSF files. It also applies to Zip/ZipX containers and disk partitions (for example, BitLocker-encrypted partitions from an LEF).

You need to obtain a password for the encrypted file. 		00027 ENCRYPTED Error
Damaged In many cases, indicates that the file cannot be processed because it is damaged in some way. EnCase files, including Logical Evidence Files, are considered Damaged when there is a mismatch between the stored and calculated cyclic redundancy check (CRC). This status can also be reported for a PST that is damaged or has invalid properties from which the contents can still be extracted.

You can try to work with the file in question, but no other action is useful in eDiscovery for this error.		 00028 FILE_DAMAGED Error
Protected The file cannot be processed because it is password-protected. If this is a protected Lotus Notes NSF file, a Lotus Notes key is required to open the file. This error may be reported for file types such as Microsoft Word or Adobe Acrobat PDF, but not for encrypted NSF attachments, mail containers other than NSF, archives, disk images, text files, EMLs, HTMLs, or vcalendar items.

You need to obtain a password for the password-protected file.		 00029 PROTECTED Error
Parsing Error Some formatting of content in the file generated a parsing error (for example, incorrectly formatted archives).

You can attempt to reprocess, but the error may recur. Check the filetype (to see if it is a common type and supported), as well as the importpath and size fields for more information that may help you decide next steps, if warranted.		 00031 PARSER_LIB_ERROR Error
Permission Error File permissions prevented the file from being processed.

If you see this error, please contact Digital Reef Customer Support for guidance.		 00037 PERMISSION_ERROR Error
File Not Found The file could not be found at its import location. It may have been moved or deleted.

During processing of an email archive (for example, a PST), this error may be reported for an email that is either corrupt or missing from the archive.

This status can also be reported during processing of a disk image (for example, an L01 Logical Evidence File) if there was a problem mounting the disk image, or if a file could not be retrieved. Failure to retrieve a file could be caused by a filename with invalid characters, such as a / (forward slash), which typically marks a directory.

For a PST, the ideal solution would be to replace the PST. If not, then try to identify the problematic email and open it in MS Outlook to verify that it produces an error.

For an L01, please contact Digital Reef Customer Support for guidance, which may involve isolating certain folders that can be extracted and processed separately. 		00038 FILE_NOT_FOUND Error
Partial Text Extraction The Strings Parser detected some text from certain files:

- After initial import of files identified as text but that include invalid characters. The Text tab of the appropriate Document Viewer displays the text.

- After reprocessing of files that are identified as Unknown files but that have some text in them. Reprocessing the Unknown files may not always yield optimal results. Although the software attempts to extract text, the text may be unusable (potentially garbage) and slow to extract.

If you see this warning with PST files, they might be partially corrupt. You may want to try reprocessing, and working with the PST in MS Outlook.		 00040 PARTIAL_TEXT_EXTRACTION Warning
Attachment Open Error The parsing library could not open this email attachment. When parsing MSGs from a PST, the parsing library checks the pr_attach_data_bin MAPI field of entries in an attachments table. If the pr_attach_data_bin field is not present for a given attachment, that attachment is marked with this error.

Reprocessing is not useful for this error. 		00041 ATTACH_OPEN Error
Attachment Save Error The parsing library could not save this email attachment. When parsing MSGs from a PST, the parsing library checks the pr_attach_data_bin MAPI field of entries in an attachments table. If the pr_attach_data_bin field is present but has a null value for a given attachment, that attachment is marked with this error.

A number of files reported with this status may indicate one of the following for an MSG attachment: 1) The attachment is actually a reference to a file on the disk of the user, 2) The binary data for the attachment is missing or of zero length, or 3) The attachment is an Archive Stub.

Reprocessing is not useful for this error. 		00042 ATTACH_SAVE Error
Unsupported Lotus Note The Lotus Notes file can be identified (for example, based on its Form type) and extracted, but is not a standard Form type. Unsupported Form types include PA, BCMemo, Bookmark, TaskNotice, PAReadOnly, PO, Archive Profile, (Message), and PartEval. This exception is also returned when the Lotus Notes Form type is Unavailable but the Digital Reef software is able to determine that the type is a Script.

This parsing status is preserved upon reprocessing, although reprocessing is generally not useful for this warning. No further action in eDiscovery is needed.

If you see this warning, it may mean that Lotus Notes was used for more than email.		 00043 UNSUPPORTED_LOTUS_NOTE Warning
Unknown Lotus Note The Lotus Notes file could not be identified (for example, based on its Form type) but it could be extracted.

This parsing status is preserved upon reprocessing, although reprocessing is generally not useful for this warning. No further action in eDiscovery is needed.

If you see this warning, it may mean that Lotus Notes was used for more than email, including custom applications.		 00044 UNKNOWN_LOTUS_NOTE Warning
Mapped Lotus Note Form The Lotus Notes Form type was Unavailable, but the Digital Reef software could derive enough information (for example, MIME content) to enable processing of the file as an EML.

This parsing status is preserved upon reprocessing, although reprocessing is generally not useful for this warning.

No further action in eDiscovery is needed.		 00045 MAPPED_LOTUS_NOTE Warning
Missing Attachment For a Bloomberg message, indicates that the message has one or more missing attachments. This occurs if an attachment resides in the XML file but not in the attachment archive.

This error may indicate an issue with the XML Bloomberg export, or potentially a file/folder name issue (for example, tar.gz archives may have the wrong doc extensions for XML).		 00046 MISSING_ATTACHMENT Error
Archive Empty Zero files were extracted from the archive (container file). This applies to containers including ZIP, TAR, RAR, 7ZIP, EWF, LEF, PST, NSF, and MBOX. This does not apply to Bloomberg containers. For mail containers, the mailcontainererror metadata field will also be populated with this error.

Examine the filetype, importpath, and size fields. Reprocessing is not generally useful.		 00047 ARCHIVE_EMPTY Error
Attachment Manifest Error For a parent file, indicates that there is an issue with an entry in the attachment manifest. This can be caused by the occurrence of special characters in an attachment filename.

Try to work with the parent email.		 00048 ATTACH_MANIFEST_ERROR Error
Nested Duplicate Archive If a parent archive (for example, a ZIP file) contains nested duplicate archives, its duplicate archives report this error to indicate that the system protected against the repeated expansion, thereby avoiding potential size limit issues.

This error is intended to protect the system. No further action is necessary. Do not reprocess documents with this parsing status. 		00049 NESTED_DUPLICATE_ARCHIVE Error
Unsupported PDF Form The software does not support Adobe Acrobat (PDF) files that are PDF Forms.

Review the files in Adobe Acrobat. No further action in eDiscovery is useful.		 00050 UNSUPPORTED_PDF_FORM Error
Invalid Transport Header The email transport header is not valid (it is either not in a standard format or lacks the minimum number of fields). A transport header must have at least three of the standard fields (for example, to, from, bcc, or cc).

When this error is reported for items in Drafts and Sent folders, it may be expected, since these do not tend to have much metadata. If you see this error for a large number of email-related items, it may indicate a broader issue.		 00051 INVALID_TRANSPORT_HEADER Error
File Type Map Failure The detected file type failed to map to a supported file type name.

If this occurs, please supply the file type information to Digital Reef Customer Support for potential patch purposes. 		00052 FILE_TYPE_MAP_FAILURE Error
Error Extracting Child This parsing status is no longer populated for newly added data (see 00062 CONTAINER_EXTRACTION_WARNING instead). Existing data may still report this parsing status to warn of a potential problem with extraction from the container file.

00053 CHILD_ARCHIVE_EXTRACTION_ERROR Error
Lotus Notes Archive Stub The software was able to process and extract some text from Lotus Notes emails with an nsfform type of ArchiveStub. This warning status alerts you to the presence of stub files.

This parsing status is preserved upon reprocessing, although reprocessing for this warning is not generally useful. 		00054 LOTUS_NOTES_ARCHIVE_STUB Warning
NSF Partial Extraction The software was only able to partially extract items from a Lotus Notes NSF.

You can try reprocessing, but this error may mean that the some of the items are corrupted. In general, you may want to try to replace the NSF. 		00056 NSF_PARTIAL_EXTRACTION Error
Third-Party Software Not Installed The third-party software required for processing is not installed on the system (for example, the UnRAR tool needed to process certain encrypted RAR files).

If you see this error, please contact Digital Reef Customer Support for guidance.		 00057 THIRD_PARTY_SOFTWARE_NOT_INSTALLED Error
Attachment Encrypted For EMLs and ICS Calendar items from Lotus Notes NSF container files, indicates the presence of an encrypted attachment. The attachment, however, will not have this parsing status; it will have a parsing status of 00017 FILE_ZERO_LENGTH.

The parsing status is preserved upon reprocessing.

Forensic assistance may be required to perform decryption of the attachment.		 00058 ATTACH_ENCRYPTED Error
Attachment Damaged For EMLs and ICS Calendar items from Lotus Notes NSF container files, indicates the presence of a damaged attachment. The attachment, however, will not have this parsing status; it will have a parsing status of 00017 FILE_ZERO_LENGTH.

This parsing status is preserved upon reprocessing.

Unless this error is widespread, a small number of files with this error may be expected and may not warrant further action.		 00059 ATTACH_DAMAGED Error
RTF Flag Missing For MSGs that are extracted from a PST/OST and have only an RTF body but are missing the PidTagRtfInSync (0x0E1F) flag, this warning indicates that the software added the missing flag.

If this warning is widespread, it may indicate that the emails were created or converted by a non-Microsoft tool that left off the flag. Most likely, the content is not problematic, but in some cases, this could indicate a corruption issue. You may want to investigate some of the affected emails to see if there is a broader issue.		 00060 RTF_FLAG_MISSING Warning
POI Error For Microsoft Office documents processed prior to 5.2.0.0, this warning indicates that a problem in the POI third-party library prevented the software from extracting attribute information such as docannotations, hiddendata, trackchanges, and markuphistory from documents.

This warning is for informational purposes only. No action is needed, including reprocessing, which will have no effect in this situation.		 00061 POI_ERROR Warning
Container Extraction Warning For items from a container processed as of 4.3.11.0, this parsing status indicates a potential problem with extraction from the container file (for example, a PST). This warning may help flag emails that have certain issues when they are extracted and may not be perfect. This warning can also be reported if an MSG from a PST/OST contains an issue with the expected Block ID values.

This parsing status persists after reprocessing of the item.

If you see this warning reported for a large number of items from a container, examine some of the emails for signs of a broader issue.		 00062 CONTAINER_EXTRACTION_WARNING Warning
No filemd5 Generated The software was unable to generate a filemd5 for this file.

If you see this error, try reprocessing. 		00065 NO_FILEMD5_GENERATED Error
Attribute Extraction Warning For Microsoft Office documents processed as of Release 5.2.0.0, this warning indicates that the software's third-party library was unable to extract attribute information such as docannotations, hiddendata, trackchanges, and markuphistory from documents.

This warning is for informational purposes only. No action is needed, including reprocessing, which will have no effect in this situation.		 00066 ATTRIBUTE_EXTRACTION_WARNING Warning
Missing OLE Text Warning This status applies to documents processed with Parsing Library V2 as of 5.2.5.x. For parent documents with one or more embedded OLE documents, this warning indicates that the parent document is missing some text from an OLE document (that is, text was not extracted for that document).

This warning is for informational purposes only. No action is needed, including reprocessing, which will have no effect in this situation.
 00067 MISSING_OLE_TEXT_WARNING Warning
File ID only For documents processed with Parsing Library V2 only, this parsing status indicates that the software was able to identify the file type, but the file type support is limited to identification only, not full parsing.

You can examine the filetype and docext fields. Reprocessing is not useful for files with this status.
 00068 FILE_ID_ONLY Warning
Virus Detection Error An error with the Virus Detection software prevented this file from being checked for viruses.

In general, if this error occurs, it will apply to all documents imported in a Data Set. If you happen to see only individual documents receive this status, you should reprocess the entire Data Set to get a revised parsing status. Also note that if for some reason two parsing statuses end up applying to a document (this status and a non-Virus Detection parsing status), the non-Virus Detection parsing status will take precedence and the Virus Detection Error status will not appear.
 00069 VIRUS_DETECTION_ERROR Error
RTF Body Substituted For emails that are determined to have a corrupt RTF body, this warning indicates that the email body information was substituted with the PR_BODY MAPI field. Reprocessing will not improve this situation.

If this warning is widespread, it may indicate that there is a general issue with the emails in question and could indicate a corruption issue. You may want to investigate some of the affected emails to see if there is a broader issue with the data or collection.		 00071 RTF_BODY_SUBSTITUTED Warning
SMF Data Extraction Error For a Short Message Format (SMF) record, this error indicates that the record was extracted from the SMF parent (for example, a Cellebrite XML file), but some aspect of the record could not be processed as expected.

For the SMF parent, this error indicates that either an entire section could not be extracted, or that some aspect of a record prevented the record from being extracted. 		00072 SMF_DATA_EXTRACTION_ERROR Error
Excluded Archive Types This warning is reported for files that have been explicitly excluded from extraction based on their file extension. You specify file extensions that you want to exclude in the Excluded File Extensions for Extraction section of the Index Settings.

This warning is for informational purposes only. No action is needed, including reprocessing, which will have no effect in this situation.

01000 SKIPPED_FILE Warning
Special File The file is a Special File (that is, not a regular file or directory). Special Files are not subject to processing. For example, a named pipe (FIFO) is a Special File.

If you see this error, please review the source data and forensic investigation may be required. If necessary, contact Digital Reef Customer Support for guidance. 		01001 SPECIAL_FILE Error
Decompress Error A compressed file could not be decompressed (for example, a GZIP file).

Try to work with the file.		 01005 FILE_DECOMPRESS Error
Access Error The file could not be retrieved using the Connector and location associated with the import operation. Connectors and locations are defined by an Administrator as part of Organization Provisioning.

Try to investigate a possible Connector configuration issue. If the issue cannot be resolved, please contact Digital Reef Customer Support. 		01006 CONNECTOR_RETRIEVE_ERROR Error
Lotus Notes Not Installed The Lotus Notes client is not installed on the system component (Analytics Node) that tried to process the file.

If you see this error, please contact Digital Reef Customer Support.		 01008 LOTUS_NOTES_NOT_INSTALLED Error
Lotus Notes Not Licensed Either the system component does not have a valid Lotus Notes client or the license has expired.

If you see this error, please contact Digital Reef Customer Support.		 01009 LOTUS_NOTES_NOT_LICENSED Error
Archive Extraction Error Extraction of one or more files from an archive failed.

Try reprocessing, but the error may recur. Try to work with the file in question. 		01010 ARCHIVE_EXTRACTION_ERROR Error
Directory Protected Access to a directory is denied because the directory is protected.

If you see this error, please contact Digital Reef Customer Support.		 01011 DIRECTORY_ACCESS_ERROR Error
Unsupported File for Connector The Connector does not support files of this type.

Try to investigate a possible source data issue or system configuration issue. If the issue cannot be resolved, please contact Digital Reef Customer Support for guidance.
01012 CONNECTOR_OPERATION_NOT_SUPPORTED Error
Missing EWF Files One or more of the EWF segment files are missing from the set.

This error may indicate an issue with the source data and forensic investigation may be required. If necessary, contact Digital Reef Customer Support for guidance.		 01013 EWF_FILE_MISSING Error
Invalid EWF Filename The software detected an invalid EWF segment filename.

This error may indicate an issue with the source data and forensic investigation may be required. If necessary, contact Digital Reef Customer Support for guidance.		 01014 EWF_FILE_INVALID_NAME Error
EWF Error An error occurred during processing of an EWF segment file.

You can try to reprocess, but the error may recur and may indicate an issue with the source data and forensic investigation may be required. If necessary, contact Digital Reef Customer Support for guidance.		 01015 EWF_FILE_ERROR Error
No Partitions The file system type could not be determined from the raw image. When this error occurs, the diskpartitions metadata field does not exist.

This error may indicate an issue with the source data and forensic investigation may be required. If necessary, contact Digital Reef Customer Support for guidance.		 01016 NO_PARTITIONS Error
Skipped Partitions All of the discovered partitions were skipped, either because their type was known and intentionally skipped, or because their type was unknown and could not be processed. The metadata field diskpartitions provides details.

Unless some parts of the LEF image have a different parsing status, the LEF most likely extracted properly and no action is needed. The skipped partitions (e.g., the L02, L03) are from a multi-part LEF image and called skipped because they are associated with the first L01 segment. 		01017 PARTITIONS_SKIPPED Error
Partition Errors At least one partition type was supported but failed during processing. This typically occurs when a file system type is known and supported but the mount fails. Other partitions may have been processed successfully. The metadata fields ewfpartitions and diskpartitionstatus provide details.

You can try to reprocess, but the error may recur and may indicate an issue with the source data. Forensic investigation may be required. If necessary, contact Digital Reef Customer Support for guidance.		 01018 PARTITION_ERRORS Error
No Fuse Support Fuse is not completely installed (that is, the Fuse kernel module, library, or binaries are not installed).

If you see this error, please contact Digital Reef Customer Support.		 01019 FUSE_NOT_INSTALLED Error
Skipped Directory By request, the directory was skipped during processing. 01020 DIRECTORY_SKIPPED Error
Invalid Characters The filename contains invalid characters.

Examine the importpath field.
If this is from an L01, forensic investigation of the import may be required. Contact Digital Reef Customer Support for guidance.		 01021 FILE_NAME_INVALID_CHARACTERS Error
Empty Filename in Disk Image The raw disk image (for example, an L01 disk image) was fully processed (with all possible contents extracted), but it contained at least one file/folder with an empty filename, thereby preventing extraction of the files beneath that point in the path.

If you see this error, forensic investigation may be required to identify empty filenames in the disk image. If necessary, contact Digital Reef Customer Support for guidance.		 01023 DISK_IMAGE_EMPTY_FILENAME Error
Partitions Encrypted A disk partition is encrypted (for example, as a BitLocker-encrypted partition).

For a BitLocker encrypted partition, make sure that you have the appropriate key file with the 48-digit key. 		01024 PARTITIONS_ENCRYPTED Error

 

Auxiliary Parsing Status Warning

The following table identifies the current auxiliary parsing status Warning. This table is intended to apply to Warnings reported in the auxparsingstatus metadata field. The entry identifies the Display Name shown in the Warnings and Errors summary, a description, the searchable Reason, the Type (Warning or Error), and whether it supports any actions upon drill-through of the entry.

Display Name for Warning Description Searchable Reason (auxparsingstatus field content) Type (Warning or Error) Supports Actions on Drill-through
Modern Attachment Retrieve Warning For the email parent of a Modern Attachment, this warning indicates that a Modern Attachment could not be retrieved during processing, either because the Data Set was imported from a non-Office 365 Connector, or the files at the links are not retrievable with the in-use Connector's credentials. See Extract Office 365 Data for information on how you can drill-through the entry in the Warnings and Errors report and use the Extract Office 365 Data option with an available Office 365 Connector (Exchange or SharePoint). modern_attachment_retrieve_warning Warning Yes
Unzip Fallback Extracted For a record within an archive that could not be processed using 7zip, this warning indicates that the record was successfully extracted from the archive using unzip as a fallback. unzip_fallback_extracted Warning Yes
Unzip Fallback Processed For an archive that could not be processed using 7zip, this warning indicates that the archive was successfully processed using unzip as a fallback. unzip_fallback_processed Warning Yes

 

OCR Errors

The following table provides information about OCR errors for files that did not fully or successfully complete OCR processing. Error codes and reasons are reported in the parsingstatus metadata field; you can search the fields using the 5-digit value, text, or both.

If you see these errors, you can evaluate whether external OCR processing is warranted.

 

OCR Error Displayed in Summary Description Searchable Error Code/Reason
OCR Failure The OCR processing of an image file failed unexpectedly. 01200 OCR_FAILURE
OCR Initialization Failure The OCR software engine could not be initialized (for example, because it is not installed correctly). 01201 OCR_INIT_FAILED
OCR Not Licensed Either the system component does not have a valid license for the OCR software or the license has expired. 01202 OCR_NOT_LICENSED
OCR Image Load Error Indicates an OCR processing error occurred when loading an image. 01203 OCR_LOAD_IMAGE_ERROR
OCR Recognition Error Indicates an OCR processing error occurred during recognition of a page in the image file. 01204 OCR_RECOGNITION_ERROR
OCR Preprocessing Error Indicates an OCR processing error occurred during image preprocessing. 01205 OCR_PREPROCESSING_ERROR
OCR Low Confidence The OCR engine reported low confidence in the correctness of recognized text from the image. 01206 OCR_LOW_CONFIDENCE
OCR Timeout OCR processing of a page in the image file exceeded the timeout value (2 minutes). 01207 OCR_TIMEOUT
OCR Unsupported Image Type The OCR software does not consider the file a supported image file format or image file type. 01209 OCR_IMF_NOTSUP_ERR
OCR Missing TIFF Tag A required TIFF basic tag is missing. 01210 OCR_IMF_TAGMISSING_ERR
OCR Image Compression Error An error occurred in image compression. 01211 OCR_IMF_COMP_ERR
OCR Unknown Image Format The OCR software detected an unknown image format. 01212 OCR_IMF_IMGFORM_ERR
OCR File Format Error The OCR software detected a file format error. 01213 OCR_IMF_FILEFORMAT_ERR
OCR Unsupported Color File The OCR software does not support a Color PCX file. 01214 OCR_IMF_COLOR_ERR
OCR Protected Image The OCR software detected a password-protected image file. 01215 OCR_IMF_PASSWORD_WARN
OCR No Text The OCR software generated a no text warning. 01216 OCR_NO_TXT_WARN
OCR Missing Zone The OCR software could not find the OCR Zone. 01217 OCR_ZONE_NOTFOUND_ERR
OCR Insufficient Memory There was not enough memory during image processing. 01218 OCR_IMG_NOTENOUGHMEMORY_ERR
OCR Invalid Dimensions The OCR software detected invalid rectangle dimensions. 01219 OCR_IMG_RECT_ERR
OCR Unsupported Resolution The OCR software detected an unsupported resolution. The resolution of image files must be between 75 and 600 DPI. The optimum resolution for OCR is 300 DPI. 01220 OCR_IMG_DPI_ERR
OCR Missing Image The OCR software could not find the image. 01221 OCR_IMG_NOTFOUND_ERR
OCR Compressed Image Error The OCR software could not process the compressed image. 01222 OCR_IMG_COMPRESSED_ERR
OCR Bits per Pixel Error The OCR software detected an unsupported bits-per-pixel value. 01223 OCR_IMG_BITSPERPIXEL_ERR
OCR Unsupported Image Size The OCR software detected an unsupported image size. This error occurs when either the height or width of the image file is less than 16 pixels, or when either the height or width exceeds 28 inches (71cm) or 8400 pixels. 01224 OCR_IMG_SIZE_ERR