| Previous | Next |
| FILTER_S_PARTIAL_CONTENTSCAN_IMMEDIATE | FILTER_S_CONTENTSCAN_DELAYED |
FILTER_S_FULL_CONTENTSCAN_IMMEDIATE
Immediate full content scan is required
FILTER_S_FULL_CONTENTSCAN_IMMEDIATE is HRESULT 268082 (0x00041732) from Indexing Service. AllStat describes it as “A full content scan of the disk needs to be scheduled for immediate execution.” 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 a full content scan of the disk needs to be scheduled for immediate execution. Before reporting completion for it, the caller must reconcile the code-specific state transition and every usable output.
What must be true before accepting it
Verify that a full rebuild is justified and sufficient storage and maintenance capacity exist. Without that proof, this result can mask a caller error even though HRESULT failure severity is not set.
Reconcile side effects associated with this result before compensation or a second invocation is attempted.
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.
- It 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.
Because it is informational, a language binding may expose it as success and hide the symbolic distinction. Keep the original HRESULT available until the code-specific branch has run.
Evidence and telemetry
- preserve catalog and schema version.
- preserve reason partial scan is insufficient.
- preserve estimated document count.
- preserve free disk and temporary-space budget.
- preserve scan checkpoints and failures.
Also record filter_s_full_contentscan_immediate_operation, filter_s_full_contentscan_immediate_state_before, filter_s_full_contentscan_immediate_state_after, UTC time, process and thread identifiers, component version, and a correlation ID. Telemetry for it should omit credentials while retaining nonsecret object identities and version data.
Correct handling and recovery
Schedule a full scan immediately, coordinate with backup and query load, and monitor disk growth, filter failures, and completion checkpoints.
Retry it only when a documented input or state has changed. An unchanged retry after it is useful only when the API explicitly advances through repeated calls.
Practical scenario
A schema change invalidates every indexed property. The service starts a full scan in the maintenance window and keeps the previous catalog available until the replacement is complete.
A regression test should reproduce it, assert the relevant outputs and state, then change only the decisive condition and verify the expected neighboring result or ordinary completion.
Difference from nearby results
It must be distinguished from ordinary S_OK and from failure-severity values in the same API family; its documented state changes control the next action.
Correctly separating it from neighboring values selects the proper continuation and cleanup path.
References
- Microsoft: Filter interface values — official Microsoft material used to interpret it.
- Microsoft: About Indexing Service filters
- Microsoft: Using custom filters
- Microsoft: HRESULT values
Looking for a different code? Search another status or error code.