| 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 the failure HRESULT 0x8004166F (-2147215761 signed; 2147751535 unsigned). Its severity bit is 1, facility is 4 (FACILITY_ITF), and code is 0x166F. AllStat describes 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. 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.
Conditions that produce it
- an incomplete exact token hides the distinction needed to separate this HRESULT from a later catalog or service failure.
- changes in canonical form between validation and execution can reproduce the result even when the user-visible input looks unchanged.
- Retrying this result with the same catalog identity leaves the decisive contract violation intact.
- This result can appear when schema registration disagrees with the state expected while looking up a syntactically present property in the target catalog schema.
- a stale or transformed provider version can make the component observe that a misspelling, display label, missing custom schema or version mismatch prevents lookup.
The strongest hypothesis for this HRESULT must account for the operation—looking up a syntactically present property in the target catalog schema—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.
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.
- use catalog identity to test whether the failure belongs to parsing, execution, indexing or capability negotiation.
- preserve schema registration before objects or work items are released.
- 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.
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.
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.
- perform the decisive check: compare the exact token with canonical target-catalog property metadata.
- reduce the case until changing schema registration alone changes the HRESULT or proves it irrelevant.
- apply the recovery only after verifying provider 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.
Recovery and retry
Correct the identity or restore legitimate schema registration before considering reindexing. 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.
What the code does not prove
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.
Related HRESULT values
QPARSE_E_EXPECTING_PROPERTY means no usable token was supplied. 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.
Practical scenario
A client uses the friendly label `Author`; mapping it to System.Author fixes lookup without a content scan. 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
- Microsoft: legacy Indexing Service error messages
- Microsoft: Windows Search WHERE clause
- Microsoft: Windows Search SQL syntax
- Microsoft: ISearchQueryHelper
Looking for a different code? Search another status or error code.