What does HRESULT 0x80041661 (QPARSE_E_EXPECTING_INTEGER) mean?

 
Previous Next
QPARSE_E_UNEXPECTED_NOT QPARSE_E_EXPECTING_REAL

QPARSE_E_EXPECTING_INTEGER

The parser expected an integer literal

QPARSE_E_EXPECTING_INTEGER is the failure HRESULT 0x80041661 (-2147215775 signed; 2147751521 unsigned). Its severity bit is 1, facility is 4 (FACILITY_ITF), and code is 0x1661. AllStat describes it as “Expecting integer.”

Exact contract boundary

This result belongs to legacy Windows query parsing and is returned while reading a whole-number value. The exact condition is: an empty field, symbolic value, localized digits or unsupported numeric form appears. 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.

Input or state defects

  • changes in raw token between validation and execution can reproduce the result even when the user-visible input looks unchanged.
  • Retrying this result with the same property type leaves the decisive contract violation intact.
  • This result can appear when operator disagrees with the state expected while reading a whole-number value.
  • a stale or transformed allowed range can make the component observe that an empty field, symbolic value, localized digits or unsupported numeric form appears.
  • an incomplete locale 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—reading a whole-number value—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.

Incident record

  • record the source and normalization path of raw token, not only its display form.
  • use property type to test whether the failure belongs to parsing, execution, indexing or capability negotiation.
  • preserve operator before objects or work items are released.
  • associate allowed range with the exact UTC timestamp and correlation identifier.
  • compare failing and known-good values for locale 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.

How to isolate the cause

  1. Capture raw token and property type at the call boundary that returns this result.
  2. confirm the operation reached reading a whole-number value with the intended operator.
  3. perform the decisive check: record property type, operator, sign policy, base and range.
  4. reduce the case until changing allowed range alone changes the HRESULT or proves it irrelevant.
  5. apply the recovery only after verifying locale; 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.

Restoration strategy

Emit an invariant in-range integer; do not insert zero as a generic default. 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.

Scope of the result

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.

Comparison with adjacent codes

QPARSE_E_INVALID_LITERAL covers a present but malformed typed literal. 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.

Example from a search pipeline

A locale formatter emits a thousands separator in a count. Invariant serialization restores the integer token. 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.