Inplace Upgrade blocked with unnecessary dependency - by PrinceLucifer

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 773634 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 12/5/2012 11:40:38 PM
Access Restriction Public


Following setup:
6 node WSFC cluster
All nodes have a SQL 2012 installation on it
All nodes use AlwaysOn Availability Groups
No SQL Server FCIs 
One node has an additional SQL 2008R2 instance installed

Now I want to upgrade that KJ instance to Denali using Inplace Upgrade.
Unfortunately the rule check fails checking the WMI service for one of the other cluster nodes.
This check is ridicolous. My standalone instance of KJ/Denali does not need the WMI Service from any other cluster nodes. So this should not be a blocking upgrade issue
Sign in to post a comment.
Posted by PrinceLucifer on 1/7/2013 at 8:27 PM
Needing WMI might be by design. But a STANDALONE INSTANCE needing WMI on a SECONDARY CLUSTER NODE is just not true. The Setup shouldn't even connect to the other Cluster nodes in this Scenario. And that was all I was saying.
Posted by Microsoft on 1/7/2013 at 2:28 PM
Hi PrinceLucifer, thanks for taking the time to report this issue. The SQL Server setup requires WMI to connect to the node so this is by design.

[SQL Server Team]