What does HRESULT 0x8004180D (CI_E_PROPERTY_NOT_CACHED) mean?

CI_E_PROPERTY_NOT_CACHED

The requested property is not present in the property cache

CI_E_PROPERTY_NOT_CACHED is HRESULT 0x8004180D. Windows documents it as “The given property is not cached.”

Interpretation in context

This result belongs to retrieving a cached property for a catalog item or query result. The schema or indexing policy did not store that property in the cache used by the helper.

Conditions to test

• The property was never configured as cached.
• The item predates a schema change.
• The file handler did not emit the property.
• The caller confuses retrievable source metadata with cached catalog data.

Compare the failing case with a control that preserves canonical property identity and changes only catalog/schema generation; this prevents unrelated environment differences from dominating the test.

Incident record

• Check canonical property identity.
• Check catalog/schema generation.
• Check item work ID and indexing time.
• Check properties configured and actually emitted.

Capture canonical property identity before releasing objects, closing handles or reconnecting. Retain the raw HRESULT with catalog/schema generation, component version, UTC timestamp and correlation ID.

Step-by-step diagnosis

1. Verify the property is cache-enabled in the target catalog.
2. Reindex a controlled item after any schema change.
3. Inspect filter output for the property.
4. Use an alternate retrieval path only when its cost and permissions are acceptable.

Preserve the component version and target identity, then alter only the condition described as the schema or indexing policy did not store that property in the cache used by the helper.

Retry decision

Change cache configuration and reindex, or handle absence. Repeating the same cache lookup cannot populate the value. Record whether retrieving a cached property for a catalog item or query result produced any content, update or state transition before returning.

Retry only after a concrete change in canonical property identity or catalog/schema generation.

What the value cannot establish

It does not prove that the source document lacks the property. Without the call boundary for retrieving a cached property for a catalog item or query result, it also cannot identify which wrapper or configuration layer introduced the condition.

Adjacent contract states

CI_E_USE_DEFAULT_PID means an unsupported property ID should fall back; this HRESULT says a valid property is not cached.

Developer and administrator actions

• Record canonical property identity with the returned HRESULT
• In telemetry, correlate catalog/schema generation with the target and component generation
• For regression coverage, force the documented condition: the schema or indexing policy did not store that property in the cache used by the helper

Concrete scenario

A new custom property is added to query projections but old items were not reindexed. Catalog-generation telemetry explains mixed results.

Official Microsoft references

• Microsoft: content-indexing helper-function values — official contract information relevant to this HRESULT.
• Microsoft: Content-Indexing values
• Microsoft: IFilter::Init
• Microsoft: IFilter::GetValue
• Microsoft: HRESULT values