| Previous | Next |
| FSRM_E_TEXTREADER_NOT_INITIALIZED | FSRM_E_PERSIST_PROPERTIES_FAILED_ENCRYPTED |
FSRM_E_TEXTREADER_IFILTER_NOT_FOUND
FSRM_E_TEXTREADER_IFILTER_NOT_FOUND means the built-in content classifier could not locate an IFilter implementation for the file extension or document class. Metadata-only rules can still work, but text-content matching cannot.
Check the filter registration chain
- Verify the actual extension and content type of the file, not only its displayed name.
- Inspect the extension, ProgID/CLSID, PersistentHandler, and IFilter persistent-addin registration.
- Install a filter matching the server architecture and test it with the same service account.
Renaming an unsupported file to a supported extension is not a fix and can load the wrong parser. Filter handlers process untrusted document content inside a controlled host, so use vendor-supported and patched filters. After registration changes, restart the relevant filter host or service and test a representative file before rerunning classification broadly.
Understanding IFilter handlers · Registering filter handlers · Classification manager
Looking for a different code? Search another status or error code.