What does HRESULT 0x80041670 (QPARSE_E_EXPECTING_EOS) mean?

 
Previous Next
QPARSE_E_NO_SUCH_PROPERTY QPARSE_E_EXPECTING_COMMA

QPARSE_E_EXPECTING_EOS

The parser expected end of string

QPARSE_E_EXPECTING_EOS is the failure HRESULT 0x80041670 (-2147215760 signed; 2147751536 unsigned). Its severity bit is 1, facility is 4 (FACILITY_ITF), and code is 0x1670. AllStat describes it as “Expecting end of string.”

Where the failure belongs

This result belongs to legacy Windows query parsing and is returned while finishing a valid top-level expression. The exact condition is: a second fragment, trailing comma, unsupported option or hidden token follows valid content. 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

  • changes in first trailing token between validation and execution can reproduce the result even when the user-visible input looks unchanged.
  • Retrying this result with the same longest valid prefix leaves the decisive contract violation intact.
  • This result can appear when suffix source disagrees with the state expected while finishing a valid top-level expression.
  • a stale or transformed control characters can make the component observe that a second fragment, trailing comma, unsupported option or hidden token follows valid content.
  • an incomplete query mode hides the distinction needed to separate this HRESULT from a later catalog or service failure.

The strongest hypothesis for this HRESULT must account for the operation—finishing a valid top-level expression—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

  • record the source and normalization path of first trailing token, not only its display form.
  • use longest valid prefix to test whether the failure belongs to parsing, execution, indexing or capability negotiation.
  • preserve suffix source before objects or work items are released.
  • associate control characters with the exact UTC timestamp and correlation identifier.
  • compare failing and known-good values for query mode under the same provider or handler version.
  • record the source and normalization path of final parser input bytes, not only its display form.

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

  1. Capture first trailing token and longest valid prefix at the call boundary that returns this result.
  2. confirm the operation reached finishing a valid top-level expression with the intended suffix source.
  3. perform the decisive check: capture the first trailing token and longest prefix that parses successfully.
  4. reduce the case until changing control characters alone changes the HRESULT or proves it irrelevant.
  5. apply the recovery only after verifying query mode; 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

Remove or correctly integrate the suffix; truncate only after proving it is unintended. 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

QPARSE_E_UNEXPECTED_EOS is the opposite: input ends while more syntax is required. 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 builder concatenates two WHERE fragments. An AST merger inserts the intended Boolean 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

Looking for a different code? Search another status or error code.