The Transaction Coordination Manager has encountered error %1!s!, state %2!s!, severity %3!s! and is shutting down. This is a serious error condition, which may prevent further transaction processing. Examine previously logged messages to figure out the cause for this unexpected failure. Depending on the failure condition, the Transaction Coordination Manager might be restarted automatically.
The trace log cannot be found at the default directory location. Trace logs will be created at the following location: %1 ...
The tracer token ID (%1!s!) could not be found for Publisher %2!s!, database %3!s!, publication %4!s!. Use the stored procedure ...
The transaction cannot be assigned because the connection object associated with the transaction and the connection object ...
The transaction cannot be reversed. Either this transaction type cannot be reversed or a related transaction must be reversed ...
The Transaction Coordination Manager has encountered error %1!s!, state %2!s!, severity %3!s! and is shutting down. This ...
The transaction could not be committed because an error occurred while tyring to flush FILESTREAM data to disk. A file may ...
The transaction encountered an out-of-memory condition while rolling back to a savepoint, and therefore cannot be committed. ...
The transaction executed too many insert, update, or delete statements in memory optimized tables. The transaction was terminated. ...
The transaction for posting merge snapshot commands to the Publisher database had been chosen as a deadlock victim, the operation ...