What does HRESULT 0x00041704 (FILTER_W_MONIKER_CLIPPED) mean?

FILTER_W_MONIKER_CLIPPED

Filter moniker covers only part of the region

FILTER_W_MONIKER_CLIPPED is HRESULT 268036 (0x00041704) from Indexing Service. The documented description is “Moniker doesn't cover entire region.” The severity bit indicates a nonfailure result, but the value carries a specific condition that must not be collapsed into plain S_OK.

In the legacy Indexing Service or IFilter pipeline, this result means that moniker doesn't cover entire region. Consumers of it must decide from the API contract whether to stop, wait, continue, or expose a reduced outcome.

What must be true before accepting it

Verify that the caller knows which region the moniker represents and does not attribute extracted content to the whole document. Checking the boundary keeps this result from hiding stale data, pending work, or a deliberately reduced result.

Do not compensate until the caller knows which sub-operations actually occurred.

Where the status is encountered

• This result can be returned during legacy Indexing Service catalog processing; log the exact method and object state instead of interpreting the constant outside that contract.
• This result can be returned during IFilter text and property extraction; log the exact method and object state instead of interpreting the constant outside that contract.
• It can be returned during search enumeration, scan scheduling, or catalog administration; log the exact method and object state instead of interpreting the constant outside that contract.

Evidence to preserve

• Preserve moniker display name.
• Preserve region start and extent.
• Preserve parent document identity.
• Preserve chunk source IDs.
• Preserve offset mapping between region and document.

Correct handling and recovery

Record the region boundaries and moniker, then either process the uncovered regions separately or mark the extraction as partial. Avoid generating document-wide offsets from clipped input.

Continuation after it may be appropriate, but an identical restart is not automatically recovery.

Practical scenario

A compound-document filter receives a moniker for one embedded object rather than the entire file. The indexer tags extracted text with the embedded region and schedules the remaining regions independently.

Difference from nearby results

References

• Microsoft: Filter interface values — official Microsoft material relevant to this HRESULT.
• Microsoft: About Indexing Service filters
• Microsoft: Using custom filters
• Microsoft: HRESULT values