| Previous | Next |
| ERROR_SPARSE_NOT_ALLOWED_IN_TRANSACTION | ERROR_FLOATED_SECTION |
ERROR_TM_IDENTITY_MISMATCH
The durable KTM log belongs to a different transaction manager identity
ERROR_TM_IDENTITY_MISMATCH belongs to the Windows Kernel Transaction Manager transaction-processing model. Durable transaction managers pair coordinator identity with persistent log state. The identity lets KTM and resource managers distinguish one transaction manager from another across recovery. If the TM identifier supplied during creation does not match the identifier stored in the log, opening that log under the new identity would attach recovery records to the wrong coordinator.
Treat this as evidence of log or configuration mismatch. Check restores, image cloning, copied log directories, service reinstallations, and code that generates a new TM GUID while reusing an existing log path. Record both identities before changing anything. Do not overwrite the stored identity or delete the log merely to start the service until outstanding transactions and RM associations are understood; the old log may contain recovery state that belongs to the original TM.
What to inspect
- Capture the supplied TM ID and the identity reported for the existing log.
- Review clone, restore, migration, and service-recreation history.
- Reassociate the correct TM and log or perform an owner-supported recovery; do not force identity replacement.
References
- Microsoft: transaction managers and durable logs
- Microsoft: creating and recovering a KTM resource manager
- Microsoft: KTM recovery processing and presumed abort
- Microsoft: KTM resource-manager log streams and recovery
Looking for a different code? Search another status or error code.