The transaction log contains a record (logop %1!s!) that is not valid. The log has been corrupted. Restore the database from a full backup, or repair the database.
The transaction cannot be reversed. Either this transaction type cannot be reversed or a related transaction must be reversed ...
The transaction could not be committed because an error occurred while tyring to flush FILESTREAM data to disk. A file may ...
The transaction for posting merge snapshot commands to the Publisher database had been chosen as a deadlock victim, the operation ...
The transaction has been stopped because it conflicted with the execution of a FILESTREAM close operation using the same ...
The transaction log contains a record (logop %1!s!) that is not valid. The log has been corrupted. Restore the database from ...
The transaction log for database '%1!s!' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc ...
The transaction that is associated with this operation has been committed or rolled back. Retry with a different transaction. ...
The transactions required for synchronizing the nosync subscription created from the specified backup are unavailable at ...
The transactions required for synchronizing the subscription with the specified log sequence number (LSN) are unavailable ...