The transaction could not be committed because an error occurred while tyring to flush FILESTREAM data to disk. A file may have been open at commit time or a disk I/O error may have occurred. '%1!s!' was one of the one or more files involved. ErorrCode: 0x%2!s!
The trace file name is not valid because it contains a rollover file number (NNN in C:\file_NNN) while the trace rollover ...
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 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 ...