| Previous | Next |
| FSRM_E_AUTO_QUOTA | XACT_S_DEFECT |
XACT_S_ASYNC
Transaction operation started asynchronously
XACT_S_ASYNC is HRESULT 315392 (0x0004D000) from winerror.h. The documented description is “An asynchronous operation was specified; The operation has begun, but its outcome is not known yet.” 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 an asynchronous operation was specified; The operation has begun, but its outcome is not known yet. Treat it as a distinct branch whose postcondition must be proven before subsequent operations begin.
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 caller waits for the transaction manager’s terminal decision and retains every object required for completion. The caller should make the acceptance test explicit in code and telemetry.
Inspect the current generation of every affected object before deciding what happens next.
Evidence to preserve
- Preserve transaction unit of work.
- Preserve coordinator and resource managers.
- Preserve async completion handle or callback.
- Preserve requested retaining flags.
- Preserve final commit or abort outcome.
Difference from nearby results
Correct handling and recovery
Track the asynchronous completion mechanism, cancellation policy, and final outcome. Never report commit or abort merely because the request was accepted.
Distinguish protocol continuation from retrying the entire high-level operation.
Practical scenario
An application submits an asynchronous commit, persists the transaction identifier, and updates business state only after the coordinator reports the final decision.
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.