| Previous | Next |
| CI_E_SHUTDOWN | CI_E_NOT_FOUND |
CI_E_WORKID_NOTVALID
The supplied content-index work ID is invalid
CI_E_WORKID_NOTVALID is HRESULT 0x80041813 (-2147215341 signed; 2147751955 unsigned). Its severity bit is 1, facility is 4 (FACILITY_ITF for these values), and code field is 0x1813. Standard HRESULT severity rules classify the value as a failure. AllStat describes the value as “The workid is not valid.”
Interpretation in context
This result belongs to resolving a document identifier for update, deletion, notification or property access. The decisive interpretation is that the work ID is unknown, stale, malformed or belongs to another catalog generation. Keep the symbolic constant and method stage together in logs; its hexadecimal value alone cannot identify the owning transition or input.
The legacy content-index helper layer has explicit object, catalog and service states. In the result investigation, a generic retry can hide lifecycle, ordering or policy defects. This context narrows the responsible component without replacing the code-specific checks below.
Conditions to test
- This result: The item was deleted and its ID recycled or retired.
- This result: A work ID from one catalog is sent to another.
- This result: Serialization truncates the identifier.
- It: A client caches IDs across catalog rebuild.
The useful hypothesis for it must explain both resolving a document identifier for update, deletion, notification or property access and the documented condition. Compare the failing case with a control that preserves raw work ID and width and changes only catalog identity and generation; this prevents unrelated environment differences from dominating the result test.
Incident record
- check raw work ID and width.
- check catalog identity and generation.
- check operation requesting the item.
- check lookup history and deletion events.
Capture raw work ID and width before releasing objects, closing handles or reconnecting. Retain the raw HRESULT with catalog identity and generation, component version, UTC timestamp and correlation ID. Bound the result telemetry to diagnostic metadata because document content, credentials and unrestricted query text may be sensitive.
Step-by-step diagnosis
- Verify the ID in the same catalog used by the caller. Associate this observation specifically with it.
- Check whether a rebuild or deletion invalidated cached mappings. Associate this observation specifically with it.
- Audit serialization and signedness. Associate this observation specifically with it.
- Resolve the current item identity from its canonical source when possible. Associate this observation specifically with it.
Change one variable per it control run. Preserve the component version and target identity, then alter only the condition described as the work ID is unknown, stale, malformed or belongs to another catalog generation. This isolates whether it is causal rather than merely repeatable.
Retry decision
Refresh the mapping and retry only with a newly resolved valid work ID. Do not guess or increment identifiers. Record whether resolving a document identifier for update, deletion, notification or property access produced any content, update or state transition before returning. If completion remains unknown, the path must not replay non-idempotent work until the owner confirms final state.
The retry gate for it should be a concrete change in raw work ID and width or catalog identity and generation. A timer alone cannot demonstrate that the result contract condition has changed.
What the value cannot establish
It does not mean the source document itself is missing. Without the call boundary for resolving a document identifier for update, deletion, notification or property access, it also cannot identify which wrapper or configuration layer introduced the condition.
Adjacent contract states
CI_E_NOT_FOUND is a broader object lookup result; this HRESULT specifically rejects the work-ID token. In it telemetry, preserve neighboring constants separately because the same visible symptom may require a different caller action, owner or recovery gate.
Developer and administrator actions
- At the code boundary, keep raw work ID and width beside the returned HRESULT; preserve the observation under the result correlation record.
- In telemetry, correlate catalog identity and generation with the target and component generation; preserve the observation under the result correlation record.
- For regression coverage, force the documented condition: the work ID is unknown, stale, malformed or belongs to another catalog generation; preserve the observation under the result correlation record.
- For operations staff, expose the corrective state change rather than a generic retry button; preserve the observation under the result correlation record.
- After remediation, validate one known-good control and the original failing case; preserve the observation under the result correlation record.
Concrete scenario
A client persists work IDs across a catalog recreation. Storing the catalog generation with each ID prevents stale updates. In this scenario, handling it at its real contract boundary prevents the application from collapsing a precise state into an unhelpful generic “search failed” message.
Official Microsoft references
- Microsoft: content-indexing helper-function values — official contract information relevant to it.
- Microsoft: Content-Indexing values
- Microsoft: HRESULT values
- Microsoft: Windows Search SQL syntax
Looking for a different code? Search another status or error code.