| Previous | Next |
| FSRM_E_TEXTREADER_STREAM_ERROR | FSRM_E_INCOMPATIBLE_FORMAT |
FSRM_E_TEXTREADER_FILENAME_TOO_LONG
FSRM_E_TEXTREADER_FILENAME_TOO_LONG specifically concerns the filename extension used to select a text filter. It should not automatically be diagnosed as the general Windows maximum-path problem.
Inspect the final name component and extension
- Record the exact filename after normalization and identify the substring treated as the extension.
- Check for generated names with unbounded suffixes, malformed temporary files, or dots embedded in identifiers.
- Exclude the pattern or rename the file according to application policy before rerunning content classification.
The content reader uses file-type registration to locate an IFilter, so an abnormal extension can fail before a handler is selected. Enabling long-path support does not make an arbitrarily long extension a registered document type. Preserve the original name when it has application meaning, and use metadata-based classification if renaming is not permitted.
Understanding IFilter handlers · Registering filter handlers · Classification management
Looking for a different code? Search another status or error code.