What does HRESULT 0x80041674 (QPARSE_E_NO_SUCH_SORT_PROPERTY) mean?

 
Previous Next
QPARSE_E_WEIGHT_OUT_OF_RANGE QPARSE_E_INVALID_SORT_ORDER

QPARSE_E_NO_SUCH_SORT_PROPERTY

The sort property cannot be resolved

QPARSE_E_NO_SUCH_SORT_PROPERTY is the failure HRESULT 0x80041674 (-2147215756 signed; 2147751540 unsigned). Its severity bit is 1, facility is 4 (FACILITY_ITF), and code is 0x1674. AllStat describes it as “An invalid property was found in the sort specification.”

Legacy API stage

This result belongs to legacy Windows query parsing and is returned while looking up a key inside the sort specification. The exact condition is: a misspelling, alias, absent custom schema or version mismatch affects the sort key. 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.

Why it appears

  • an incomplete sort token hides the distinction needed to separate this HRESULT from a later catalog or service failure.
  • changes in canonical mapping between validation and execution can reproduce the result even when the user-visible input looks unchanged.
  • Retrying this result with the same catalog version leaves the decisive contract violation intact.
  • This result can appear when sort eligibility disagrees with the state expected while looking up a key inside the sort specification.
  • a stale or transformed unsorted control query can make the component observe that a misspelling, alias, absent custom schema or version mismatch affects the sort key.

The strongest hypothesis for this HRESULT must account for the operation—looking up a key inside the sort specification—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.

Developer evidence

  • compare failing and known-good values for sort token under the same provider or handler version.
  • record the source and normalization path of canonical mapping, not only its display form.
  • use catalog version to test whether the failure belongs to parsing, execution, indexing or capability negotiation.
  • preserve sort eligibility before objects or work items are released.
  • associate unsorted control query with the exact UTC timestamp and correlation identifier.
  • compare failing and known-good values for final parser input bytes under the same provider or handler version.

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.

Disciplined troubleshooting

  1. Capture sort token and canonical mapping at the call boundary that returns this result.
  2. confirm the operation reached looking up a key inside the sort specification with the intended catalog version.
  3. perform the decisive check: prove the base query succeeds without sorting and resolve the key against target schema.
  4. reduce the case until changing sort eligibility alone changes the HRESULT or proves it irrelevant.
  5. apply the recovery only after verifying unsorted control query; 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.

Retry conditions

Use a canonical sortable property or an explicit product-approved fallback. 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.

Misleading assumptions

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.

Related query outcomes

QPARSE_E_INVALID_SORT_ORDER rejects only the direction token. 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.

Concrete troubleshooting case

A query sorts by the UI alias `Name`; retaining canonical System.ItemName in the sort clause fixes lookup. 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.