| Previous | Next |
| CI_E_NOT_FOUND | CI_E_DUPLICATE_NOTIFICATION |
CI_E_USE_DEFAULT_PID
The requested property ID is unsupported and the default should be used
CI_E_USE_DEFAULT_PID is HRESULT 0x80041816 (-2147215338 signed; 2147751958 unsigned). Its severity bit is 1, facility is 4 (FACILITY_ITF for these values), and code field is 0x1816. Standard HRESULT severity rules classify the value as a failure. AllStat describes the value as “The passed-in property id is not supported.”
Contract boundary
This result belongs to mapping a caller-supplied property identifier in a legacy content-index helper. The decisive interpretation is that the helper cannot use that PID under its schema and directs the caller toward default property behavior. 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.
Ways this state occurs
- The PID belongs to another property set; preserve the observation under the result correlation record.
- The provider version does not support the extension; preserve the observation under the result correlation record.
- A custom configuration uses an obsolete identifier; preserve the observation under the result correlation record.
- Numeric conversion changes the PID; preserve the observation under the result correlation record.
The useful hypothesis for it must explain both mapping a caller-supplied property identifier in a legacy content-index helper and the documented condition. Compare the failing case with a control that preserves property-set GUID and PID and changes only default property selected by the API; this prevents unrelated environment differences from dominating the result test.
Telemetry fields
- The result investigation should record property-set GUID and PID.
- The result investigation should record default property selected by the API.
- The result investigation should record provider/catalog version.
- The result investigation should record caller fallback behavior.
Capture property-set GUID and PID before releasing objects, closing handles or reconnecting. Retain the raw HRESULT with default property selected by the API, 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.
Verification sequence
- Validate the full property identity. Associate this observation specifically with this result.
- Confirm whether the contract treats this HRESULT as a fallback signal.
- Log the chosen default property explicitly.
- Do not silently apply a default when semantics would change dangerously. 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 helper cannot use that PID under its schema and directs the caller toward default property behavior. This isolates whether it is causal rather than merely repeatable.
Safe continuation
Use the documented default only when the calling contract allows it; otherwise surface unsupported-property behavior to the caller. Record whether mapping a caller-supplied property identifier in a legacy content-index helper 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 property-set GUID and PID or default property selected by the API. A timer alone cannot demonstrate that the result contract condition has changed.
Limits of the HRESULT
It does not mean a supported property is merely absent from cache. Without the call boundary for mapping a caller-supplied property identifier in a legacy content-index helper, it also cannot identify which wrapper or configuration layer introduced the condition.
Distinguishing related codes
CI_E_PROPERTY_NOT_CACHED concerns cache population; it concerns unsupported PID selection. 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 step 1 for it, at the code boundary, keep property-set GUID and PID beside the returned HRESULT
- At step 2 for it, in telemetry, correlate default property selected by the API with the target and component generation
- At step 3 for it, for regression coverage, force the documented condition: the helper cannot use that PID under its schema and directs the caller toward default property behavior
- At step 4 for it, for operations staff, expose the corrective state change rather than a generic retry button
- At step 5 for it, after remediation, validate one known-good control and the original failing case
Practical case
A legacy client requests a private PID on a standard catalog. The wrapper records the fallback and binds the documented default property. 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: IFilter::GetValue
- Microsoft: HRESULT values
Looking for a different code? Search another status or error code.