| Previous | Next |
| QPARSE_E_INVALID_LITERAL | QPARSE_E_EXPECTING_EOS |
QPARSE_E_NO_SUCH_PROPERTY
The named property cannot be resolved
QPARSE_E_NO_SUCH_PROPERTY is HRESULT 0x8004166F. Windows documents it as “No such property.”
Contract and failing stage
This result belongs to legacy Windows query parsing and is returned while looking up a syntactically present property in the target catalog schema. The exact condition is: a misspelling, display label, missing custom schema or version mismatch prevents lookup.
Conditions that produce it
Evidence to preserve
- Compare failing and known-good values for exact token under the same provider or handler version.
- Record the source and normalization path of canonical form, not only its display form.
- Record schema registration before releasing the relevant objects.
- Associate provider version with the exact UTC timestamp and correlation identifier.
- Compare failing and known-good values for final parser input bytes under the same provider or handler version.
Diagnostic sequence
- Capture exact token and canonical form at the call boundary that returns this result.
- Confirm the operation reached looking up a syntactically present property in the target catalog schema with the intended catalog identity.
- compare the exact token with canonical target-catalog property metadata.
Recovery and retry
Correct the identity or restore legitimate schema registration before considering reindexing. Retrying identical parser bytes cannot succeed; regenerate the specific token or schema pairing that failed.
What the code does not prove
Related HRESULT values
QPARSE_E_EXPECTING_PROPERTY means no usable token was supplied.
Developer and administrator guidance
Practical scenario
A client uses the friendly label Author; mapping it to System.Author fixes lookup without a content scan.
Official Microsoft references
Looking for a different code? Search another status or error code.