What does HRESULT 0x80041672 (QPARSE_E_UNEXPECTED_EOS) mean?

 
Previous Next
QPARSE_E_EXPECTING_COMMA QPARSE_E_WEIGHT_OUT_OF_RANGE

QPARSE_E_UNEXPECTED_EOS

Input ended before the query construct was complete

QPARSE_E_UNEXPECTED_EOS is the failure HRESULT 0x80041672 (-2147215758 signed; 2147751538 unsigned). Its severity bit is 1, facility is 4 (FACILITY_ITF), and code is 0x1672. AllStat describes it as “Unexpected end of string.”

Interpretation

This result belongs to legacy Windows query parsing and is returned while reaching physical string end with an outstanding parser expectation. The exact condition is: a dangling operator, open delimiter, missing value or truncation leaves syntax incomplete. 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.

Concrete sources

  • This result can appear when last complete token disagrees with the state expected while reaching physical string end with an outstanding parser expectation.
  • a stale or transformed expected token can make the component observe that a dangling operator, open delimiter, missing value or truncation leaves syntax incomplete.
  • an incomplete original length hides the distinction needed to separate this HRESULT from a later catalog or service failure.
  • changes in transmitted length between validation and execution can reproduce the result even when the user-visible input looks unchanged.
  • Retrying this result with the same delimiter stack leaves the decisive contract violation intact.

The strongest hypothesis for this HRESULT must account for the operation—reaching physical string end with an outstanding parser expectation—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.

Observability checklist

  • preserve last complete token before objects or work items are released.
  • associate expected token with the exact UTC timestamp and correlation identifier.
  • compare failing and known-good values for original length under the same provider or handler version.
  • record the source and normalization path of transmitted length, not only its display form.
  • use delimiter stack to test whether the failure belongs to parsing, execution, indexing or capability negotiation.
  • preserve final parser input bytes before objects or work items are released.

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.

Investigation order

  1. Capture last complete token and expected token at the call boundary that returns this result.
  2. confirm the operation reached reaching physical string end with an outstanding parser expectation with the intended original length.
  3. perform the decisive check: compare original and transmitted lengths and record the exact expected token at EOS.
  4. reduce the case until changing transmitted length alone changes the HRESULT or proves it irrelevant.
  5. apply the recovery only after verifying delimiter stack; 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.

Corrective action

Restore the specific missing node or fix string-length/encoding transport. 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 must not be inferred

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.

Neighboring status codes

QPARSE_E_EXPECTING_EOS finds extra input after a complete expression. 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.

Reproduction example

An embedded null truncates text after `System.Title =`. Correct length handling restores the intended literal. 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.