Additionally, errors that resemble the following are logged in the SQL Server error log:
date time,Backup,Unknown,Error: 3041 Severity: 16 State: 1.
date time,spid326,Unknown,The log backup chain is broken. You must perform a full database backup before you can perform a log backup.
date time,spid326,Unknown,The operating system returned error 170 (The requested resource is in use.) to SQL Server during a write at offset 0x00000009dde000 in file file_path. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information see SQL Server Books Online.
Cumulative Update for 13 SQL Server 2012 SP2
Cumulative Update 5 for SQL Server 2012 Service Pack 3 (SP3)
Cumulative Update 1 for SQL Server 2014 SP2
Note After you apply this update, the intention is to remove the override of a valid transaction log backup. Therefore, this update introduces some additional validations to check whether the log chain remains unbroken.
Article ID: 3162858 - Last Review: Sep 21, 2016 - Revision: 1