| Previous | Next |
| DB_S_GOALCHANGED | DB_S_DIALECTIGNORED |
DB_S_UNWANTEDOPERATION
OLE DB consumer declines further notifications for an operation
DB_S_UNWANTEDOPERATION is HRESULT 265932 (0x00040ECC) from Microsoft OLE DB. AllStat describes this result as “Consumer does not want to receive further notification calls for this operation.” The high-order severity bit is clear, so this is a success result, but it carries more information than plain S_OK.
A notification sink successfully tells the provider that it no longer wants callbacks for the current operation.
Where the result is encountered
- This result can appear in rowset notification callbacks; record the producing interface and method rather than inferring behavior from the symbolic name alone.
- This result can appear in consumer-controlled event suppression; record the producing interface and method rather than inferring behavior from the symbolic name alone.
- It can appear in providers honoring sink return codes during multi-phase operations; 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
0x00040ECCimmediately 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: only the intended operation is suppressed and the provider’s remaining notification contract is understood.
- 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 only the intended operation is suppressed and the provider’s remaining notification contract is understood. 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
Stop callbacks for that operation as requested and maintain any other subscribed notifications. Consumers should return this status deliberately, not as a generic way to ignore errors.
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 notification interface and sink identity.
- preserve operation reason and phase.
- preserve return code history.
- preserve provider behavior after suppression.
- preserve outstanding asynchronous work.
Also record db_s_unwantedoperation_operation, db_s_unwantedoperation_object, db_s_unwantedoperation_state_before, db_s_unwantedoperation_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_UNWANTEDPHASE suppresses a phase, and DB_S_UNWANTEDREASON suppresses a reason; it targets the operation.
This distinction determines whether the caller should consume partial outputs, stop iteration, wait, reconfigure, notify the user, or perform no error recovery at all.
Practical validation scenario
A UI consumer no longer needs row-position notifications for a canceled refresh. It returns it, while retaining schema-change notifications for the rowset.
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.