What does HRESULT 0x80041662 (QPARSE_E_EXPECTING_REAL) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

The parser expected a real-number literal. Diagnose raw token, decimal separator and exponent form.

Previous	Next
QPARSE_E_EXPECTING_INTEGER	QPARSE_E_EXPECTING_DATE

QPARSE_E_EXPECTING_REAL

The parser expected a real-number literal

QPARSE_E_EXPECTING_REAL is the failure HRESULT 0x80041662 (-2147215774 signed; 2147751522 unsigned). Its severity bit is 1, facility is 4 (FACILITY_ITF), and code is 0x1662. AllStat describes it as “Expecting real number.”

Legacy API stage

This result belongs to legacy Windows query parsing and is returned while reading a floating-point comparison or argument. The exact condition is: the token is empty, quoted, uses a comma decimal, or contains unsupported NaN/infinity text. 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.

Why it appears

Retrying this result with the same raw token leaves the decisive contract violation intact.
This result can appear when decimal separator disagrees with the state expected while reading a floating-point comparison or argument.
a stale or transformed exponent form can make the component observe that the token is empty, quoted, uses a comma decimal, or contains unsupported NaN/infinity text.
an incomplete finite-value check hides the distinction needed to separate this HRESULT from a later catalog or service failure.
changes in property type between validation and execution can reproduce the result even when the user-visible input looks unchanged.

The strongest hypothesis for this HRESULT must account for the operation—reading a floating-point comparison or argument—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.

Developer evidence

use raw token to test whether the failure belongs to parsing, execution, indexing or capability negotiation.
preserve decimal separator before objects or work items are released.
associate exponent form with the exact UTC timestamp and correlation identifier.
compare failing and known-good values for finite-value check under the same provider or handler version.
record the source and normalization path of property type, not only its display form.
use final parser input bytes to test whether the failure belongs to parsing, execution, indexing or capability negotiation.

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.

Disciplined troubleshooting

Capture raw token and decimal separator at the call boundary that returns this result.
confirm the operation reached reading a floating-point comparison or argument with the intended exponent form.
perform the decisive check: capture decimal separator, exponent form and target property type.
reduce the case until changing finite-value check alone changes the HRESULT or proves it irrelevant.
apply the recovery only after verifying property type; 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.

Retry conditions

Emit a finite invariant real number supported by the grammar. 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.

Misleading assumptions

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 query outcomes

QPARSE_E_EXPECTING_INTEGER names a whole-number field rather than floating point. 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.

Concrete troubleshooting case

A UI value `0,75` reaches an invariant parser. Converting the numeric value to `0.75` fixes the query. 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.