You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This article describes resolutions to errors encountered when creating clusters.
16
+
This article describes resolutions to errors you might come across when creating clusters.
17
17
18
18
> [!NOTE]
19
-
> The first three errors in the list below occur due to validation errors when the CsmDocument_2_0 class is used by an HDInsight product.
19
+
> The first three errors described in this article are validation errors. They can occur when an Azure HDInsight product uses the **CsmDocument_2_0** class.
20
20
21
+
## Error code: DeploymentDocument 'CsmDocument_2_0' failed the validation
21
22
23
+
### Error
22
24
23
-
## Error Code: DeploymentDocument 'CsmDocument_2_0' failed the validation
25
+
"Script Action location cannot be accessed URI:\<SCRIPT ACTION URL\>"
24
26
25
-
###**Error**: Script Action location cannot be accessed URI:\<SCRIPT ACTION URL\>
27
+
#### Error message
26
28
27
-
**Error message: "The remote server returned an error: (404) Not Found."**
29
+
"The remote server returned an error: (404) Not Found."
28
30
29
31
### Cause
30
-
The Script Action URL that is provided as part of the Create Cluster request is not accessible from HDInsight service. We receive the “ErrorMessage” when we try to access the script action.
31
32
32
-
### Resolution
33
-
- For an http/https URL, you can verify by trying to open the URL from an incognito browser window.
34
-
- For a WASB URL, make sure that the script exists in the storage account that is given in request. Make sure that the storage key for this storage account is accurate.
35
-
- For an ADLS URL, make sure that the script exists in the storage account.
33
+
The HDInsight service can't access the script action URL that you provided as part of the Create Cluster request. The service receives the preceding error message when it tries to access the script action.
34
+
35
+
### Resolution
36
+
37
+
- For an HTTP or HTTPS URL, verify the URL by trying to go to it from an incognito browser window.
38
+
- For a WASB URL, be sure that the script exists in the storage account that you give in the request. Also make sure that the storage key for this storage account is correct.
39
+
- For an ADLS URL, be sure that the script exists in the storage account.
36
40
37
41
---
38
42
39
-
## Error Code: DeploymentDocument 'CsmDocument_2_0' failed the validation
43
+
## Error code: DeploymentDocument 'CsmDocument_2_0' failed the validation
"Script Action location cannot be accessed URI: \<SCRIPT_ACTION_URL\>"
42
48
43
-
**Error message: The given script URI \<SCRIPT URI\> is in ADLS, but this cluster has no data lake storage principal**
49
+
#### Error message
50
+
51
+
"The given script URI \<SCRIPT_URI\> is in ADLS, but this cluster has no data lake storage principal"
44
52
45
53
### Cause
46
-
The Script Action URL that is provided as part of the Create Cluster request is not accessible from the HDInsight service. We receive the “ErrorMessage” when we try to access the script action.
54
+
55
+
The HDInsight service can't access the script action URL that you provided as part of the Create Cluster request. The service receives the preceding error message when it tries to access the script action.
47
56
48
57
### Resolution
49
58
50
-
Make sure that the corresponding Azure Data Lake Store Gen 1 account is added to the cluster. The service principal that is used to access the Azure Data Lake Store Gen 1 account is also added to the cluster.
59
+
Add the corresponding Azure Data Lake Storage Gen 1 account to the cluster. Also add the service principal that accesses the Data Lake Storage Gen 1 account to the cluster.
51
60
52
61
---
53
62
54
-
## Error Code: DeploymentDocument 'CsmDocument_2_0' failed the validation
63
+
## Error code: DeploymentDocument 'CsmDocument_2_0' failed the validation
55
64
56
-
### **Error**: VM size '\<CUSTOMER SPECIFIED VM SIZE\>' provided in the request is invalid or not supported for role '\<ROLE\>'. Valid values are: \<VALID VM SIZE FOR ROLE\>.
65
+
### Error
66
+
67
+
"VM size '\<CUSTOMER_SPECIFIED_VM_SIZE\>' provided in the request is invalid or not supported for role '\<ROLE\>'. Valid values are: \<VALID_VM_SIZE_FOR_ROLE\>."
57
68
58
69
### Cause
59
-
The customer-specified VM sizes are not allowed for the role. This may be true because the VM size value is not working as expected or is not suitable for the computer role.
70
+
71
+
The virtual machine size that you specified isn't allowed for the role. This error might occur because the VM size value doesn't work as expected or isn't suitable for the computer role.
60
72
61
73
### Resolution
62
-
The error message lists the valid values for the VM size. Select one of these valid values, and retry the Create Cluster request.
74
+
75
+
The error message lists the valid values for the VM size. Select one of these values and retry the Create Cluster request.
63
76
64
77
---
65
78
66
-
## Error Code: InvalidVirtualNetworkId
79
+
## Error code: InvalidVirtualNetworkId
80
+
81
+
### Error
67
82
68
-
### **Error**: The VirtualNetworkId is not valid. VirtualNetworkId '\<USER_VIRTUALNETWORKID\>'*
83
+
"The VirtualNetworkId is not valid. VirtualNetworkId '\<USER_VIRTUALNETWORKID\>'*"
69
84
70
85
### Cause
71
-
The **VirtualNetworkId** value that is specified during cluster creation is not in the correct format.
86
+
87
+
The **VirtualNetworkId** value that you specified during cluster creation isn't in the correct format.
72
88
73
89
### Resolution
74
-
Make sure that **VirtualNetworkId** and subnet are in the correct format. To obtain the **VirtualnetworkId** value, go to the Azure portal, select your virtual network, and then select **Properties** on the menu. The **ResourceID** property is the **VirtualNetworkId** value.
75
90
76
-
An example of a virtual network ID is:
91
+
Make sure that the **VirtualNetworkId** and subnet values are in the correct format. To get the **VirtualNetworkId** value:
92
+
93
+
1. Go to the Azure portal.
94
+
1. Select your virtual network.
95
+
1. Select the **Properties** menu item. The **ResourceID** property value is the **VirtualNetworkId** value.
### **Error**: Cluster deployment failed due to an error in the custom script action. Failed Actions: \<SCRIPT_NAME\>, Please go to Ambari UI to further debug the failure.
107
+
"Cluster deployment failed due to an error in the custom script action. Failed Actions: \<SCRIPT_NAME\>, Please go to Ambari UI to further debug the failure."
85
108
86
109
### Cause
87
-
The user’s custom script that was provided during the Create Cluster request is executed after the cluster is deployed successfully. This error code indicates that an error was encountered while executing this custom script with name \<SCRIPT_NAME\>.
110
+
111
+
The custom script that you provided during the Create Cluster request is executed after the cluster is deployed successfully. This error code indicates that an error arose during execution of the custom script named \<SCRIPT_NAME\>.
88
112
89
113
### Resolution
90
-
Because this is the user’s custom script, users should troubleshoot the issue and rerun the script if necessary. To troubleshoot the script failure, examine the logs in the /var/lib/ambari-agent/* folder. Or, open the Operations page in the Ambari UI, and then select the **run_customscriptionaction** operation to view the error details.
114
+
115
+
Because the script is your custom script, we recommend that you troubleshoot the problem and rerun the script if necessary. To troubleshoot the script failure, examine the logs in the /var/lib/ambari-agent/* folder. Or open the **Operations** page in the Ambari UI and then select the **run_customscriptaction** operation to view the error details.
91
116
92
117
---
93
118
94
-
## Error Code: InvalidDocumentErrorCode
119
+
## Error code: InvalidDocumentErrorCode
95
120
96
-
### **Error**: The \<META_STORE_TYPE\> Metastore schema version \<METASTORE_MAJOR_VERSION\> in database \<DATABASE_NAME\> is incompatible with cluster version \<CLUSTER_VERSION\>
121
+
### Error
122
+
123
+
"The \<META_STORE_TYPE\> Metastore schema version \<METASTORE_MAJOR_VERSION\> in database \<DATABASE_NAME\> is incompatible with cluster version \<CLUSTER_VERSION\>"
97
124
98
125
### Cause
99
-
The custom metastore is incompatible with the selected HDInsight cluster version. Currently, HDInsight 4.0 cluster supports only Metastore version 3.*x*, and HDInsight 3.6 does not support Metastore version 3.*x* or later.
126
+
127
+
The custom metastore is incompatible with the selected HDInsight cluster version. Currently, HDInsight 4.0 clusters support only Metastore version 3.0 and later, while HDInsight 3.6 clusters don't support Metastore version 3.0 and later.
100
128
101
129
### Resolution
102
-
Make sure to use only Metastore versions that are supported by each HDInsight cluster version. Notice that if a custom metastore is not specified, HDInsight internally creates a metastore. However, this metastore will automatically be deleted upon cluster deletion.
130
+
131
+
Use only Metastore versions that your HDInsight cluster version supports. If you don't specify a custom metastore, HDInsight internally creates a metastore and then deletes it upon cluster deletion.
### **Error**: Unable to connect to cluster management endpoint to perform scaling operation. Verify that network security rules are not blocking external access to the cluster, and that the cluster manager (Ambari) UI can be successfully accessed.
139
+
"Unable to connect to cluster management endpoint to perform scaling operation. Verify that network security rules are not blocking external access to the cluster, and that the cluster manager (Ambari) UI can be successfully accessed."
109
140
110
141
### Cause
111
-
You have a firewall rule on your Network Security Group (NSG) that is blocking cluster communication with critical Azure health and management services.
142
+
143
+
A firewall rule on your network security group (NSG) is blocking cluster communication with critical Azure health and management services.
112
144
113
145
### Resolution
114
-
If you plan to use **network security groups** to control network traffic, take the following actions before you install HDInsight:
115
-
- Identify the Azure region that you plan to use for HDInsight.
116
-
- Identify the IP addresses required by HDInsight. For more information, see [HDInsight management IP addresses](https://docs.microsoft.com/azure/hdinsight/hdinsight-management-ip-addresses).
117
-
- Create or modify the network security groups for the subnet that you plan to install HDInsight into.
118
-
-**Network security groups:** Allow **inbound** traffic on port **443** from the IP addresses. This makes sure that HDInsight management services can reach the cluster from outside the virtual network.
146
+
147
+
If you plan to use network security groups to control network traffic, take the following actions before you install HDInsight:
148
+
149
+
- Identify the Azure region that you plan to use for HDInsight.
150
+
- Identify the IP addresses required by HDInsight. For more information, see [HDInsight management IP addresses](https://docs.microsoft.com/azure/hdinsight/hdinsight-management-ip-addresses).
151
+
- Create or modify the network security groups for the subnet that you plan to install HDInsight into.
152
+
- For network security groups, allow inbound traffic on port 443 from the IP addresses. This configuration ensures that HDInsight management services can reach the cluster from outside the virtual network.
119
153
120
154
---
121
155
122
-
## Error Code: StoragePermissionsBlockedForMsi
156
+
## Error code: StoragePermissionsBlockedForMsi
157
+
158
+
### Error
123
159
124
-
### **Error**: The Managed Identity does not have permissions on the storage account. Please verify that 'Storage Blob Data Owner' role is assigned to the Managed Identity for the storage account. Storage: /subscriptions/ \<Subscription ID\> /resourceGroups/\< Resource Group Name\> /providers/Microsoft.Storage/storageAccounts/ \<Storage Account Name\>, Managed Identity: /subscriptions/ \<Subscription ID\> /resourceGroups/ /\< Resource Group Name\> /providers/Microsoft.ManagedIdentity/userAssignedIdentities/ \<User Managed Identity Name\>
160
+
"The Managed Identity does not have permissions on the storage account. Please verify that 'Storage Blob Data Owner' role is assigned to the Managed Identity for the storage account. Storage: /subscriptions/ \<Subscription ID\> /resourceGroups/\< Resource Group Name\> /providers/Microsoft.Storage/storageAccounts/ \<Storage Account Name\>, Managed Identity: /subscriptions/ \<Subscription ID\> /resourceGroups/ /\< Resource Group Name\> /providers/Microsoft.ManagedIdentity/userAssignedIdentities/ \<User Managed Identity Name\>"
125
161
126
162
### Cause
127
-
The required permissions were not provided to **Manage identity.****User-assigned managed identity** didn’t have Blob Storage Contributor Role on ADLS Gen2 storage account.
163
+
164
+
You didn't provide the permissions required to manage identity. The user-assigned managed identity doesn't have the Blob Storage Contributor role on the Azure Data Lake Storage Gen2 storage account.
128
165
129
166
### Resolution
130
167
131
-
Open the Azure portal, go to your Storage account, look under **Access Control (IAM)**, and make sure that the Storage Blob Data Contributor or the Storage Blob Data Owner role has ""Assigned" access to the **User-assigned managed identity** for the subscription. For more information, see [Set up permissions for the managed identity on the Data Lake Storage Gen2 account](hdinsight-hadoop-use-data-lake-storage-gen2.md).
168
+
1. Open the Azure portal.
169
+
1. Go to your storage account.
170
+
1. Look under **Access Control (IAM)**.
171
+
1. Make sure that the Storage Blob Data Contributor role or the Storage Blob Data Owner role has "Assigned" access to the user-assigned managed identity for the subscription.
172
+
173
+
For more information, see [Set up permissions for the managed identity on the Data Lake Storage Gen2 account](hdinsight-hadoop-use-data-lake-storage-gen2.md).
### **Error**: The security rules in the Network Security Group /subscriptions/\<SubscriptionID>\/resourceGroups/<ResourceGroupname> default/providers/Microsoft.Network/networkSecurityGroups/\<Network Security Group Name\> configured with subnet /subscriptions/\<SubscriptionID>\/resourceGroups/\<Resource Group name> RG-westeurope-vnet-tomtom-default\/providers/Microsoft.Network/virtualNetworks/\<Virtual Network Name>\/subnets/\<Subnet Name\>
138
-
does not allow required inbound and/or outbound connectivity. For more information, please visit [Plan a virtual network for Azure HDInsight](https://docs.microsoft.com/azure/hdinsight/hdinsight-plan-virtual-network-deployment), or contact support.**
179
+
### Error
180
+
181
+
"The security rules in the Network Security Group /subscriptions/\<SubscriptionID\>/resourceGroups/<Resource Group name\> default/providers/Microsoft.Network/networkSecurityGroups/\<Network Security Group Name\> configured with subnet /subscriptions/\<SubscriptionID\>/resourceGroups/\<Resource Group name\> RG-westeurope-vnet-tomtom-default/providers/Microsoft.Network/virtualNetworks/\<Virtual Network Name\>/subnets/\<Subnet Name\> does not allow required inbound and/or outbound connectivity. For more information, please visit [Plan a virtual network for Azure HDInsight](https://docs.microsoft.com/azure/hdinsight/hdinsight-plan-virtual-network-deployment), or contact support."
139
182
140
183
### Cause
141
-
If you use network security groups (NSGs) or user-defined routes (UDRs) to control inbound traffic to your HDInsight cluster, you must make sure that your cluster can communicate with critical Azure health and management services.
184
+
185
+
If network security groups or user-defined routes (UDRs) control inbound traffic to your HDInsight cluster, be sure that your cluster can communicate with critical Azure health and management services.
142
186
143
187
### Resolution
144
-
If you plan to use **network security groups** to control network traffic, take the following actions before you install HDInsight:
145
-
- Identify the Azure region that you plan to use for HDInsight, and create a safe list of the IP addresses for your region: [Health and management services: Specific regions](https://docs.microsoft.com/azure/hdinsight/hdinsight-management-ip-addresses#health-and-management-services-specific-regions).
146
-
- Identify the IP addresses that are required by HDInsight. For more information, see [HDInsight management IP addresses](https://docs.microsoft.com/azure/hdinsight/hdinsight-management-ip-addresses).
147
-
- Create or modify the network security groups for the subnet that you plan to install HDInsight into. **Network security groups**: allow inbound traffic on port **443** from the IP addresses. This will ensure that HDInsight management services can reach the cluster from outside the virtual network.
188
+
189
+
If you plan to use network security groups to control network traffic, take the following actions before you install HDInsight:
190
+
191
+
- Identify the Azure region that you plan to use for HDInsight, and create a safe list of the IP addresses for your region. For more information, see [Health and management services: Specific regions](https://docs.microsoft.com/azure/hdinsight/hdinsight-management-ip-addresses#health-and-management-services-specific-regions).
192
+
- Identify the IP addresses that HDInsight requires. For more information, see [HDInsight management IP addresses](https://docs.microsoft.com/azure/hdinsight/hdinsight-management-ip-addresses).
193
+
- Create or modify the network security groups for the subnet that you plan to install HDInsight into. For network security groups, allow inbound traffic on port 443 from the IP addresses. This configuration ensures that HDInsight management services can reach the cluster from outside the virtual network.
148
194
149
195
---
150
196
151
-
## Error Code: Cluster setup failed to install components on one or more hosts
197
+
## Error code: Cluster setup failed to install components on one or more hosts
152
198
153
-
### **Error**: Cluster setup failed to install components on one or more hosts. Please retry your request.
199
+
### Error
200
+
201
+
"Cluster setup failed to install components on one or more hosts. Please retry your request."
154
202
155
203
### Cause
156
-
Typically this error is generated when there is a transient issue or there is an Azure Outage
204
+
205
+
Typically, this error is generated when there's a transient problem or an Azure outage.
157
206
158
207
### Resolution
159
208
160
-
Check the [Azure status](https://status.azure.com/status) page for any potential Azure Outages that may impact cluster deployment. If there aren't any outages, retry cluster deployment.
209
+
Check the [Azure status](https://status.azure.com/status) page for any Azure outages that might affect cluster deployment. If there are no outages, retry cluster deployment.
161
210
162
-
## Next Steps
211
+
## Next steps
163
212
164
-
For more insight into troubleshooting errors with cluster creation, see [Troubleshoot cluster creation failures with Azure HDInsight](https://docs.microsoft.com/azure/hdinsight/hadoop/hdinsight-troubleshoot-cluster-creation-fails).
213
+
For more information about troubleshooting errors in cluster creation, see [Troubleshoot cluster creation failures with Azure HDInsight](https://docs.microsoft.com/azure/hdinsight/hadoop/hdinsight-troubleshoot-cluster-creation-fails).
0 commit comments