| Previous | Next |
| FILTER_E_ACCESS | FILTER_E_NO_VALUES |
FILTER_E_NO_TEXT
The current filter chunk does not contain text
FILTER_E_NO_TEXT is HRESULT 0x80041705. Its failure-severity encoding reports a method/chunk-type mismatch, not necessarily a defect in the source document. Windows documents it as “No text in current chunk.”
Interpretation in context
This result belongs to calling IFilter::GetText when STAT_CHUNK describes a property-value chunk or another nontext chunk. The caller selected the wrong extraction method for the current chunk type.
Conditions to test
- CHUNK_VALUE was returned but the consumer calls GetText.
- Chunk flags were cached from a previous chunk.
- A filter emits metadata-only content.
Compare the failing case with a control that preserves current STAT_CHUNK flags and attribute and changes only exact GetChunk/GetText sequence; this prevents unrelated environment differences from dominating the test.
Incident record
- Check current STAT_CHUNK flags and attribute.
- Check exact GetChunk/GetText sequence.
- Check chunk id used by the consumer.
- Check filter conformance output.
Capture current STAT_CHUNK flags and attribute before releasing objects, closing handles or reconnecting. Retain the raw HRESULT with exact GetChunk/GetText sequence, component version, UTC timestamp and correlation ID.
Step-by-step diagnosis
- Inspect flags immediately after each successful GetChunk.
- Dispatch CHUNK_TEXT to GetText and CHUNK_VALUE to GetValue.
- Remove stale chunk metadata from asynchronous queues.
- Confirm the filter did not change flags after returning the chunk.
Preserve the component version and target identity, then alter only the condition described as the caller selected the wrong extraction method for the current chunk type.
Retry decision
Use the method indicated by STAT_CHUNK or advance to the next chunk. Retrying GetText is a contract error in the caller. Record whether calling IFilter::GetText when STAT_CHUNK describes a property-value chunk or another nontext chunk produced any content, update or state transition before returning.
Retry only after a concrete change in current STAT_CHUNK flags and attribute or exact GetChunk/GetText sequence.
What the value cannot establish
It does not say the whole document lacks text; later chunks may contain searchable text. Without the call boundary for calling IFilter::GetText when STAT_CHUNK describes a property-value chunk or another nontext chunk, it also cannot identify which wrapper or configuration layer introduced the condition.
Adjacent contract states
FILTER_E_NO_MORE_TEXT exhausts a valid text chunk; it identifies a nontext current chunk.
Developer and administrator actions
- Record current STAT_CHUNK flags and attribute with the returned HRESULT
- In telemetry, correlate exact GetChunk/GetText sequence with the target and component generation
- For regression coverage, force the documented condition: the caller selected the wrong extraction method for the current chunk type
Concrete scenario
A parallel extractor associates the previous chunk flags with a new chunk and calls GetText. Serializing chunk state fixes the method mismatch.
Official Microsoft references
- Microsoft: Filter-Interface values — official contract information relevant to this HRESULT.
- Microsoft: IFilter::GetText
- Microsoft: IFilter::GetChunk
- Microsoft: testing filter handlers
- Microsoft: IFilter interface
Looking for a different code? Search another status or error code.