The .NET Framework 3.5 is required when you configure SQL Server 2016 as a secondary in Transaction Log Shipping
Consider the following scenario:
- You install SQL Server 2016 on your computer.
- You use Transaction Log Shipping and configure SQL Server 2016 as the secondary.
In this scenario, when you start a LSCopy job on the secondary, you may encounter failure without an error logged.
If you edit the LSCopy job under SQL Server Agent on the secondary, copy and paste the full sqllogship.exe command in the command line and then press Enter, the .NET Framework 3.5 is listed as being required.
Note After you install the .NET Framework 3.5 and restart the server in this scenario, the LSCopy and LSRestore jobs run correctly.
The fix for this issue is included in the following cumulative update for SQL Server:
About cumulative updates 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. Check out the latest cumulative updates for SQL Server:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Learn about the terminology Microsoft uses to describe software updates.
Article ID: 3173666 - Last Review: 07/25/2016 21:58:00 - Revision: 1.0
Microsoft SQL Server 2016 Developer, Microsoft SQL Server 2016 Enterprise, Microsoft SQL Server 2016 Standard
- kbqfe kbfix kbexpertiseinter kbsurveynew KB3173666