SQL SERVER Installation – FeatureUpgradeMatrixCheck (SQL Server 2016 Feature Upgrade) setup rule failed

One of the best ways to learn problems faced by individuals and organizations is to look at the forums for these issues. Often I have visited MSDN forums and see if there are some hot or interesting issues. Sometimes it is interesting to see some setup failures and investigate for the root cause. They might look trivial, but the best part is going the path of troubleshooting can be refreshing and gives you immense satisfaction to how things work inside SQL Server or Windows. This blog is inspired by one such error that encountered and I found it interesting enough to share it on this blog for the benefit of a larger audience. Let us learn about SQL Server Installation Error.

Recently there was a post where failure of rule FeatureUpgradeMatrixCheck was reported.

Rule “SQL Server 2016 Feature Upgrade” failed.

The specified edition upgrade from source Enterprise edition to target Evaluation edition is not supported. For information about supported upgrade paths, see the SQL Server 2016 version and edition upgrade in Books Online.

SQL SERVER Installation - FeatureUpgradeMatrixCheck (SQL Server 2016 Feature Upgrade) setup rule failed RuleFailed-800x597

I looked into Detail.txt and I have highlighted the line which explains the crux of the problem.

(17) 2016-07-11 03:05:42 Slp: Initializing rule : SQL Server 2016 Feature Upgrade
(17) 2016-07-11 03:05:42 Slp: Rule is will be executed : True
(17) 2016-07-11 03:05:42 Slp: Init rule target object: Microsoft.SqlServer.Configuration.SetupExtension.SkuUpgradeRule
(17) 2016-07-11 03:05:42 Slp: — SkuUpgradeRule : Rule ‘FeatureUpgradeMatrixCheck’ looking for previous version upgrade data for feature package ‘sql_as_Cpu64’.
(17) 2016-07-11 03:05:42 Slp: — SkuUpgradeRule : Rule ‘FeatureUpgradeMatrixCheck’ feature package ‘sql_as_Cpu64’ found no upgrade features.
(17) 2016-07-11 03:05:42 Slp: — SkuUpgradeRule : Rule ‘FeatureUpgradeMatrixCheck’ looking for previous version upgrade data for feature package ‘sql_engine_core_inst_Cpu64’.
(17) 2016-07-11 03:05:42 Slp: — SkuUpgradeRule : Found feature package ‘sql_engine_core_inst_SQL14_Cpu64’ with SkuValue=ENTERPRISE (Enterprise) ProductVersion=12.0.2000.8
(17) 2016-07-11 03:05:42 Slp: — SkuUpgradeRule : Rule ‘FeatureUpgradeMatrixCheck’ found sourceVersion 12.0.0 and edition ENTERPRISE for feature package ‘sql_engine_core_inst_Cpu64’.
(17) 2016-07-11 03:05:42 Slp: — SkuPublicConfigObject : ValidateSkuMatrix checking sku matrix for sourceVersion=12.0.0 sourceEdition=ENTERPRISE (Enterprise) sourceArchitecture=X64 targetEdition=EVAL (Evaluation) targetArchitecture=X64
(17) 2016-07-11 03:05:42 Slp: — SkuPublicConfigObject : ValidateSkuMatrix source and target architecture match.
(17) 2016-07-11 03:05:42 Slp: — SkuPublicConfigObject : ValidateSkuMatrix did not find a match in sku matrix .
(17) 2016-07-11 03:05:42 Slp: — SkuUpgradeRule : Rule ‘FeatureUpgradeMatrixCheck’ feature package ‘sql_engine_core_inst_Cpu64’ is blocking upgrade.
(17) 2016-07-11 03:05:42 Slp: — SkuUpgradeRule : Rule ‘FeatureUpgradeMatrixCheck’ detection result: IsValidFeatureUpgrade=False
(17) 2016-07-11 03:05:42 Slp: Evaluating rule : FeatureUpgradeMatrixCheck
(17) 2016-07-11 03:05:42 Slp: Rule running on machine: LAB-SQL-SERVER
(17) 2016-07-11 03:05:42 Slp: Rule evaluation done : Failed
(17) 2016-07-11 03:05:42 Slp: Rule evaluation message: The specified edition upgrade from source Enterprise edition to target Evaluation edition is not supported. For information about supported upgrade paths, see the SQL Server 2016 version and edition upgrade in Books Online.

Whenever there are issues with upgrade, I always look for topic “Supported Version and Edition Upgrades”

If we look at source edition, its ENTERPRISE and target is EVAL. Here is the document for SQL Server 2016.

As per books online “SQL Server 2014 Enterprise” can only be upgraded to “SQL Server 2016 Enterprise” and “SQL Server 2016 Business Intelligence” and hence the error.

Have you ever faced similar rule failure? How did you fix them?

Reference: Pinal Dave (https://blog.sqlauthority.com)

, ,
Previous Post
SQL SERVER – Install Error – Could not Find the Database Engine Startup Handle
Next Post
SQL SERVER – Unable to Create Listener for AlwaysOn Availability Group in Azure via Template Deployment

Related Posts

Leave a Reply

Menu