| Previous | Next |
| FDAEMON_W_EMPTYWORDLIST | FILTER_W_MONIKER_CLIPPED |
SEARCH_S_NOMOREHITS
Search enumeration reached the end of hits
SEARCH_S_NOMOREHITS is HRESULT 267936 (0x000416A0) from Indexing Service. AllStat describes it as “End of hits has been reached.” 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 end of hits has been reached. Before reporting completion for it, the caller must reconcile the code-specific state transition and every usable output.
Where the status is encountered
- Legacy Indexing Service catalog processing; log the exact method and object state instead of interpreting the constant outside that contract.
- IFilter text and property extraction; log the exact method and object state instead of interpreting the constant outside that contract.
- 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 query text and scope.
- preserve catalog generation.
- preserve page size and cumulative hit count.
- preserve last work ID or bookmark.
- preserve enumerator lifetime.
Also record search_s_nomorehits_operation, search_s_nomorehits_state_before, search_s_nomorehits_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.
What must be true before accepting it
Verify that the consumer has processed every returned hit and stops without treating normal exhaustion as an error. Without that proof, it can mask a caller error even though HRESULT failure severity is not set.
Reconcile side effects associated with it before compensation or a second invocation is attempted.
Correct handling and recovery
Finish the enumeration, release query handles, and retain the final count. Retry only after the catalog or query changes, not to obtain more rows from the same exhausted cursor.
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.
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.
Practical scenario
A search client reads pages of results until this status arrives. It shows the exact total and closes the command instead of displaying a failure banner.
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.
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.