| Previous | Next |
| STATUS_SPARSE_NOT_ALLOWED_IN_TRANSACTION | STATUS_FLOATED_SECTION |
STATUS_TM_IDENTITY_MISMATCH
The log belongs to a different transaction-manager identity
A durable KTM log is bound to a transaction-manager identity. That binding prevents an unrelated manager from opening another manager's recovery history and interpreting its transactions as its own.
This commonly follows copying or restoring a log without the matching configuration, reusing a path for a newly generated identity, or mixing files from different machines or backup generations. Changing the GUID just to make the call succeed can attach the wrong namespace to the log.
What to inspect
- Record the requested TM identity, the log path, and the identity expected by the deployment configuration.
- Check recent restore, clone, migration, or failover operations.
- Keep the log and all related metadata from one consistent backup generation.
- Use the documented recovery or migration procedure rather than editing identity data.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: transaction manager objects
- Microsoft: using log streams with KTM
- Microsoft Windows SDK metadata: ktmw32.h
Looking for a different code? Search another status or error code.