| Previous | Next |
| QPARSE_E_UNEXPECTED_EOS | QPARSE_E_NO_SUCH_SORT_PROPERTY |
QPARSE_E_WEIGHT_OUT_OF_RANGE
The relevance weight is outside its permitted range
QPARSE_E_WEIGHT_OUT_OF_RANGE is HRESULT 0x80041673. Windows documents it as “Weight must be between 0 and 1000 in short form queries and between 0.0 and 1.0 in long form queries.”
Exact contract boundary
This result belongs to legacy Windows query parsing and is returned while validating a term or ranking weight in short- or long-form query syntax. The exact condition is: short form requires 0–1000 while long form requires 0.0–1.0; scale, locale or negative input violates the range.
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.
Input or state defects
A parse failure does not identify the expected token class, property type, locale conversion or escaping layer until the final parser input is preserved.
Incident record
- Associate query form with the exact UTC timestamp and correlation identifier.
- Compare failing and known-good values for raw weight under the same provider or handler version.
- Record the source and normalization path of parsed value, not only its display form.
- Record boundary tests before releasing the relevant objects.
- Associate final parser input bytes with the exact UTC timestamp and correlation identifier.
Preserve a bounded token window, offsets, quote and delimiter state, locale and canonical property identity without logging unrelated query text.
How to isolate the cause
- Capture query form and raw weight at the call boundary that returns this result.
- Confirm the operation reached validating a term or ranking weight in short- or long-form query syntax with the intended parsed value.
- capture query form, raw weight and parsed numeric value before clamping.
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.
Restoration strategy
Validate the correct range and serialize invariantly; clamp only if the product contract explicitly says so. Retrying identical parser bytes cannot succeed; regenerate the specific token or schema pairing that failed.
Scope of the result
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.
Comparison with adjacent codes
QPARSE_E_INVALID_RANKMETHOD rejects the ranking method rather than its numeric weight.
Developer and administrator guidance
Retain final parser bytes, query form, token offset, expected token class, locale, escaping path and target property schema. Before changing catalog schema, prove the final token stream and property type at the parser boundary.
Example from a search pipeline
A UI value of 75 percent is emitted as 75 in long form. Explicit conversion to 0.75 preserves intent.
Official Microsoft references
Looking for a different code? Search another status or error code.