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(230.39999999999998, 72%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHC%3C/text%3E%3C/svg%3E)
Got the error below but I've validated that the load balancer settings are already in place.
Showing 1 out of 1 error(s).Status Message: Internal server error occurred while processing the request. Please retry the request or contact support. The following host components failed to start up: HIVE_METASTORE, HIVE_SERVER, OOZIE_SERVER, RESOURCEMANAGER, SPARK3_JOBHISTORYSERVER, SPARK3_THRIFTSERVER, WEBHCAT_SERVER. There is a possibility that this issue occurred due to HDInsight's transition to Standard Load Balancer. Please refer to https://learn.microsoft.com/en-us/azure/hdinsight/load-balancer-migration-guidelines to recreate the cluster with standard load balancers if not done yet, or contact support for assistance if it remains unresolved. (Code:AmbariClusterCreationFailedErrorCode)
An Azure managed cluster service for open-source analytics.
![](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(12.8, 24%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPP%3C/text%3E%3C/svg%3E)
Hi Hanyuan Cui,
Thankyou for reaching microsoft Q&A!
This error usually happens when cluster services fail to start during provisioning, most commonly due to networking issues related to the Standard Load Balancer setup.
Could you please double-check that the subnet has proper outbound connectivity (via NAT Gateway or outbound rules), and that NSG/UDR rules are not blocking required traffic to Azure services? Also ensure the subnet has enough available IPs and isn’t reused from a previous failed deployment.
As a quick isolation step, try deploying the cluster in a fresh subnet with minimal network restrictions.
You can also refer to the guidance here: https://learn.microsoft.com/en-us/azure/hdinsight/load-balancer-migration-guidelines
I think the root cause is ambari freezing on stale basic‑lb metadata in the control‑plane…" "recreate the cluster on a clean standard‑lb with a fresh subnet; if it still fails, the ambari backend needs azure to re‑init it.