An error pccurred while creating the cluster. Could not determine Management point Network Type -- The procedure number is out of range

Question

_{Thursday, December 28, 2017 4:20 PM}

I am receiving the error in the subject when i try to create a cluster. The two nodes of the cluster are WS2016 Core.

The Validation Wizard doesn't show any Error or Warning.
The two servers are set-up to prefer IPv4 over IPv6 as this has been pointed out in some other posts as a possible cause of the type of error that i am  getting.

Thanks in advance for your help, and your suggestions!

All replies (7)

_{Friday, December 29, 2017 5:58 AM}

Hi ,

If you cannot successfully create a cluster after all your validation tests are passing, please examine the CreateCluster.mht file. This file is created during the cluster creation process through the “Create Cluster” wizard in Failover Cluster Manager or the Create-Cluster Failover Clustering Windows PowerShell cmdlet. The file can be found in the following location: C:\Windows\Cluster\Reports\CreateCluster.mht.
Note:  In Windows Server 2016 the report is changed from .MHT to .HTM.

For your reference:

How to Troubleshoot Create Cluster Failures

https://blogs.msdn.microsoft.com/clustering/2012/05/07/how-to-troubleshoot-create-cluster-failures-in-windows-server-2012/

Best Regards,

Candy

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Saturday, December 30, 2017 2:15 PM}

Thanks Candy for your reply.

The CreateCluster file displays  the following message:

"

Beginning to configure the cluster Cluster12.

An error occurred while creating the cluster.
Could not determine Management Point Network Type.

The procedure number is out of range

To troubleshoot cluster creation problems, run the Validate a Configuration wizard on the servers you want to cluster.

"

_{Tuesday, January 2, 2018 7:49 AM}

Hi ，

This is a quick note to let you know that I am currently performing research on this issue and will get back to you as soon as possible. I appreciate your patience.
If you have any updates during this process, please feel free to let me know.

Best Regards,

Candy

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Monday, January 8, 2018 1:00 AM | 8 votes}

Hi Go.ForIt,

I believe this is a bug in Server 2016. I was able to recreate this issue. However, I was able to create the cluster using PowerShell. Just run this cmd, but replace the node names and IP address with the names of your Hyper-V hosts and cluster IP address. 

New-Cluster -Name MyCluster01 -Node Host01,Host02,Host03 -StaticAddress 10.0.1.10

Cheers,

Ryan

Microsoft Server Engineer

Blog:   Twitter:   LinkedIn:   

Please remember to mark the replies as answers if they help.

Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

_{Tuesday, January 16, 2018 8:18 PM | 1 vote}

Dears,

I have the same issue. I have 2 networks.

I was able to create a cluster after ignoring one of the network, using -IgnoreNetwork parameter

_{Sunday, November 4, 2018 3:25 PM}

Older post but I had the same issue and the powershell command Ryan provided worked like a charm. Thanks!~

_{Thursday, December 6, 2018 8:30 AM}

I have encountered the same problem with Failover Cluster Manager. And changing to the "New-Cluster" command of PowerShell, it succeed.