| Previous | Next |
| STATUS_TRANSACTION_RESPONSE_NOT_ENLISTED | STATUS_NO_LINK_TRACKING_IN_TRANSACTION |
STATUS_TRANSACTION_RECORD_TOO_LONG
STATUS_TRANSACTION_RECORD_TOO_LONG means that the record KTM would log for the transaction is too large. For STATUS_TRANSACTION_RECORD_TOO_LONG, the documented causes are too many enlistments on one transaction or recovery information whose combined size is too large.
This is not the same as a full CLFS log. Increasing a log file does not necessarily make one overlong transaction record valid. The diagnostic boundary is the number of enlisted participants and the amount of recovery data each one contributes.
The transaction’s recovery record exceeds KTM’s allowed size
- Measure enlistment count and the size of recovery information per resource manager before the failing phase.
- Reduce or externalize recovery metadata only where the resource manager’s recovery design remains correct and durable.
- Split an oversized unit of work into independent transactions only when the application can preserve its intended atomicity semantics.
References for STATUS_TRANSACTION_RECORD_TOO_LONG
- Microsoft: KTM transaction managers and recovery
- Microsoft: creating a KTM resource manager
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.