SQL Server

Troubleshooting Upgrading to SQL Server 2016

Troubleshooting Upgrading to SQL Server 2016

Should you have problems with upgrading to SQL Server 2016, review this troubleshooting
checklist to find potential solutions.

1. Check the hardware requirements.

To upgrade to SQL Server 2016, you should have the following hardware:
– Intel or compatible platform with processor speed:
1.4 GHz minimum for a 64-bit x64
2.0 GHz or faster recommended
– Memory (RAM): 512 Mb minimum for SQL Server 2016 Express Edition,
1 GB minimum for other SQL Server 2016 Editions,
4 GB or more recommended.
– Hard disk space: a minimum of 6 GB of available hard-disk space.
– Display at least 800×600 pixel resolutions.
– A Microsoft mouse or compatible pointing device.

2. Check the operating system requirements.

To upgrade to SQL Server 2016, you must have one of the following operating systems:

– Windows 8 editions.
– Windows 8.1 editions.
– Windows 10 editions.
– Windows Server 2012 editions.
– Windows Server 2012 R2 editions.
– Windows Server 2016 editions.

3. Check the software requirements.

SQL Server 2016 requires Internet Explorer 7 or later version, and .NET Framework 4.6.

4. Ensure that you have administrative rights on the computer.

SQL Server needs these permissions to create registry entries, create services and so on.

5. Close all extraneous programs running.

Because extraneous programs use some system resources, it is a good idea to close all
extraneous programs before upgrading to SQL Server 2016. Be sure that there are no any
programs on the taskbar except as the Setup application.

6. Enable Windows Authentication for SQL Server Agent.

You should enable Windows Authentication for SQL Server Agent before upgrading to
SQL Server 2016.

7. Ensure that the SQL Server Agent service account is a member of the
SQL Server sysadmin group.


8. Ensure that the Windows Installer service is running.

The upgrade to SQL Server 2016 will be blocked if the Windows Installer service is
not running.

9. If you use member permissions in an earlier version of Master Data Services (MDS),
the member permissions may be broken after the upgrade.

This is SQL Server 2016 bug. This bug was fixed in Cumulative update package 1
for SQL Server 2016. You can download the Cumulative Update package 1 for
SQL Server 2016 at here:
https://support.microsoft.com/en-us/help/3164674/cumulative-update-1-for-sql-server-2016

10. The error occurs when you open the SQL Server Reporting Services (SSRS)
web portal after you upgrade to SSRS 2016.

This is the error message text: “HTTP 503: Service Unavailable”. This bug was fixed
in Cumulative update package 1 for SQL Server 2016. You can download the Cumulative
Update package 1 for SQL Server 2016 at here:
https://support.microsoft.com/en-us/help/3164674/cumulative-update-1-for-sql-server-2016

11. Secondary replica in “not healthy” state, after you upgrade the primary database
from SQL Server 2014 to SQL Server 2016.

This bug was fixed in Cumulative update package 1 for SQL Server 2016. You can
download the Cumulative Update package 1 for SQL Server 2016 at here:
https://support.microsoft.com/en-us/help/3164674/cumulative-update-1-for-sql-server-2016
To work around this problem, you can restart the secondary replica.

12. The error 19432 occurs after you upgrade Availability replicas in an Always
On Availability Group to Cumulative Update package 1 for SQL Server 2016.

This is the error message text: “Always On Availability Groups transport has detected
a missing log block for availability database “database_name”.” This bug was fixed in
Cumulative update package 3 for SQL Server 2016. You can download the Cumulative
Update package 3 for SQL Server 2016 at here:
https://support.microsoft.com/en-us/help/3205413/cumulative-update-3-for-sql-server-2016

13. To locate any problems during upgrade, check the Summary.txt file in the
“Program FilesMicrosoft SQL Server130Setup BootstrapLOG” directory
(the default path).

The Summary.txt file contains the general information about components installation
(successful or failed) and contains the links to the log files with detailed
description of the upgrading process. See also errorlog files located in the
Log directory of the target installation directory. These files contain full
description of each SQL Server component.

Facebooktwittergoogle_plusredditpinterestlinkedinmail