| Previous | Next |
| FSRM_E_PARTIAL_CLASSIFICATION_PROPERTY_NOT_FOUND | FSRM_E_TEXTREADER_IFILTER_NOT_FOUND |
FSRM_E_TEXTREADER_NOT_INITIALIZED
FSRM_E_TEXTREADER_NOT_INITIALIZED indicates an internal content-classification reader was asked to extract text before it had a file stream, filter, or other required state initialized for the current file.
Verify the content-reader lifecycle
- Check the earlier file-open and IFilter-selection messages for the same path.
- Confirm that the classifier declares
NeedsFileContentand receives a readable stream. - Do not reuse a reader instance across files after a failed initialization or module-session transition.
This is different from “no IFilter found”: initialization can fail even when a handler is registered, for example because the stream cannot be obtained or the filter cannot load. Preserve the first failure in the event log and fix that cause rather than retrying text extraction on an uninitialized object.
Module NeedsFileContent · GetFileStreamInterface · IFilter overview
Looking for a different code? Search another status or error code.