| Previous | Next |
| ERROR_IMPLICIT_TRANSACTION_NOT_SUPPORTED | ERROR_TRANSACTIONMANAGER_IDENTITY_MISMATCH |
ERROR_TRANSACTION_INTEGRITY_VIOLATED
The transaction was sacrificed to preserve KTM forward progress and integrity
ERROR_TRANSACTION_INTEGRITY_VIOLATED belongs to the Windows Kernel Transaction Manager transaction-processing model. This is a coordinator-protection condition, not an ordinary application-requested rollback. KTM manages transaction state across resource managers and must be able to drive transactions toward a final outcome. When a transaction blocks forward progress severely enough to violate the manager integrity rules, KTM can abort or forget it rather than allow the transaction system to remain stuck.
Treat the first occurrence as an incident requiring coordinator and RM timeline analysis. Collect transaction notifications, prepare and completion calls, timeouts, resource-manager disconnects, and recovery events for the same transaction ID. A resource manager that receives a notification but never calls the matching completion routine can prevent progression. Do not simply extend application timeouts: determine which participant or superior branch stopped advancing the protocol and whether recovery information is sufficient to reconcile durable data.
What to inspect
- Build a notification and completion timeline for every enlistment in the transaction.
- Identify RMs or superior branches that stopped responding after prepare or outcome notification.
- Check durable data consistency before retrying business work under a new transaction.
References
- Microsoft: KTM transaction notifications
- Microsoft: KTM recovery processing and presumed abort
- Microsoft: KTM transaction, TM, RM, and enlistment functions
- MS-DTCO: superior and subordinate transaction-manager roles
Looking for a different code? Search another status or error code.