| Previous | Next |
| QUERY_E_TIMEDOUT | QUERY_E_INVALID_OUTPUT_COLUMN |
QUERY_E_DUPLICATE_OUTPUT_COLUMN
The projection contains a duplicate output column
QUERY_E_DUPLICATE_OUTPUT_COLUMN is the failure HRESULT 0x80041608 (-2147215864 signed; 2147751432 unsigned). Its severity bit is 1, facility is 4 (FACILITY_ITF), and code is 0x1608. AllStat describes it as “One or more columns in the output column list is a duplicate.”
Operation and state
This result belongs to legacy Windows query execution and is returned while validating the SELECT/output schema returned in each rowset row. The exact condition is: the same canonical property identity appearing more than once, possibly through aliases or reused fragments. 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 belongs to the legacy Indexing Service query-execution contract. It can surface through the Indexing Service OLE DB provider or related query interfaces, but it should not be presented as a generic result from every modern Windows Search API. Current Windows Search SQL documentation can clarify related clause concepts, but it does not establish that every current search API returns this legacy query-execution constant.
Failure paths to examine
- changes in ordered projection between validation and execution can reproduce the result even when the user-visible input looks unchanged.
- Retrying this result with the same canonical identities leaves the decisive contract violation intact.
- This result can appear when aliases disagrees with the state expected while validating the SELECT/output schema returned in each rowset row.
- a stale or transformed contributing query fragment can make the component observe that the same canonical property identity appearing more than once, possibly through aliases or reused fragments.
- an incomplete accessor ordinal layout hides the distinction needed to separate this HRESULT from a later catalog or service failure.
The strongest hypothesis for this HRESULT must account for the operation—validating the SELECT/output schema returned in each rowset row—and the documented condition. A failed command or empty rowset is only the visible symptom; it does not identify which restriction, projection, sort, scope, timeout or catalog state violated the query contract.
Data to collect first
- record the source and normalization path of ordered projection, not only its display form.
- use canonical identities to test whether the failure belongs to parsing, execution, indexing or capability negotiation.
- preserve aliases before objects or work items are released.
- associate contributing query fragment with the exact UTC timestamp and correlation identifier.
- compare failing and known-good values for accessor ordinal layout under the same provider or handler version.
- record the source and normalization path of provider command text and dialect, not only its display form.
Evidence for this HRESULT should reflect what the component actually received. Redact private literals if necessary, but keep clause boundaries, canonical properties, parameter types, dialect and parser or provider offsets.
Step-by-step diagnosis
- Capture ordered projection and canonical identities at the call boundary that returns this result.
- confirm the operation reached validating the SELECT/output schema returned in each rowset row with the intended aliases.
- perform the decisive check: canonicalize every requested property and trace which query fragment contributed each occurrence.
- reduce the case until changing contributing query fragment alone changes the HRESULT or proves it irrelevant.
- apply the recovery only after verifying accessor ordinal layout; preserve the original result for comparison.
A useful control for this HRESULT changes one dimension at a time. Begin with a known-good minimal command against the same catalog and restore projection, restriction, sorting, grouping and scope one component at a time.
Continuation policy
Keep one authoritative column and update ordinal-based bindings deliberately. Retry it only after the responsible input or state changes and the previous operation has completed or been cancelled. Backoff helps only with measured transient load or timeout; it cannot repair invalid clauses, projection metadata, scopes or command state.
Limits of this HRESULT
It does not by itself prove catalog corruption, service outage, access denial or absence of matches; the query stage and provider records must identify the failing clause or state. Without code-specific evidence for this HRESULT, the value also cannot identify which wrapper, configuration, handler or service transition introduced the condition.
Distinguishing similar results
QUERY_E_INVALID_OUTPUT_COLUMN rejects an unknown or unsupported identity; this value rejects repetition. 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 command text, dialect, catalog generation, parameter values, timeout, cancellation state and chained OLE DB error records. Do not log credentials or unrestricted document content. Before rebuilding the catalog or restarting the provider for this HRESULT, reproduce the minimal command and preserve its chained errors.
Operational case
A default projection and a caller template both add the item URL under different aliases. Canonical identity comparison removes the duplicate safely. 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
- Microsoft: Indexing Service query-execution values
- Microsoft: Windows Search SQL syntax
- Microsoft: OLE DB provider for Indexing Service
- Microsoft: HRESULT values
Looking for a different code? Search another status or error code.