| Previous | Next |
| ERROR_TRANSACTION_RESPONSE_NOT_ENLISTED | ERROR_IMPLICIT_TRANSACTION_NOT_SUPPORTED |
ERROR_TRANSACTION_RECORD_TOO_LONG
This error means KTM cannot write the required record for the proposed operation. The documented causes are too many enlistments on one transaction or recovery information whose combined size is too large. It is a transaction-log record limit, not simply a lack of free disk space.
Where the size comes from
KTM lets a resource manager store opaque recovery information on behalf of an enlistment. After a failure, the resource manager can retrieve that information to recover its state. Large recovery blobs and a high number of participants both increase the record that KTM must log.
What to measure
- Count resource-manager enlistments for the transaction.
- Measure recovery-information sizes before calling the KTM API that records them.
- Look for an application design that packs unbounded business payloads into recovery data instead of a compact recovery reference.
- Split independent work into separate transactions only when atomicity requirements allow it.
See SetEnlistmentRecoveryInformation, KTM recovery functions, and the WinError definition.
Looking for a different code? Search another status or error code.