Node and Cluster Edition Match Setup Rule Check Failed
One of the common task of a DBA is to perform installation of SQL Server or applying patches. Most often of not the installation completes successfully without any errors, however sometimes the setup fails with small and simetimes complex weird errors. Unfortunately there are also great lot of bugs with the setup media as well. Starting with SQL Server 2008, the cluster installation has changed where we have to install SQL Server as cluster instance on first node and then run ADD Node operation on remaining all other nodes. Below is one of the error we faced in our environment while performing ADD node operation of SQL Server cluster instance.
Rule Check Result
Rule “Node and cluster edition match” failed.
The edition of the new node does not match the edition of the cluster.
From Details.txt log file
Slp: The edition user specified is: ENTERPRISE
Slp: The edition of the cluster instance: STANDARD
Slp: Evaluating rule : AddNodeEditionBlock
The error message in this case is pretty clear which states that the edition is not matching. As we have already performed installation of SQL instance as cluster in first node, and we are performing add node operation, it is possible that the setup media used to run add node operation can be of different edition than what was installed on first node. Checking the detail.txt setup log clarifies the doubt where it specifies that the edition of SQL Server setup media used is ENTERPRISE, but the SQL Server cluster instance to which we are trying to add is STANDARD edition, thus the mismatch. It is not possible or allowed to use different editions on each node, it has to be same.
Sometimes the errors are small and has clear message, so it is just a little common sense to understand and fix the problem. This kind of issue is very rare as installation on all cluster nodes are performed by same DBA on same day in a span of few days, but in some cases where installation of one or more nodes is performed and after few months or years, they decide to install another node. In such cases it is better to review the existing environment rather than directly performing the installation.
Hope this was helpful.
This is applicable for below versions of SQL Server
SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, Frequently asked questions, SQL Server Trainings