SQL Server 2016 database log restore fails with the "Hk Recovery LSN is not NullLSN" error message

SQL Server database log restore fails, and you receive the following error message:
Hk Recovery LSN is not NullLSN and before deploy LSN during Redo
The issue was first fixed in the following cumulative update of SQL Server: Recommendation: Install the latest cumulative update for SQL Server
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. We recommend that you download and install the latest cumulative updates for SQL Server:
More information
To restore the log of a database that experiences this issue, install this update and enable trace flag 9958. Run the restore log command, when the database becomes online, issue a manual checkpoint so that subsequent backups will no longer have the issue specified in this article. After the successful log restore, the trace flag is no longer needed.

To enable the trace flag, add the -T9958 startup parameter. Or, you can use the dbcc traceon(9958) statement for a specific session.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Learn about the terminology that Microsoft uses to describe software updates.

Article ID: 3171002 - Last Review: 07/26/2016 00:40:00 - Revision: 1.0

Microsoft SQL Server 2016 Developer, Microsoft SQL Server 2016 Enterprise, Microsoft SQL Server 2016 Enterprise Core, Microsoft SQL Server 2016 Standard

  • kbqfe kbfix kbsurveynew kbexpertiseadvanced KB3171002