FIX: Upgrade to SQL Server 2016 SP2 CU3 or CU4 fails with an error when sysadmin account "sa" is renamed in SQL Server 2016 and 2017

Applies to: SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Enterprise Core

Symptoms


Consider the following scenario:

  • You have a Microsoft SQL Server 2016 or 2017 which is a Distributor in SQL Server Replication.
  • The built in sysadmin account "sa" is renamed to a different name, even if "sa" is disabled.
  • You try to upgrade to SQL Server 2016 Service Pack 2 (SP2) Cumulative Update 3 (CU3), Cumulative Update 4 (CU4) or later versions.

In this situation, you may notice that the upgrade operation fails, and you may receive an error message that resembles the following in the SQL Server error log:

The specified '@owner_login_name' is invalid (valid values are returned by sp_helplogins [excluding Windows NT groups])

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. 

Resolution


This issue is fixed in the following cumulative updates for SQL Server:

Note: To avoid receiving the error message while upgrading to SQL Server 2016 SP2 CU3 or CU4, you should uninstall CU3 or CU4 and install the SQL Server 2016 SP2 CU5 or later versions.

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:

References


Learn about the terminology that Microsoft uses to describe software updates.