| Previous | Next |
| XACT_S_LOCALLY_OK | CO_S_NOTALLINTERFACES |
XACT_S_LASTRESOURCEMANAGER
Resource requests last-resource-manager coordination
XACT_S_LASTRESOURCEMANAGER is HRESULT 315408 (0x0004D010) from winerror.h. The documented description is “The resource manager has requested to be the coordinator (last resource manager) for the transaction.” 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 resource manager has requested to be the coordinator (last resource manager) for the transaction. Consumers of it must decide from the API contract whether to stop, wait, continue, or expose a reduced outcome.
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.
Evidence to preserve
- Preserve requesting resource manager.
- Preserve other enlistments and capabilities.
- Preserve last-resource policy.
- Preserve prepare and commit ordering.
- Preserve recovery record location.
What must be true before accepting it
Verify that the transaction manager accepts the one-phase resource role without creating multiple uncoordinated last resources. Checking the boundary keeps it from hiding stale data, pending work, or a deliberately reduced result.
Do not compensate until the caller knows which sub-operations actually occurred.
Correct handling and recovery
Verify policy permits the last-resource optimization, ensure only one such resource exists, and record the recovery implications before proceeding.
Continuation after it may be appropriate, but an identical restart is not automatically recovery.
Difference from nearby results
Practical scenario
A transactional system combines a durable two-phase database with one legacy one-phase queue. The queue requests last-resource-manager status and the coordinator validates exclusivity.
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.