| Previous | Next |
| QUERY_E_INVALIDSCOPE_COALESCE | QUERY_E_INVALIDCOALESCE |
QUERY_E_INVALIDSORT_COALESCE
QUERY_E_INVALIDSORT_COALESCE means the coalesced query components disagree on sort order. The engine requires the same ORDER BY list across components so combined rows have one deterministic ordering definition.
Compare normalized ORDER BY clauses component by component
- Log column names or ordinals, direction, and column order for every component.
- Remember that Windows Search applies the last specified direction to subsequent columns until another direction is stated.
- Generate one canonical sort list and apply it to all coalesced components before submission.
Windows Search ORDER BY supports multiple columns and one-based projection ordinals. Semantically equivalent-looking sort strings can still differ if directions or column order are not normalized. If components genuinely need different sort policies, combine their results outside the coalesce query. Rebuilding the catalog cannot reconcile conflicting ordering clauses.
ORDER BY clause · Legacy query errors · Windows Search SQL overview
Looking for a different code? Search another status or error code.