| Previous | Next |
| XACT_S_OKINFORM | XACT_S_MADECHANGESINFORM |
XACT_S_MADECHANGESCONTENT
Transaction sink made changes and is content
XACT_S_MADECHANGESCONTENT is HRESULT 315397 (0x0004D005) from winerror.h. AllStat describes it as “The sink is content and wishes the transaction to proceed; Changes were made to one or more resources during this call.” The severity bit indicates a nonfailure result, but the value carries a specific condition that must not be collapsed into plain S_OK.
In the COM transaction and MSDTC protocol, this result means that the sink is content and wishes the transaction to proceed; Changes were made to one or more resources during this call. The high-level request can be considered complete after it only when its documented postcondition has been checked.
Where the status is encountered
- ITransaction commit or abort processing; log the exact method and object state instead of interpreting the constant outside that contract.
- Resource-manager enlistment and coordinated outcomes; log the exact method and object state instead of interpreting the constant outside that contract.
- Transaction event-sink notification passes; log the exact method and object state instead of interpreting the constant outside that contract.
Because it is informational, a language binding may expose it as success and hide the symbolic distinction. Keep the original HRESULT available until the code-specific branch has run.
What must be true before accepting it
Verify that the sink’s changes are included and it does not require another review pass. The verification prevents it from being promoted to broader success than the producing API promised.
The component may have changed durable or in-memory state before returning it; inspect that state first.
Evidence and telemetry
- preserve sink identity.
- preserve resources changed.
- preserve before and after versions.
- preserve protocol phase.
- preserve final transaction decision.
Also record xact_s_madechangescontent_operation, xact_s_madechangescontent_state_before, xact_s_madechangescontent_state_after, UTC time, process and thread identifiers, component version, and a correlation ID. Protect user data in logs and keep only the identifiers required to reproduce component state.
Difference from nearby results
It must be distinguished from ordinary S_OK and from failure-severity values in the same API family; its documented state changes control the next action.
The nearby-status comparison controls whether outputs are usable and whether more work is expected.
Correct handling and recovery
Record the modified resources and proceed with the protocol. Revalidation is needed only if the transaction contract or another failure invalidates those changes.
Retry it only when a documented input or state has changed. Retry policy must follow the owning state machine rather than a generic transient-error loop.
Practical scenario
A normalization sink updates one enlisted resource and returns content. The coordinator proceeds without recalling that sink, while audit logs retain the exact modification.
A regression test should reproduce it, assert the relevant outputs and state, then change only the decisive condition and verify the expected neighboring result or ordinary completion.
References
- Microsoft: COM transaction status codes — official Microsoft material used to interpret it.
- Microsoft: ITransaction::Commit
- Microsoft: ITransaction::Abort
- Microsoft: HRESULT values
Looking for a different code? Search another status or error code.