ERROR_ENLISTMENT_NOT_FOUND - 6717 (0x1A3D)

The specified Enlistment object could not be opened, because it was not found.

Updated: Feb 21, 2026

Technical Meaning

The ERROR_ENLISTMENT_NOT_FOUND error indicates that a transaction enlistment object could not be opened because it does not exist. This error is typically encountered in the context of distributed transactions managed by the Windows Transaction Manager.

Error Details

This error code, 6717 (0x1A3D), signifies that an attempt to access or open a transaction enlistment object failed due to its non-existence. Enlistments are components within a distributed transaction that participate in the transaction's lifecycle by committing or rolling back changes.

Usage Context

This error is commonly encountered when working with distributed transactions, particularly when attempting to enlist resources such as databases or file systems into a transaction managed by the Transaction Manager (TM). The TM uses enlistments to coordinate and manage the transactional behavior of various components involved in the transaction.

Developer Interpretation

When this error occurs, it indicates that the specified enlistment object does not exist. This could be due to several reasons such as incorrect object identifiers, misconfiguration, or issues with the underlying resources. Developers should ensure that all necessary objects are correctly configured and available before attempting to open them.

Related Errors

FAQ

Q: What does the ERROR_ENLISTMENT_NOT_FOUND error mean?

A: It indicates that a transaction enlistment object could not be opened because it was not found. This typically occurs in distributed transactions managed by the Transaction Manager.

Q: How can I resolve this issue?

A: Ensure that all necessary objects are correctly configured and available before attempting to open them. Verify the correctness of identifiers and configurations related to transaction enlistments.

Summary

The ERROR_ENLISTMENT_NOT_FOUND error (6717) is a specific technical error indicating that an attempt to access or open a transaction enlistment object failed due to its non-existence. Developers should ensure proper configuration and availability of objects involved in distributed transactions managed by the Transaction Manager.