What does HRESULT 0x80041609 (QUERY_E_INVALID_OUTPUT_COLUMN) mean?

 
Previous Next
QUERY_E_DUPLICATE_OUTPUT_COLUMN QUERY_E_INVALID_DIRECTORY

QUERY_E_INVALID_OUTPUT_COLUMN

An output column is unknown or unusable

QUERY_E_INVALID_OUTPUT_COLUMN is the failure HRESULT 0x80041609 (-2147215863 signed; 2147751433 unsigned). Its severity bit is 1, facility is 4 (FACILITY_ITF), and code is 0x1609. AllStat describes it as “One or more columns in the output column list is not valid.”

Interpretation

This result belongs to legacy Windows query execution and is returned while resolving selected properties into the rowset schema. The exact condition is: a misspelled, unavailable, unsupported or incorrectly aliased projection property. 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.

Concrete sources

  • Retrying this result with the same exact projection order leaves the decisive contract violation intact.
  • This result can appear when canonical property mapping disagrees with the state expected while resolving selected properties into the rowset schema.
  • a stale or transformed target schema version can make the component observe that a misspelled, unavailable, unsupported or incorrectly aliased projection property.
  • an incomplete single-column reproducer hides the distinction needed to separate this HRESULT from a later catalog or service failure.
  • changes in output accessor bindings between validation and execution can reproduce the result even when the user-visible input looks unchanged.

The strongest hypothesis for this HRESULT must account for the operation—resolving selected properties into the rowset schema—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.

Observability checklist

  • use exact projection order to test whether the failure belongs to parsing, execution, indexing or capability negotiation.
  • preserve canonical property mapping before objects or work items are released.
  • associate target schema version with the exact UTC timestamp and correlation identifier.
  • compare failing and known-good values for single-column reproducer under the same provider or handler version.
  • record the source and normalization path of output accessor bindings, not only its display form.
  • use provider command text and dialect to test whether the failure belongs to parsing, execution, indexing or capability negotiation.

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.

Investigation order

  1. Capture exact projection order and canonical property mapping at the call boundary that returns this result.
  2. confirm the operation reached resolving selected properties into the rowset schema with the intended target schema version.
  3. perform the decisive check: start with one known-good column and add requested properties until the invalid identity is isolated.
  4. reduce the case until changing single-column reproducer alone changes the HRESULT or proves it irrelevant.
  5. apply the recovery only after verifying output accessor bindings; 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.

Corrective action

Replace the name with a canonical supported property and rebuild accessors for the final order. 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.

What must not be inferred

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.

Neighboring status codes

QUERY_E_DUPLICATE_OUTPUT_COLUMN concerns repetition and QPARSE_E_NO_SUCH_PROPERTY is a parser-level lookup failure. 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.

Reproduction example

A client requests a modern property name from a legacy catalog. A one-column test exposes the unsupported projection without reindexing. 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.