| Previous | Next |
| XACT_S_ASYNC | XACT_S_READONLY |
XACT_S_DEFECT
Transaction API returned the reserved XACT_S_DEFECT status
XACT_S_DEFECT is HRESULT 315393 (0x0004D001) from winerror.h. AllStat describes it as “this result.” 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 it. 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 owning API and implementation define the meaning because Microsoft’s public status table provides no semantic expansion beyond the symbolic constant. 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
- It 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 interface and method name.
- preserve transaction state before and after.
- preserve component version.
- preserve resource enlistments.
- preserve coordinator trace around the return.
Also record xact_s_defect_operation, xact_s_defect_state_before, xact_s_defect_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
Preserve the exact method, implementation version, and transaction state. Do not invent a retry or commit interpretation; escalate with a minimal reproduction and coordinator traces.
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 legacy transaction sink returns it during a compatibility test. The team records the interface call and implementation build and avoids mapping it to an unrelated failure.
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.