What does HRESULT 0x8004166B (QPARSE_E_UNSUPPORTED_PROPERTY_TYPE) mean?

 
Previous Next
QPARSE_E_EXPECTING_PHRASE QPARSE_E_EXPECTING_REGEX

QPARSE_E_UNSUPPORTED_PROPERTY_TYPE

The resolved property type is unsupported for the operation

QPARSE_E_UNSUPPORTED_PROPERTY_TYPE is the failure HRESULT 0x8004166B (-2147215765 signed; 2147751531 unsigned). Its severity bit is 1, facility is 4 (FACILITY_ITF), and code is 0x166B. AllStat describes it as “Unsupported property type.”

Operation and state

This result belongs to legacy Windows query parsing and is returned while validating operator capability against the property DBTYPE. The exact condition is: a text/regex/range operation targets a numeric, binary, vector or otherwise incompatible property. This stage matters because converting the result to a generic COM failure removes the information needed to choose the owner and retry policy.

This value comes from the legacy Indexing Service query parser. The exact final string, parser mode, locale and target property schema matter more than the query text shown in a user interface, because escaping and serialization can alter the token stream before parsing. Current Search SQL documentation can help compare operators and property syntax, but the failing token must still be interpreted under this legacy parser dialect.

Failure paths to examine

  • changes in canonical property between validation and execution can reproduce the result even when the user-visible input looks unchanged.
  • Retrying this result with the same actual DBTYPE leaves the decisive contract violation intact.
  • This result can appear when operator disagrees with the state expected while validating operator capability against the property DBTYPE.
  • a stale or transformed literal type can make the component observe that a text/regex/range operation targets a numeric, binary, vector or otherwise incompatible property.
  • an incomplete schema version hides the distinction needed to separate this HRESULT from a later catalog or service failure.

The strongest hypothesis for this HRESULT must account for the operation—validating operator capability against the property DBTYPE—and the documented condition. A parse failure does not identify the expected token class, property type, locale conversion or escaping layer until the final parser input is preserved.

Data to collect first

  • record the source and normalization path of canonical property, not only its display form.
  • use actual DBTYPE to test whether the failure belongs to parsing, execution, indexing or capability negotiation.
  • preserve operator before objects or work items are released.
  • associate literal type with the exact UTC timestamp and correlation identifier.
  • compare failing and known-good values for schema version under the same provider or handler version.
  • record the source and normalization path of final parser input bytes, not only its display form.

Evidence for this HRESULT should reflect what the component actually received. Preserve a bounded token window, offsets, quote and delimiter state, locale and canonical property identity without logging unrelated query text.

Step-by-step diagnosis

  1. Capture canonical property and actual DBTYPE at the call boundary that returns this result.
  2. confirm the operation reached validating operator capability against the property DBTYPE with the intended operator.
  3. perform the decisive check: read actual target-catalog schema instead of cached UI assumptions.
  4. reduce the case until changing literal type alone changes the HRESULT or proves it irrelevant.
  5. apply the recovery only after verifying schema version; preserve the original result for comparison.

A useful control for this HRESULT changes one dimension at a time. Begin with a minimal expression using the same property and parser mode, then add the failing literal, operator or delimiter without changing locale or escaping.

Continuation policy

Choose a type-appropriate operator or schema-owned indexed representation. Retry it only after the responsible input or state changes and the previous operation has completed or been cancelled. Retrying identical parser bytes cannot succeed; regenerate the specific token or schema pairing that failed.

Limits of this HRESULT

It does not prove that the user intent is invalid or that the catalog lacks data; it identifies how this parser interpreted the final serialized expression. Without code-specific evidence for this HRESULT, the value also cannot identify which wrapper, configuration, handler or service transition introduced the condition.

Distinguishing similar results

QPARSE_E_NO_SUCH_PROPERTY is lookup failure; this property exists but its type is incompatible. Keep the symbolic HRESULT beside the stage name in telemetry because nearby constants may require different owners, user messages and retry rules despite the same visible symptom.

Developer and administrator guidance

Retain final parser bytes, query form, token offset, expected token class, locale, escaping path and target property schema. Do not log credentials or unrestricted document content. Before changing catalog schema for this HRESULT, prove the final token stream and property type at the parser boundary.

Operational case

A textual prefix filter targets System.Size. The UI switches to numeric comparison after schema inspection. A regression test for this HRESULT should assert the decisive evidence, change only the responsible condition, and include one neighboring HRESULT so future code cannot collapse distinct failures into a generic message.

Official Microsoft references

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