| Previous | Next |
| QPARSE_E_NO_SUCH_SORT_PROPERTY | QUTIL_E_CANT_CONVERT_VROOT |
QPARSE_E_INVALID_SORT_ORDER
The sort direction token is invalid
QPARSE_E_INVALID_SORT_ORDER is HRESULT 0x80041675. Windows documents it as “An invalid sort order was specified. Only [a] and [d] are supported.”
Contract and failing stage
This result belongs to legacy Windows query parsing and is returned while reading ascending/descending syntax for a valid sort key. The exact condition is: the affected legacy grammar accepts only [a] and [d], while a generic builder emits other words or booleans.
Conditions that produce it
Evidence to preserve
- Record the source and normalization path of raw direction, not only its display form.
- Record sort key before releasing the relevant objects.
- Associate builder branch with the exact UTC timestamp and correlation identifier.
- Compare failing and known-good values for ascending/descending control under the same provider or handler version.
- Record the source and normalization path of final parser input bytes, not only its display form.
Diagnostic sequence
- Capture raw direction and query form at the call boundary that returns this result.
- Confirm the operation reached reading ascending/descending syntax for a valid sort key with the intended sort key.
- capture raw direction, query form and builder branch.
Recovery and retry
Map ascending and descending to the documented dialect tokens without localization. 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_NO_SUCH_SORT_PROPERTY rejects key identity, not direction.
Developer and administrator guidance
Practical scenario
A shared builder emits DESC; a legacy serializer emits [d] and preserves descending order.
Official Microsoft references
Looking for a different code? Search another status or error code.