What does HRESULT 0x80041664 (QPARSE_E_EXPECTING_CURRENCY) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

The parser expected a currency literal. Diagnose raw value, currency scale and symbol.

Previous	Next
QPARSE_E_EXPECTING_DATE	QPARSE_E_EXPECTING_GUID

QPARSE_E_EXPECTING_CURRENCY

The parser expected a currency literal

QPARSE_E_EXPECTING_CURRENCY is the failure HRESULT 0x80041664 (-2147215772 signed; 2147751524 unsigned). Its severity bit is 1, facility is 4 (FACILITY_ITF), and code is 0x1664. AllStat describes it as “Expecting currency.”

Where the failure belongs

This result belongs to legacy Windows query parsing and is returned while reading a currency-valued comparison or argument. The exact condition is: the token contains an unsupported symbol, locale separators, missing numeric content or excess scale. 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

a stale or transformed raw value can make the component observe that the token contains an unsupported symbol, locale separators, missing numeric content or excess scale.
an incomplete currency scale hides the distinction needed to separate this HRESULT from a later catalog or service failure.
changes in symbol between validation and execution can reproduce the result even when the user-visible input looks unchanged.
Retrying this result with the same decimal separator leaves the decisive contract violation intact.
This result can appear when property type disagrees with the state expected while reading a currency-valued comparison or argument.

The strongest hypothesis for this HRESULT must account for the operation—reading a currency-valued 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.

Telemetry that matters

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

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

Capture raw value and currency scale at the call boundary that returns this result.
confirm the operation reached reading a currency-valued comparison or argument with the intended symbol.
perform the decisive check: capture unscaled value, scale, symbol policy and target property type.
reduce the case until changing decimal separator 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.

Safe remediation

Serialize the numeric currency representation required by the query 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.

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_EXPECTING_REAL is not a substitute because currency scale semantics differ. 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 UI inserts a localized symbol and grouping spaces. The query builder uses the underlying scaled numeric value instead. 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.