| Previous | Next |
| DB_S_LOCKUPGRADED | DB_S_ERRORSOCCURRED |
DB_S_PROPERTIESCHANGED
OLE DB provider adjusted requested properties
DB_S_PROPERTIESCHANGED is HRESULT 265945 (0x00040ED9) from Microsoft OLE DB. AllStat describes this result as “One or more properties were changed as allowed by provider.” The high-order severity bit is clear, so this is a success result, but it carries more information than plain S_OK.
One or more properties were changed to values permitted by the provider rather than applied exactly as requested.
Evidence and telemetry to preserve
- preserve property set GUID and property IDs.
- preserve requested values and options.
- preserve DBPROPSTATUS values.
- preserve effective properties.
- preserve provider version and initialization phase.
Also record db_s_propertieschanged_operation, db_s_propertieschanged_object, db_s_propertieschanged_state_before, db_s_propertieschanged_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.
Where the result is encountered
- This result can appear in IDBProperties or rowset property negotiation; record the producing interface and method rather than inferring behavior from the symbolic name alone.
- This result can appear in initialization settings; record the producing interface and method rather than inferring behavior from the symbolic name alone.
- It can appear in requests containing optional and required property values; 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 caller inspects each property status and reads back effective values before using the object. 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.
Diagnostic sequence
- capture the raw HRESULT
0x00040ED9immediately 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 caller inspects each property status and reads back effective values before using the object.
- 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.
Difference from nearby HRESULT values
DB_S_GOALCHANGED identifies a clamped goal or weight; it is the general property-adjustment result.
This distinction determines whether the caller should consume partial outputs, stop iteration, wait, reconfigure, notify the user, or perform no error recovery at all.
Correct handling, retry, and recovery
Accept only changes compatible with the application. Fail early for required properties; adapt optional behavior to the effective values.
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.
Practical validation scenario
A rowset requests bookmarks and a specific cursor behavior. The provider adjusts one optional property; the consumer reads back both values and disables bookmark-based UI when unsupported.
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.
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 265945, hexadecimal 0x00040ED9, 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.