| Previous | Next |
| QPARSE_E_NOT_YET_IMPLEMENTED | QPARSE_E_UNSUPPORTED_PROPERTY_TYPE |
QPARSE_E_EXPECTING_PHRASE
The parser expected a phrase operand
QPARSE_E_EXPECTING_PHRASE is the failure HRESULT 0x8004166A (-2147215766 signed; 2147751530 unsigned). Its severity bit is 1, facility is 4 (FACILITY_ITF), and code is 0x166A. AllStat describes it as “Expecting phrase.”
Where the failure belongs
This result belongs to legacy Windows query parsing and is returned while reading a full-text phrase-bearing construct. The exact condition is: the phrase is empty, omitted, stripped by escaping or replaced by a Boolean operator. 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.
Likely causes
- an incomplete raw phrase hides the distinction needed to separate this HRESULT from a later catalog or service failure.
- changes in escaped phrase between validation and execution can reproduce the result even when the user-visible input looks unchanged.
- Retrying this result with the same quote boundaries leaves the decisive contract violation intact.
- This result can appear when language disagrees with the state expected while reading a full-text phrase-bearing construct.
- a stale or transformed owning operator can make the component observe that the phrase is empty, omitted, stripped by escaping or replaced by a Boolean operator.
The strongest hypothesis for this HRESULT must account for the operation—reading a full-text phrase-bearing construct—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.
Telemetry that matters
- compare failing and known-good values for raw phrase under the same provider or handler version.
- record the source and normalization path of escaped phrase, not only its display form.
- use quote boundaries to test whether the failure belongs to parsing, execution, indexing or capability negotiation.
- preserve language before objects or work items are released.
- associate owning operator 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.
Verification workflow
- Capture raw phrase and escaped phrase at the call boundary that returns this result.
- confirm the operation reached reading a full-text phrase-bearing construct with the intended quote boundaries.
- perform the decisive check: preserve pre-escape and final phrase text plus quote boundaries.
- reduce the case until changing language alone changes the HRESULT or proves it irrelevant.
- apply the recovery only after verifying owning operator; 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.
Safe remediation
Require nonempty phrase content and serialize the phrase node atomically. 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.
Avoid the wrong conclusion
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.
How nearby codes differ
QUERY_E_ALLNOISE happens after syntactically valid text is removed by linguistic processing. 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.
Worked example
A form emits `CONTAINS()` for a blank box. The builder refuses to serialize the empty node. 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.