| Previous | Next |
| DB_S_COLUMNTYPEMISMATCH | DB_S_BOOKMARKSKIPPED |
DB_S_TYPEINFOOVERRIDDEN
OLE DB caller metadata overrode parameter type information
DB_S_TYPEINFOOVERRIDDEN is HRESULT 265922 (0x00040EC2) from Microsoft OLE DB. AllStat describes this result as “Parameter type information was overridden by caller.” The high-order severity bit is clear, so this is a success result, but it carries more information than plain S_OK.
The command accepted caller-supplied parameter type information and used it instead of the provider’s inferred or original metadata.
Where the result is encountered
- This result can appear in ICommandWithParameters parameter setup; record the producing interface and method rather than inferring behavior from the symbolic name alone.
- This result can appear in stored procedure calls; record the producing interface and method rather than inferring behavior from the symbolic name alone.
- It can appear in providers that allow consumers to specify DBPARAMBINDINFO; 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.
State boundary that must be proved
The central question for it is whether the override matches the server parameter contract and does not cause truncation, coercion, or plan changes the caller did not intend. 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.
Evidence and telemetry to preserve
- preserve parameter ordinal and name.
- preserve original and overridden DBTYPE.
- preserve size, precision, scale, and flags.
- preserve binding structure.
- preserve server-side parameter metadata and execution result.
Also record db_s_typeinfooverridden_operation, db_s_typeinfooverridden_object, db_s_typeinfooverridden_state_before, db_s_typeinfooverridden_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.
Correct handling, retry, and recovery
Treat the override as part of the command contract. Validate it against the data source and remove unnecessary overrides that mask metadata drift.
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.
Diagnostic sequence
- capture the raw HRESULT
0x00040EC2immediately 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: the override matches the server parameter contract and does not cause truncation, coercion, or plan changes the caller did not intend.
- 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.
Practical validation scenario
A provider infers a string parameter while the procedure expects a fixed binary token. The consumer supplies binary metadata, records the warning, and verifies exact bytes reach the procedure.
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.
Difference from nearby HRESULT values
DB_S_COLUMNTYPEMISMATCH concerns column copying; it concerns parameter metadata chosen before execution.
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 265922, hexadecimal 0x00040EC2, the AllStat meaning, the owning API, and the first detailed status or output that explains why the method did not return ordinary S_OK.
References
Looking for a different code? Search another status or error code.