The transactional resource manager had too many transactions outstanding that could not be aborted. The transactional resource manager has been shut down.
The specified transaction was unable to be opened because it was not found.
The specified resource manager was unable to be opened because it was not found.
The specified enlistment was unable to be opened because it was not found.
The specified transaction manager was unable to be opened because it was not found.
The specified resource manager was unable to create an enlistment because its associated transaction manager is not online.
The specified transaction manager was unable to create the objects contained in its log file in the Ob namespace. Therefore, the transaction manager 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 as a superior.
The compression operation could not be completed because a transaction is active on the file.
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 to be logged was too long. This can occur because either there are too many enlistments on this transaction or the combined RecoveryInformation being logged on behalf of those enlistments is too long.
The link-tracking operation could not be completed because a transaction is active.
This operation cannot be performed in a transaction.
The kernel transaction manager had to abort or forget the transaction because it blocked forward progress.
The handle is no longer properly associated with its transaction. It may have been opened in a transactional resource manager that was subsequently forced to restart. Please close the handle and open a new one.
The specified operation could not be performed because the resource manager is not enlisted in the transaction.
The log service found an invalid log sector.
The log service encountered a log sector with invalid block parity.
The log service encountered a remapped log sector.
The log service encountered a partial or incomplete log block.
The log service encountered an attempt to access data outside the active log range.
The log service user-log marshaling buffers are exhausted.
The log service encountered an attempt to read from a marshaling area with an invalid read context.
The log service encountered an invalid log restart area.
The log service encountered an invalid log block version.