Windows 2016 Update-ClusterFunctionalLevel command fails

I'm trying to update the Cluster Functional Level of a two-node Hyper-V cluster where the original Win 2012 R2 nodes have been replaced with newer Win 2016 nodes.  The new nodes went in without issues, and the old nodes were removed without problems, but I can't raise the Cluster Functional Level from 8 to 9:

PS C:\Users\T-DLA01> Update-ClusterFunctionalLevel

Updating the functional level for cluster HVSAN01.
Warning: You cannot undo this operation. Do you want to continue?
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "Y"): A
Update-ClusterFunctionalLevel : Updating the cluster functional level failed.

The cluster did not successfully complete the version upgrade
At line:1 char:1
+ Update-ClusterFunctionalLevel
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Update-ClusterFunctionalLevel], ClusterCmdletException
    + FullyQualifiedErrorId : Update-ClusterFunctionalLevel,Microsoft.FailoverClusters.PowerShell.UpdateClusterFunctio
   nalLevelCommand

I've checked everything I can think to check, including ensuring all required cluster resources are present.

This is the test bed for a much larger cluster upgrade scheduled for early next year.

TIA for any assistance you may be able to give.
DougAppelSr. AnalystAsked:
Who is Participating?
 
DougAppelSr. AnalystAuthor Commented:
Nevermind - it was a permissions issue.  Thanks for your help!

-DLA
0
 
Alex Green3rd Line Server SupportCommented:
Please try the following commands to restore the "MSMQ" and "MSMQ Triggers" cluster resource types:

Get-ClusterResourceType

 

Add-ClusterResourceType MSMQ -dll C:\Windows\Cluster\mqclus.dll

 

Add-ClusterResourceType MSMQTriggers -dll C:\Windows\Cluster\mqtgclus.dll

 

Get-ClusterResourceType

 

Update-ClusterFunctionalLevel



From

https://social.technet.microsoft.com/Forums/ie/en-US/3532a986-9067-482f-afd6-28ac2d1a17ed/failover-cluster-cannot-upgrade-functional-level?forum=winserverClustering
0
 
Cliff GaliherCommented:
What do the logs say?
0
Cloud Class® Course: CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

 
DougAppelSr. AnalystAuthor Commented:
Cliff Galiher - which logs specifically?
Alex Green - as I said in the question post, I verified that all required resources were present, including MSMQ and MSMQTriggers.  Thanks.
0
 
Cliff GaliherCommented:
Event logs for certain.  I am fairly certain that cluster services also have their own logs. But am mobile at the moment and don't have the quick ability to google their location.  Either way, event logs are *always* a good start.
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
In Failover Cluster Manager set up a log query in Cluster Events.

Query:
1: Choose Nodes
2: Event Logs:
 + Microsoft-Windows-Cluster*
 + Microsoft-Windows-FailoverClustering*
 + Microsoft-Windows-Hyper-V*
   *The asterisk represents all options in that category
3: Critical, Error, Warning
4: Events On: Date FROM/TO the problem occurring
5: Click OK
6: Save Query As...
 + Give it a name and copy that .XML off for future usage.
7: Save Events As...
 + Keep a copy of the events as they stand

Then from there, dig through.

There are additional steps that can be done in PowerShell but let's start here.
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Where were the permissions choked?
0
 
DougAppelSr. AnalystAuthor Commented:
Turned out to be an overlooked permissions issue.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.