This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(153.6, 47%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELM%3C/text%3E%3C/svg%3E)
Hi
I have built out my new azure stack HCI cluster on Dell AX nodes and added the cluster to admin centre. I can create VMs directly on the servers ok and networking is good but when i try and configure the VM to be highly available i get the error "couldnt create the virtual machine, it was not added to the failover cluster ,None of the virtual machine configurations chosen was successfully made highly available. Please see the full report for further details about the failures."
Where can i find the full report? Can someone help guide me on this please ?
You can find the full report for the error message in the Event Viewer on the cluster nodes
Error: "couldn't create the virtual machine, it was not added to the failover cluster, none of the virtual machine configurations chosen was successfully made highly available. Please see the full report for further details about the failures"
The report will provide more details about the specific failure that occurred. You can also check the Failover Cluster Manager to ensure that the virtual machine is added to the failover cluster.
If you need further assistance, you can refer to the documentation on how to troubleshoot virtual machine high availability issues in a failover cluster.
The event viewer just says to please see the full report for further details about the operation but there is no report. Anyway i downloaded the diagnostic bundle and see this in the log, will this error go away when i register the cluster with azure ? That is not done yet
The service being accessed is licensed for a particular number of connections. No more connections can be made to the service at this time because there are already as many connections as the service can accept**
This issue needs deeper investigation, Azure technical support team will be able to check and help on this. I would recommend you open an azure support case. If you don't have the ability to open a technical support ticket, please let me know and I can help you further with this.
I dont have the ability to open a support ticket at the moment, i think that the issue is my cluster is not registered with Azure yet.
I am able to create VMs on the nodes themselves but not able to configure HA, can you confirm i need to register the cluster before i will be able to do this please ?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(118.4, 56.00000000000001%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETH%3C/text%3E%3C/svg%3E)
Hi Mike,
This error occurs because the cluster has either not yet be registered with Azure and/or the cluster is showing as 'Out of Policy'. A cluster that is out of policy prevents new HA VMs from being created and will also prevent existing VMs from being live migrated. Once you have your cluster successfully registered and in-policy, this error will be resolved.
Seems like i just have to register the cluster with azure and it will be ok, this is the message im getting
Job failure when attempting to create VM
Failure state explanation:
If the cluster is not registered with Azure upon deployment, or if the cluster is registered but has not connected to Azure for more than 30 days, the system will not allow new virtual machines (VMs) to be created or added. When this occurs, you will see the following error message when attempting to create VMs:
There was a failure configuring the virtual machine role for 'vmname'. Job failed. Error opening "vmname" clustered roles. The service being accessed is licensed for a particular number of connections. No more connections can be made to the service at this time because there are already as many connections as the service can accept.
Remediation action:
Register your HCI cluster with Azure. For information on how to register the cluster, see the instructions in the Register-AzStackHCI documentation.