| Previous | Next |
| IDS_MON_INVALIDSELECT_COALESCE | IDS_MON_DATE_OUT_OF_RANGE |
IDS_MON_CANNOT_CAST
IDS_MON_CANNOT_CAST focuses on the literal side of a conversion. Windows Search distinguishes string, numeric, hexadecimal, Boolean, and date literals, and explicit casts support a documented set of target types. A syntactically valid literal can still be impossible to convert to the requested type.
Inspect the literal before changing the property schema
- Preserve the exact literal text and quote placement.
- Verify the explicit cast target and compare it with the documented Windows Search data types.
- Check for locale-generated decimal separators or date strings that do not use the supported date/time literal form.
A quoted number is parsed as a string, Boolean literals must be unquoted, hexadecimal values use a 0x prefix, and dates use specific year/month/day or year-month-day forms. Those rules make textual query generation a frequent source of cast failures. Fix serialization at the query boundary; changing indexed documents cannot make an invalid literal cast succeed.
Literals · Casting data types · Data type mappings
Looking for a different code? Search another status or error code.