What does HRESULT 0x8004173B (FILTER_E_NO_SUCH_PROPERTY) mean?

 
Previous Next
FILTER_E_NOT_OPEN FILTER_E_OFFLINE

FILTER_E_NO_SUCH_PROPERTY

The requested property GUID is not exposed by the document

FILTER_E_NO_SUCH_PROPERTY is HRESULT 0x8004173B (-2147215557 signed; 2147751739 unsigned). Its severity bit is 1, facility is 4 (FACILITY_ITF for these values), and code field is 0x173B. For FILTER_E_NO_SUCH_PROPERTY, standard HRESULT severity rules classify the value as a failure. AllStat describes the value as “There is no property with the given GUID.”

Where the result belongs

FILTER_E_NO_SUCH_PROPERTY belongs to resolving a property-set/property identifier against the current object or filter metadata. The decisive interpretation is that the exact property identity is absent or unsupported for this handler and document. For FILTER_E_NO_SUCH_PROPERTY, keep the symbolic constant and method stage together in logs; its hexadecimal value alone cannot identify the owning transition or input.

For FILTER_E_NO_SUCH_PROPERTY, the IFilter contract is stateful: GetChunk selects a chunk, then GetText or GetValue consumes content according to STAT_CHUNK flags. In the FILTER_E_NO_SUCH_PROPERTY investigation, method order and filter-instance ownership are therefore part of the evidence. This context narrows the responsible component without replacing the code-specific checks below.

Concrete causes

  • For FILTER_E_NO_SUCH_PROPERTY, check the property-set GUID is wrong.
  • For FILTER_E_NO_SUCH_PROPERTY, check a PID belongs to another format version.
  • For FILTER_E_NO_SUCH_PROPERTY, check the caller assumes every handler exposes the same metadata.
  • For FILTER_E_NO_SUCH_PROPERTY, check schema registration and request are out of sync.

The useful hypothesis for FILTER_E_NO_SUCH_PROPERTY must explain both resolving a property-set/property identifier against the current object or filter metadata and the documented condition. Compare the failing case with a control that preserves full GUID and property ID and changes only document format and version; this prevents unrelated environment differences from dominating the FILTER_E_NO_SUCH_PROPERTY test.

Evidence to retain

  • Full GUID and property ID; preserve the observation under the FILTER_E_NO_SUCH_PROPERTY correlation record.
  • Document format and version; preserve the observation under the FILTER_E_NO_SUCH_PROPERTY correlation record.
  • Requested attribute list passed to Init; preserve the observation under the FILTER_E_NO_SUCH_PROPERTY correlation record.
  • Properties actually emitted by the filter; preserve the observation under the FILTER_E_NO_SUCH_PROPERTY correlation record.

For FILTER_E_NO_SUCH_PROPERTY, capture full GUID and property ID before releasing objects, closing handles or reconnecting. Retain the raw HRESULT with document format and version, component version, UTC timestamp and correlation ID. Bound the FILTER_E_NO_SUCH_PROPERTY telemetry to diagnostic metadata because document content, credentials and unrestricted query text may be sensitive.

Diagnostic path

  1. Preserve the complete property specification, not only a display name. Associate this observation specifically with FILTER_E_NO_SUCH_PROPERTY.
  2. Compare it with the schema for this document type. Associate this observation specifically with FILTER_E_NO_SUCH_PROPERTY.
  3. Inspect whether Init restricted the emitted attributes. Associate this observation specifically with FILTER_E_NO_SUCH_PROPERTY.
  4. Use a known supported property as a control. Associate this observation specifically with FILTER_E_NO_SUCH_PROPERTY.

Change one variable per FILTER_E_NO_SUCH_PROPERTY control run. Preserve the component version and target identity, then alter only the condition described as the exact property identity is absent or unsupported for this handler and document. This isolates whether FILTER_E_NO_SUCH_PROPERTY is causal rather than merely repeatable.

Recovery and retry

Request a supported canonical property or handle absence explicitly. Retry only after schema, document or handler capability changes. For FILTER_E_NO_SUCH_PROPERTY, record whether resolving a property-set/property identifier against the current object or filter metadata produced any content, update or state transition before returning. If completion remains unknown, the FILTER_E_NO_SUCH_PROPERTY path must not replay non-idempotent work until the owner confirms final state.

The retry gate for FILTER_E_NO_SUCH_PROPERTY should be a concrete change in full GUID and property ID or document format and version. A timer alone cannot demonstrate that the FILTER_E_NO_SUCH_PROPERTY contract condition has changed.

What must not be inferred

It does not mean the property value is empty; the property identity itself was not found. Without the call boundary for resolving a property-set/property identifier against the current object or filter metadata, FILTER_E_NO_SUCH_PROPERTY also cannot identify which wrapper or configuration layer introduced the condition.

Nearby results

FILTER_E_NO_VALUES describes a current chunk with no values, whereas this HRESULT rejects a specific property identity. In FILTER_E_NO_SUCH_PROPERTY telemetry, preserve neighboring constants separately because the same visible symptom may require a different caller action, owner or recovery gate.

Developer and administrator actions

  • The FILTER_E_NO_SUCH_PROPERTY investigation should record At the code boundary, keep full GUID and property ID beside the returned HRESULT.
  • The FILTER_E_NO_SUCH_PROPERTY investigation should record In telemetry, correlate document format and version with the target and component generation.
  • The FILTER_E_NO_SUCH_PROPERTY investigation should record For regression coverage, force the documented condition: the exact property identity is absent or unsupported for this handler and document.
  • The FILTER_E_NO_SUCH_PROPERTY investigation should record For operations staff, expose the corrective state change rather than a generic retry button.
  • The FILTER_E_NO_SUCH_PROPERTY investigation should record After remediation, validate one known-good control and the original failing case.

Operational example

A caller uses a custom property GUID from one document family against another. Canonical schema validation prevents the invalid request. In this scenario, handling FILTER_E_NO_SUCH_PROPERTY at its real contract boundary prevents the application from collapsing a precise state into an unhelpful generic “search failed” message.

Official Microsoft references

Looking for a different code? Search another status or error code.