Error code search

The specified ResourceManager object could not be opened, because it was not found.

The specified Enlistment object could not be opened, because it was not found.

The specified TransactionManager object could not be opened, because it was not found.

The object specified could not be created or opened, because its associated TransactionManager is not online. The TransactionManager must be brought fully Online by calling RecoverTransactionManager to recover to the end of its LogFile before objects in its Transaction or ResourceManager namespaces can be opened. In addition, errors in writing records to its LogFile can cause a TransactionManager to go offline.

The specified TransactionManager was unable to create the objects contained in its logfile in the Ob namespace. Therefore, the TransactionManager was unable to recover.

The call to create a superior Enlistment on this Transaction object could not be completed, because the Transaction object specified for the enlistment is a subordinate branch of the Transaction. Only the root of the Transaction can be enlisted on as a superior.

Because the associated transaction manager or resource manager has been closed, the handle is no longer valid.

The specified operation could not be performed on this Superior enlistment, because the enlistment was not created with the corresponding completion response in the NotificationMask.

The specified operation could not be performed, because the record that would be logged was too long. This can occur because of two conditions: either there are too many Enlistments on this Transaction, or the combined RecoveryInformation being logged on behalf of those Enlistments is too long.

Implicit transaction are not supported.

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 log file.

This snapshot operation cannot continue because a transactional resource manager cannot be frozen in its current state. Please try again.

The transaction cannot be enlisted on with the specified EnlistmentMask, because the transaction has already completed the PrePrepare phase. In order to ensure correctness, the ResourceManager must switch to a write- through mode and cease caching data within this transaction. Enlisting for only subsequent transaction phases may still succeed.

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 did not commit successfully due to heuristics. Therefore it is possible that some data modified in the transaction may not have committed, resulting in transactional inconsistency. If possible, check the consistency of the associated data.

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 Rollback.

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 savepoint rollback.

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 file or an open handle when the transaction ended or rolled back to savepoint.

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 transaction.

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

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