| Previous | Next |
| XACT_S_SINGLEPHASE | XACT_S_LASTRESOURCEMANAGER |
XACT_S_LOCALLY_OK
Local transaction has not aborted
XACT_S_LOCALLY_OK is HRESULT 315402 (0x0004D00A) from winerror.h. AllStat describes it as “The this condition.” 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 this condition. Handling of it is complete only after the caller verifies what work occurred and what remains outstanding.
What must be true before accepting it
Verify that the local resource remains valid while the distributed or coordinating outcome may still require observation. Failure to prove the boundary can make this result look healthy while the intended operation remains unfinished.
Classify the operation phase reached at this result before releasing objects or issuing replacement work.
Where the status is encountered
- This result can be returned during ITransaction commit or abort processing; log the exact method and object state instead of interpreting the constant outside that contract.
- It can be returned during resource-manager enlistment and coordinated outcomes; log the exact method and object state instead of interpreting the constant outside that contract.
- It can be returned during 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.
Evidence and telemetry
- preserve local transaction identifier.
- preserve distributed unit of work.
- preserve local resource state.
- preserve remote participant states.
- preserve coordinator decision.
Also record xact_s_locally_ok_operation, xact_s_locally_ok_state_before, xact_s_locally_ok_state_after, UTC time, process and thread identifiers, component version, and a correlation ID. Keep it traces useful by recording object identity and timing while excluding authentication or content secrets.
Correct handling and recovery
Treat this only as the local state. Continue waiting for the global transaction decision and avoid exposing local success as end-to-end commit.
Retry it only when a documented input or state has changed. Only a meaningful state transition should cause a repeated request after it.
Practical scenario
A bridge reports that the local database has not aborted while a remote resource is still resolving. The service keeps the operation pending until the coordinator decides.
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.
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 semantic difference represented by it should be visible in both control flow and operational metrics.
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.