DLP EDM profiling is failing to index a source document with Error: Data file could not be read.

Products

• Data Loss Prevention Enforce

Issue/Introduction

When you attempt to profile an index you are getting an failure or an error. Error: Data file could not be read (Creating Index Version: xxx)

Resolution

1. In your EDM profile you MUST select the same encoding as the source file. Using ISO-8859-1 (Latin-1) is not the same as UTF-8. Instructions are documented in your DLP Admin guide. Selecting the wrong encoding could result in a failed detection.
 
2. Each time you update a EDM Profile you must either:

(i). Upload the new source file
or
(ii). Copy the source file to the \SymantecDLP\Protect\datafiles folder and select the file from the drop down menu "Reference Data Source on Manager Host".
 
3. Do not use the "Use This File Name" for a recurring or scheduled index, this option is only meant to be used as a place holder when you create a EDM profile initially. It is only meant to be used once.
 
4. It is up to you to make sure the source data is replaced after each index schedule has completed. You can either manually copy before each run of the EDM schedule or automate the process of copying the source data from its source location to the \SymantecDLP\Protect\datafiles folder and ensuring that you have selected "Reference Data Source on Manager Host".