| 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. The documented description is “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.
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.
Evidence to preserve
- Preserve sink identity.
- Preserve resources changed.
- Preserve before and after versions.
- Preserve protocol phase.
- Preserve final transaction decision.
Difference from nearby results
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 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.
References
- Microsoft: COM transaction status codes — official Microsoft material relevant to this HRESULT.
- Microsoft: ITransaction::Commit
- Microsoft: ITransaction::Abort
- Microsoft: HRESULT values
Looking for a different code? Search another status or error code.