| 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 HRESULT 0x80041662. Windows documents 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.
Why it appears
Developer evidence
- Record decimal separator before releasing the relevant objects.
- 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.
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.
- capture decimal separator, exponent form and target property type.
Retry conditions
Emit a finite invariant real number supported by the grammar. Retrying identical parser bytes cannot succeed; regenerate the specific token or schema pairing that failed.
Misleading assumptions
Related query outcomes
QPARSE_E_EXPECTING_INTEGER names a whole-number field rather than floating point.
Developer and administrator guidance
Concrete troubleshooting case
A UI value 0,75 reaches an invariant parser. Converting the numeric value to 0.75 fixes the query.
Official Microsoft references
Looking for a different code? Search another status or error code.