| 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 HRESULT 0x8004166B. Windows documents 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 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
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.
- Record operator before releasing the relevant objects.
- 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.
Preserve a bounded token window, offsets, quote and delimiter state, locale and canonical property identity without logging unrelated query text.
Step-by-step diagnosis
- Capture canonical property and actual DBTYPE at the call boundary that returns this result.
- Confirm the operation reached validating operator capability against the property DBTYPE with the intended operator.
- read actual target-catalog schema instead of cached UI assumptions.
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. 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.
Distinguishing similar results
QPARSE_E_NO_SUCH_PROPERTY is lookup failure; this property exists but its type is incompatible.
Developer and administrator guidance
Retain final parser bytes, query form, token offset, expected token class, locale, escaping path and target property schema. Before changing catalog schema, 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.
Official Microsoft references
Looking for a different code? Search another status or error code.