| Previous | Next |
| ERROR_TRANSACTION_INTEGRITY_VIOLATED | ERROR_RM_CANNOT_BE_FROZEN_FOR_SNAPSHOT |
ERROR_TRANSACTIONMANAGER_IDENTITY_MISMATCH
This status reports an identity mismatch between the Transaction Manager supplied by the caller and the identity recorded in the manager's log. It is a protection against attaching a log to the wrong manager identity, not a transient busy condition.
Situations worth investigating
- A log file was restored, copied, or reused with configuration intended for a different Transaction Manager.
- Deployment automation changed the identity input while retaining an earlier log.
- A test environment reused persistent KTM state across independent instances.
- The application mixed a newly created manager with a log that belongs to an existing one.
Preserve the log and collect its path, configured identity, and deployment history before deleting or reinitializing anything. The right correction is to pair the original identity with its own log or deliberately create a fresh manager and fresh log for a new identity.
See OpenTransactionManager, RecoverTransactionManager, and the WinError definition.
Looking for a different code? Search another status or error code.