| Previous | Next |
| ERROR_HEURISTIC_DAMAGE_POSSIBLE | ERROR_RM_NOT_ACTIVE |
ERROR_TRANSACTIONAL_CONFLICT
Another transaction owns the name transition that this operation needs
ERROR_TRANSACTIONAL_CONFLICT is a Transactional NTFS (TxF) file-system status. TxF isolates uncommitted namespace changes as well as file contents. A transaction can create, rename, or delete a path while another caller still sees the last committed namespace. This error is returned when an operation attempts to use a name whose transactional state is already reserved by a different transaction. It is more specific than a normal sharing violation because the conflict is tied to an unresolved transactional namespace change.
Record the transaction IDs and the exact source and destination names involved in create, rename, link, or delete operations. Look for long-running transactions that keep a rename or deletion uncommitted, and for retry code that starts a second transaction against the same target name. The useful fix is to shorten or serialize the conflicting transaction or wait for its outcome. Changing ACLs or repeatedly reopening the path outside the transaction does not remove the reserved transactional name.
What to inspect
- Capture both the path and transaction ID for every transactional namespace operation.
- Check for a pending rename or delete that reserves the same destination name.
- Serialize conflicting updates or wait for the owning transaction to commit or roll back.
References
- Microsoft: TxF isolation, locking, and file views
- Microsoft: transacted file handles and transaction binding
- Microsoft: listing files locked by a transaction
Looking for a different code? Search another status or error code.