Unable to Install SQL 2017 CUs

Question

Unable to Install SQL 2017 CUs

Panopticon 11

I am in the process of upgrading our SQL 2017 servers to the current CU. I have ran across two systems that won't allow me to apply the update. In the SQL installer, I see below text when I click on the SQL Instance name.

"The version of SQL Server instance MSSQLSERVER does not match the version expected by the SQL Server update. The installed SQL Server product version is 14.0.3381.3, and the expected SQL Server version is 14.0.1000.169."

I am unsure where the installer pulls the version info from. I have compared the registry against a couple of other systems and nothing is standing out as being incorrect, so not sure where it is pulling the 14.0.1000.169 value for the "expected sql version". I tried removing the previous CU so I could reapply it, but it didn't appear that it removed fully as it was still in the add/remove programs screen. Everything I have found online points to older versions where people were trying to install CUs on top of the wrong Service Packs, which doesn't apply in this case since SQL 2017 doesn't have service packs.

Any ideas would be greatly appreciated.

Bryan 1 Reputation point

2022-09-16T19:11:55.39+00:00

Did you ever figure out how to get around this? We have the same issue (our product version is 14.0.2027.2 however) where we cannot install updates. We did update another server successfully. Our servers are both 14 (2017) but the one that upgraded was Standard Edition whereas the one that is having a problem is Enterprise Edition : Core-based Licensing. Both are on Windows Server 2016 Standard 10.0 (Build 14393). What edition are you running (can be found in Management Studio right click on server choose properties)?
Panopticon 11 Reputation points

2022-09-19T12:11:14.513+00:00

I have not found a solution for this issue yet. I have a ticket open with Microsoft and am making very little progress there. The server is running 2017 Standard with Core licensing running on Windows Server 2019 Standard.
Panopticon 11 Reputation points

2022-10-19T13:58:25.733+00:00

@Bryan , I did finally get a solution to this issue. The SQL installer was looking in the registry at an SSRS key with two values in it. One of the values was invalid and causing the error. Once I deleted the incorrect registry value, the installer worked. Here is the path - 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\RS' . The value I had to delete was one mapping MSSQLSERVER to SSRS (See Screenshot).

3 answers

Your answer

Bryan 1 Reputation point

2022-09-16T19:11:55.39+00:00

Did you ever figure out how to get around this? We have the same issue (our product version is 14.0.2027.2 however) where we cannot install updates. We did update another server successfully. Our servers are both 14 (2017) but the one that upgraded was Standard Edition whereas the one that is having a problem is Enterprise Edition : Core-based Licensing. Both are on Windows Server 2016 Standard 10.0 (Build 14393). What edition are you running (can be found in Management Studio right click on server choose properties)?
Panopticon 11 Reputation points

2022-09-19T12:11:14.513+00:00

I have not found a solution for this issue yet. I have a ticket open with Microsoft and am making very little progress there. The server is running 2017 Standard with Core licensing running on Windows Server 2019 Standard.
Panopticon 11 Reputation points

2022-10-19T13:58:25.733+00:00

@Bryan , I did finally get a solution to this issue. The SQL installer was looking in the registry at an SSRS key with two values in it. One of the values was invalid and causing the error. Once I deleted the incorrect registry value, the installer worked. Here is the path - 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\RS' . The value I had to delete was one mapping MSSQLSERVER to SSRS (See Screenshot).

Answer 1

CathyJi-MSFT 22,406 Microsoft External Staff

Hi @Panopticon ,

Which version of CU that you want to apply to SQL server 2017 CU23? Suggest you applying the latest CU30 to this SQL server instance. In addition, did you choose the correct instance name that you want to upgrade during upgrading process? How many SQL server instance that installed on your server?

-----------------------------------------------------------------------------------------------------------------------------------------------

If the answer is helpful, please click ”Accept Answer” and kindly vote it.

Panopticon 11 Reputation points

2022-08-16T12:18:54.707+00:00

CU23 is already applied. I am trying to get any of the newer CUs to apply correctly. There is only a default instance of SQL on this server.
CathyJi-MSFT 22,406 Reputation points Microsoft External Staff

2022-08-17T07:38:06.543+00:00

Hi @Panopticon ,

Please check your SQL server setup log. And share us the related error message from the log. Or you can share us the summary and detail log for analysis. Refer to View and Read SQL Server Setup Log Files.

Please use the SQLCMD -L command to list instances installed on your server as below screenshot. Please share us the result.
Panopticon 11 Reputation points

2022-08-17T13:29:54.113+00:00

I ran the sqlcmd -L but all it listed was a SQL instance on a different SQL server. I assume that uses the SQL Browser service which is disabled in on this system. I attached the detail and summary logs from the setup. Nothing in the logs stands out to me as an error. 232003-detail.txt 232056-summary.txt

Answer 2

Cause

We found that there is an instance mapping for Report Server that maps default instance name (MSSQLSERVER) to SSRS instance ID:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\RS
MSSQLSERVER REG_SZ SSRS

This causes the SQL setup to fail to patch the default instance.

Recommendation/Resolution

Deleting the 'MSSQLSERVER REG_SZ SSRS' registry key at 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\RS' allows SQL setup to successfully patch the default instance. Upon further investigation
Furthermore, we confirmed that this key should not exist as it implies the presence of a second SSRS 2017 instance which is not possible as SSRS 2017+ does not support multiple instances on the same server.

Tomasz Flor 0 Reputation points

2024-02-07T16:08:02.0533333+00:00

Just ran into this issue with SQL 2019, and can confirm that deleting the above registry key has resolved the problem. SSRS instance is unaffected.

Answer 3

Tom Phillips 17,781

The error might just be wrong. It sounds like you are trying to downgrade to a prior CU.

Try redownloading CU30 and try again.

https://support.microsoft.com/en-us/topic/kb5013756-cumulative-update-30-for-sql-server-2017-274943fa-8dde-4844-90ed-d3b587fa0c7c

Panopticon 11 Reputation points

2022-08-15T17:22:19.06+00:00

I have tried multiple different CUs above CU23 (3381) and get the same thing.
Tom Phillips 17,781 Reputation points

2022-08-15T18:43:07.253+00:00

Please post the results of SELECT @@VERSION
Panopticon 11 Reputation points

2022-08-15T18:47:30.103+00:00

Microsoft SQL Server 2017 (RTM-CU23) (KB5000685) - 14.0.3381.3 (X64) Feb 9 2021 12:08:50 Copyright (C) 2017 Microsoft Corporation Standard Edition (64-bit) on Windows Server 2019 Standard 10.0 <X64> (Build 17763: ) (Hypervisor)

Share via

Unable to Install SQL 2017 CUs

3 answers

Your answer