Log backup for database "%1!s!" on a secondary replica failed because the last backup LSN (0x%2!s!) from the primary database is greater than the current local redo LSN (0x%3!s!). No log records need to be backed up at this time. Retry the log-backup operation later.
Locating the SQL Server Browser service component failed with Windows Installer return code '{0}'. The component ID: '{1}'. ...
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 ...