| Previous | Next |
| QPARSE_E_EXPECTING_REAL | QPARSE_E_EXPECTING_CURRENCY |
QPARSE_E_EXPECTING_DATE
The parser expected a date literal
QPARSE_E_EXPECTING_DATE is HRESULT 0x80041663. Windows documents it as “Expecting date.”
Contract and failing stage
This result belongs to legacy Windows query parsing and is returned while reading a date/time property comparison. The exact condition is: the value is empty, ambiguous, localized or serialized with unsupported precision.
Conditions that produce it
Evidence to preserve
- Record raw date before releasing the relevant objects.
- Associate locale with the exact UTC timestamp and correlation identifier.
- Compare failing and known-good values for time zone under the same provider or handler version.
- Record the source and normalization path of precision, not only its display form.
- Record final parser input bytes before releasing the relevant objects.
Diagnostic sequence
- Capture raw date and locale at the call boundary that returns this result.
- Confirm the operation reached reading a date/time property comparison with the intended time zone.
- record calendar, locale, time zone, property type and exact transmitted form.
Recovery and retry
Emit an unambiguous dialect-supported date and define time-zone conversion explicitly. Retrying identical parser bytes cannot succeed; regenerate the specific token or schema pairing that failed.
What the code does not prove
Related HRESULT values
QPARSE_E_INVALID_LITERAL can reject a present date whose form is invalid.
Developer and administrator guidance
Practical scenario
A filter emits 31/12/2026 into a parser expecting another form. Schema-aware invariant serialization removes ambiguity.
Official Microsoft references
Looking for a different code? Search another status or error code.