The kernel transaction manager had to abort or forget the transaction because it blocked forward progress.

The TransactionManager identity that was supplied did not match the one recorded in the TransactionManager's l

This snapshot operation cannot continue because a transactional resource manager cannot be frozen in its curre

The transaction cannot be enlisted on with the specified EnlistmentMask, because the transaction has already c

The transaction does not have a superior enlistment.

The attempt to commit the Transaction completed, but it is possible that some portion of the transaction tree

The function attempted to use a name that is reserved for use by another transaction.

Transaction support within the specified resource manager is not started or was shut down due to an error.

The metadata of the RM has been corrupted. The RM will not function.

The specified directory does not contain a resource manager.

The remote server or share does not support transacted file operations.

The requested log size is invalid.

The object (file, stream, link) corresponding to the handle has been deleted by a Transaction Savepoint Rollba

The specified file miniversion was not found for this transacted file open.

The specified file miniversion was found but has been invalidated. Most likely cause is a transaction savepoin

A miniversion may only be opened in the context of the transaction that created it.

It is not possible to open a miniversion with modify access.

It is not possible to create any more miniversions for this stream.

The remote server sent mismatching version number or Fid for a file opened with transactions.

The handle has been invalidated by a transaction. The most likely cause is the presence of memory mapping on a

There is no transaction metadata on the file.

The log data is corrupt.

The file can't be recovered because there is a handle still open on it.

The transaction outcome is unavailable because the resource manager responsible for it has disconnected.

The request was rejected because the enlistment in question is not a superior enlistment.

The transactional resource manager is already consistent. Recovery is not needed.

The transactional resource manager has already been started.

The file cannot be opened transactionally, because its identity depends on the outcome of an unresolved transa

The operation cannot be performed because another transaction is depending on the fact that this property will

The operation would involve a single file with two transactional resource managers and is therefore not allowe

The $Txf directory must be empty for this operation to succeed.

The operation would leave a transactional resource manager in an inconsistent state and is therefore not allow

The operation could not be completed because the transaction manager does not have a log.

A rollback could not be scheduled because a previously scheduled rollback has already executed or been queued

The transactional metadata attribute on the file or directory is corrupt and unreadable.

The encryption operation could not be completed because a transaction is active.

This object is not allowed to be opened in a transaction.

An attempt to create space in the transactional resource manager's log failed. The failure status has been rec

Memory mapping (creating a mapped section) a remote file under a transaction is not supported.

Transaction metadata is already present on this file and cannot be superseded.

A transaction scope could not be entered because the scope handler has not been initialized.

Promotion was required in order to allow the resource manager to enlist, but the transaction was set to disall

This file is open for modification in an unresolved transaction and may be opened for execute only by a transa

The request to thaw frozen transactions was ignored because transactions had not previously been frozen.

Transactions cannot be frozen because a freeze is already in progress.

The target volume is not a snapshot volume. This operation is only valid on a volume mounted as a snapshot.

The savepoint operation failed because files are open on the transaction. This is not permitted.

Windows has discovered corruption in a file, and that file has since been repaired. Data loss may have occurre

The sparse operation could not be completed because a transaction is active on the file.

The call to create a TransactionManager object failed because the Tm Identity stored in the logfile does not m