Log backup for database "%1!s!" on secondary replica failed because the new backup information could not be committed on primary database. Check the database status in the SQL Server error log of the server instance that is hosting the current primary replica. If the primary database is participating in the availability group, retry the operation.
Lock Pages In Memory (LPIM) feature was not enabled on the 32-bit installation. However, LPIM privilege exists for engine ...
Lock Pages In Memory (LPIM) feature was not enabled on the 64-bit installation. However, LPIM privilege exists for engine ...
Log backup for database "%1!s!" on a secondary replica failed because a synchronization point could not be established on ...
Log backup for database "%1!s!" on a secondary replica failed because the last backup LSN ( 2!s!) from the primary database ...
Log backup for database "%1!s!" on secondary replica failed because the new backup information could not be committed on ...
Log file '%1!s!' does not match the primary file. It may be from a different database or the log may have been rebuilt previously. ...
Log files, offline files, restoring files, and defunct files for database snapshots should not be specified. "%1!s!" is not ...
Log scan process failed in processing a ddl log record. Refer to previous errors in the current session to identify the cause ...
Log Scan process failed in processing log records. Refer to previous errors in the current session to identify the cause ...