SQL 2017 upgrade to SQL 2019 still shows as SQL 2017

Question

This is like nothing I've seen in twenty years of working with SQL Server.

In the dialog, it states "it is not possible to change the SQL Server features to be upgraded in this release" Despite the statement, SQL will run through the upgrade process. Once proceed is accepted, the message states "There are not features selected for upgrade. The Database Engine Services are checked and selected. The Registry indicates the version is 2019. The Configuration Manager indicates the version is 2019. But the SQL 2019 backups will not apply.

The latest run, in the Setup Bootstrap for 2019, there are lines indicating the "Product features discovered"
Product Instance Instance ID Feature
SQL 2017 MSSQLSERVER MSSQL14.MSSQLSERVER Database Engine Services
SQL 2019 MSSQLSERVER.INACTIVE MSSQL14.MSSQLSERVER Database Engine Services

What is MSSQLSERVER.INACTIVE?

Answer 1

Hi @J Longstreet ,

Did you upgrade SQL server 2017 standard to SQL 2019 standard failed? The error messages that you offered are from SQL setup log? Could you find any other related error information from set up log? May be we can start from the latest SQL setup log.

>"The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start."

Check if the solution from this thread could help you.

> What is MSSQLSERVER.INACTIVE?

Check if this blog THE INSTANCE ID ‘MSSQLSERVER’ IS ALREADY IN USE BY SQL SERVER INSTANCE ‘MSSQLSERVER.INACTIVE’ could help you.

Best regards,
Cathy

---

If the response is helpful, please click "Accept Answer" and upvote it.
Hot issues October--Users always get connection timeout problem when using multi subnet AG via listener. Especially after failover to another subnet

Answer 2

That error message generally means you are trying to downgrade the edition. Please check your version and edition with SELECT @@VERSION. And verify the edition you are trying to upgrade to.

Answer 3

Thanks Tom,

I keep revising. When we purchased the Standard license, the only available license was 2019. We considered downgrading but then reconsidered. That seemed like a very bad decision. Is it possible the license thinks we are trying to downgrade?

SELECT @@VERSION
shows we are still at SQL 2017.

I'm wondering if I can change the registry entry from MSSQLSERVER.INACTIVE to just MSSQLSERVER. I don't understand the meaning of the INACTIVE suffix. Since I'll wind up reinstalling the entire process, I'll give that a go.

I attempted to Repair SQL 2017, then upgrade to Update 22, and once again try to install the SQL 2019 upgrade.

Probably the more pertinent error is "It is not possible to change the SQL Server features to be upgraded in this release."

I should note, I am using the same procedures used in dev and in test - both of these instances upgraded flawlessly. Not sure of your meaning of version, but the version is SQL 2017 Standard and SQL 2019 Standard. Both are x64. Not much time to waste here. If this has no answer, we go live Monday and need to test before then. It is likely the answer here is uninstall both versions, start over from scratch.

AFTER FIXING (see latest comment)
If someone is actually reading this, I had some initial issues because the dollar sign on the end of the gMSA is required. That also causes a WMI error. But it isn't related to what happened here.

Answer 4

This error "It is not possible to change the SQL Server features to be upgraded in this release." means you are trying to do an invalid EDITION upgrade or 32bit to 64 bit.

Please see supported upgrade options:

https://learn.microsoft.com/en-us/sql/database-engine/install-windows/supported-version-and-edition-upgrades-version-15?view=sql-server-ver15#upgrades-from-earlier-versions-to-

Answer 5

Installed initially is a SQL Standard 2017 x64 (DEV TEST and AGAIN ON PROD)
Upgraded to SQL Standard 2019 x64 (DEV TEST) no issues

This is an issue only on Prod. Same installs.

Removing and reinstalling reveals trouble with WMI Provider and an inability to compile the mof.
ERROR:
"The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start."

There is an older fix that points to the Windows Cleanup Utility. https://social.msdn.microsoft.com/Forums/sqlserver/en-US/4290b113-8e1d-4432-9e0b-73f1859b8aaf/the-mof-compiler-could-not-connect-with-the-wmi-server

But a search explains the tool was removed. The issues found were pieces of an older installation in the registry. I thought I got most of the registry extracted but apparently there is more to remove. I've seen in the past where the mof compiler was an issue (SQL 2008 for example) but that could usually be resolved by repairing the instance.

Had this error been evident at the start it might have resolved with a recompile of the mof using mofcomp against sqlmgmproviderxpsp2up.mof