| Previous | Next |
| DB_S_ASYNCHRONOUS | DB_S_ERRORSRETURNED |
DB_S_COLUMNSCHANGED
OLE DB rowset columns changed during repositioning
DB_S_COLUMNSCHANGED is HRESULT 265937 (0x00040ED1) from Microsoft OLE DB. AllStat describes this result as “Command was executed to reposition to the start of the rowset; Either the order of the columns changed, or columns were added to or removed from the rowset.” The high-order severity bit is clear, so this is a success result, but it carries more information than plain S_OK.
The provider reexecuted or repositioned the command and the rowset column order or membership changed.
Where the result is encountered
- This result can appear in scrolling or restarting a rowset; record the producing interface and method rather than inferring behavior from the symbolic name alone.
- This result can appear in commands whose metadata can vary; record the producing interface and method rather than inferring behavior from the symbolic name alone.
- It can appear in providers reexecuting schema-sensitive queries; record the producing interface and method rather than inferring behavior from the symbolic name alone.
The same numeric success value can be mishandled when a wrapper exposes only a Boolean. Keep the original HRESULT until the code-specific outputs and state transition have been evaluated.
Diagnostic sequence
- capture the raw HRESULT
0x00040ED1immediately after the returning method and record whether the caller usedSUCCEEDED,FAILED, equality testing, or exception translation. - Identify the exact owner of it: interface, method, object instance, provider or filter version, thread or apartment, and operation phase.
- Validate the decisive contract boundary for it: all ordinal-based bindings and cached metadata are rebuilt before the consumer reads the new rowset layout.
- inspect every output parameter, count, status array, returned interface, or side effect that the method documentation associates with this success-with-information result.
- Compare the observed state before and after it; do not assume that a success severity bit means every optional sub-operation completed.
- reproduce the smallest request with the same object state and then change only the condition identified by the evidence before repeating the operation.
State boundary that must be proved
The central question for it is whether all ordinal-based bindings and cached metadata are rebuilt before the consumer reads the new rowset layout. The HRESULT alone confirms neither unrelated work nor the quality of optional outputs.
A reliable interpretation of it names the exact method contract, the object generation, and the outputs that remain valid. This prevents a success-with-information result from being promoted to full success or demoted to a generic error.
Correct handling, retry, and recovery
Release or rebuild accessors against the new metadata. Continuing with stale ordinals can corrupt interpretation even though the HRESULT is a success value.
Retry it only when the recorded state can change the documented outcome. Repeating the same call is inappropriate for a stable end marker, cancellation, unsupported format, adjusted property, or partial result whose completed side effects have not been reconciled.
Evidence and telemetry to preserve
- preserve old and new IColumnsInfo metadata.
- preserve binding ordinals and accessors.
- preserve command execution generation.
- preserve schema version.
- preserve rows fetched before and after the change.
Also record db_s_columnschanged_operation, db_s_columnschanged_object, db_s_columnschanged_state_before, db_s_columnschanged_state_after, UTC time, process and thread identifiers, and a correlation ID. Keep secrets out of logs while retaining GUIDs, CLSIDs, media subtypes, property IDs, row identities, and hashes needed to distinguish objects.
Difference from nearby HRESULT values
DB_S_COMMANDREEXECUTED describes reexecution; it identifies the resulting metadata change that requires consumer action.
This distinction determines whether the caller should consume partial outputs, stop iteration, wait, reconfigure, notify the user, or perform no error recovery at all.
Developer and administrator guidance
Application telemetry should separate terminal failure, ordinary success, partial completion, continuation, cancellation, and warning-like success. Support bundles should contain the smallest reproducible call and the effective configuration seen by the owning component.
A support report for it should include decimal 265937, hexadecimal 0x00040ED1, the AllStat meaning, the owning API, and the first detailed status or output that explains why the method did not return ordinary S_OK.
Practical validation scenario
A query uses a provider-specific dynamic projection. After repositioning, a new column appears; the consumer discards old accessors, rebuilds by column identity, and resumes safely.
The negative test should preserve the condition that produces it; the recovery test should alter only that condition and verify the final state as well as the HRESULT.
References
Looking for a different code? Search another status or error code.