| Previous | Next |
| ERROR_FLOATED_SECTION | ERROR_CANNOT_ABORT_TRANSACTIONS |
ERROR_CANNOT_ACCEPT_TRANSACTED_WORK
The RM is alive but applying backpressure to new transactions
ERROR_CANNOT_ACCEPT_TRANSACTED_WORK belongs to the Windows Kernel Transaction Manager transaction-processing model. This status describes a transient resource-manager capacity or state condition. The RM has not necessarily lost its durable metadata or disconnected from KTM, but it cannot safely take additional transacted work at that moment. Examples in the system message include low resources; outstanding recovery or log pressure can also be relevant depending on the RM implementation.
Measure the RM state before retrying: active transaction count, notification backlog, log capacity, memory or handle pressure, and recovery activity. Apply bounded backoff and preserve the original transaction outcome semantics. A tight retry loop can deepen the resource shortage. If the condition persists, find the first RM-specific warning or event and determine whether the manager is approaching a shutdown condition such as failure to abort outstanding transactions.
What to inspect
- Capture RM resource metrics and transaction backlog at the first rejection.
- Use bounded retry with backoff only when the operation is safe to replay.
- Investigate sustained rejection as an RM health problem, not a client parameter error.
References
- Microsoft: creating and recovering a KTM resource manager
- Microsoft: KTM transaction notifications
- Microsoft: transactional resource manager and log management
- Microsoft: KTM recovery processing and presumed abort
Looking for a different code? Search another status or error code.