BugZero found this defect 1308 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
6/2/2022
SQL Server 2016 Developer - duplicate (do not use)
SQL Server 2016 Enterprise - duplicate (do not use)
SQL Server 2016 Enterprise Core - duplicate (do not use)
SQL Server 2016 Standard - duplicate (do not use)
build lower than 14.0.3076.1
14.0.3076.1
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])
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This issue is fixed in the following cumulative updates for SQL Server: Cumulative Update 14 for SQL Server 2017 Cumulative Update 5 for SQL Server 2016 SP2 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: Latest cumulative update for SQL Server 2017 Latest cumulative update for SQL Server 2016
Learn about the terminology that Microsoft uses to describe software updates.