| Previous | Next |
| ERROR_RM_ALREADY_STARTED | ERROR_CANT_BREAK_TRANSACTIONAL_DEPENDENCY |
ERROR_FILE_IDENTITY_NOT_PERSISTENT
TxF cannot give the file a stable transactional identity until another transaction resolves
ERROR_FILE_IDENTITY_NOT_PERSISTENT is a Transactional NTFS (TxF) file-system status. TxF isolates namespace and file changes made by active transactions. A file created, renamed, or otherwise transformed by an unresolved transaction can have an identity whose final meaning depends on commit versus rollback. This status prevents another transactional open from treating that contingent identity as stable.
Find the transaction that currently owns the file or namespace change. FSCTL_TXFS_GET_METADATA_INFO can report TxF metadata and the GUID of the locking transaction when the file is locked. Correlate that transaction with pending rename, create, or delete work and wait for a durable outcome. Repeated opens from a second transaction do not make the identity persistent. If the application needs concurrency, redesign the name publication step so other transactions consume only committed identities.
What to inspect
- Query TxF metadata and capture the transaction GUID associated with the file.
- Trace transactional create, rename, and delete operations affecting the path.
- Expose the file to independent transactional work only after its owning transaction resolves.
References
- Microsoft: retrieving TxF metadata and locking transaction
- Microsoft: TxF isolation, locking, and file views
- Microsoft: listing files locked by a transaction
- Microsoft: transacted file handles and transaction binding
Looking for a different code? Search another status or error code.