FIX: "Unable to create restore plan due to break in the LSN chain" error when you restore differential backup in SSMS
Content provided by Microsoft
Applies to: Microsoft SQL Server 2012 Service Pack 2Microsoft SQL Server 2012 DeveloperMicrosoft SQL Server 2012 EnterpriseMicrosoft SQL Server 2012 StandardMicrosoft SQL Server 2014 DeveloperMicrosoft SQL Server 2014 DeveloperMicrosoft SQL Server 2014 EnterpriseMicrosoft SQL Server 2014 EnterpriseMicrosoft SQL Server 2014 Enterprise CoreMicrosoft SQL Server 2014 Enterprise CoreMicrosoft SQL Server 2014 StandardMicrosoft SQL Server 2014 StandardMicrosoft SQL Server 2016 DeveloperMicrosoft SQL Server 2016 EnterpriseMicrosoft SQL Server 2016 Enterprise CoreMore
Assume that you create a full backup file and a differential backup file in Microsoft SQL Server Management Studio (SSMS). When you restore the full backup file by using the NORECOVERY option, and then you restore the differential backup file by using the RECOVERY option in SSMS, the operation fails, and you receive the following error message:
Unable to create restore plan due to break in the LSN chain. (Microsoft.SqlServer.SmoExtended)
Note This problem occurs in SSMS and SQL Server Management Objects (SMO), but not in SQL Server engine.
The issue was first fixed in the following Service Packs and 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:
Service packs are cumulative. Each new service pack contains all the fixes that are in previous service packs, together with any new fixes. Our recommendation is to apply the latest service pack and the latest cumulative update for that service pack. You do not have to install a previous service pack before you install the latest service pack. Use Table 1 in the following article for finding more information about the latest service pack and latest cumulative update.