ERROR_TRANSACTION_RECORD_TOO_LONG - 6724 (0x1A44)

Technical Background

The ERROR_TRANSACTION_RECORD_TOO_LONG error code indicates that a transaction operation could not be completed due to the size of the log record exceeding system-defined limits. This error is specific to the Windows Transaction Manager and its interaction with distributed transactions.

Error Details

This error occurs when either:

• There are too many Enlistments on this Transaction, leading to an excessively large transaction log record.
• The combined RecoveryInformation being logged for those Enlistments exceeds the maximum allowed size.

Common Causes

• Exceeding the system-defined limit on the number of Enlistments in a single transaction.
• Logging recovery information that is too extensive or complex, leading to oversized records.

Real-World Context

This error typically arises when performing distributed transactions involving multiple resources. Each resource involved in the transaction contributes RecoveryInformation, which can grow significantly depending on the complexity and number of Enlistments.

Is This Error Critical?

The criticality of this error depends on the specific operation being performed. If a transaction is part of a critical system process, it may result in a failure to complete that process. However, for non-critical operations, the impact might be minimal.

How to Diagnose

To diagnose this issue:

1. Review Operation Context: Ensure that the transaction involves a reasonable number of Enlistments and that each Enlistment contributes RecoveryInformation within acceptable limits.
2. Validate Parameters: Check if any parameters related to the transaction are set inappropriately, leading to excessive logging.
3. Confirm Object Types: Verify that all objects involved in the transaction are correctly identified and do not contribute overly large amounts of data.

How to Resolve

To resolve this issue:

• Correct Parameter Usage: Ensure that parameters related to Enlistments and RecoveryInformation are set appropriately.
• Adjust Operation Context: If possible, reduce the number of Enlistments or simplify the recovery information logged for each Enlistment.
• Restore Data: In cases where data corruption is suspected, restore from a backup if available.
• Retry Operation with Valid Inputs: Attempt to perform the transaction again with valid inputs and parameters.

Developer Notes

Developers should be aware of the system limits on transaction size and ensure that their applications handle transactions in a way that avoids exceeding these limits. Proper management of Enlistments and recovery information can prevent this error from occurring.

Related Errors

• ERROR_TRANSACTION_NOT_JOINED (6725, 0x1A45)
• ERROR_TRANSACTION_INTEGRITY (6738, 0x1A9E)

FAQ

Q: What does the ERROR_TRANSACTION_RECORD_TOO_LONG error mean?

A: This error indicates that a transaction operation could not be completed because the log record would exceed system-defined limits.

Q: How can I prevent this error from occurring?

A: Ensure that your application manages Enlistments and recovery information in a way that does not exceed the system-defined limits for transaction size.

Summary

The ERROR_TRANSACTION_RECORD_TOO_LONG error is specific to distributed transactions managed by the Windows Transaction Manager. It occurs when the log record for a transaction exceeds predefined limits due to too many Enlistments or overly complex recovery information. Developers should be mindful of these limitations and manage their applications accordingly to avoid this issue.