An unknown file type or a file with a custom extension is failing text extraction
In some cases internal files may have the wrong extension, but are a known and supported content type. If that happens, use the following steps to map the custom extension to a known Content Type so text extraction can succeed.
- Navigate to the Config section of the Administration Interface
- Expand Text Processing
- Select Content Type Extension Mappings
- Create a new entry, mapping the extension (such as
".rpt") to the correct content type (such asHTML) - Restart the Collector service
- Re-process any affected files