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
Copy file name to clipboardExpand all lines: support/azure/azure-kubernetes/create-upgrade-delete/error-code-vhdfilenotfound.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,28 +1,28 @@
1
1
---
2
2
title: Troubleshoot the ERR_VHD_FILE_NOT_FOUND error code
3
-
description: Learn how to troubleshoot the ERR_VHD_FILE_NOT_FOUND error (124) when you try to create and deploy an Azure Kubernetes Service (AKS) cluster.
4
-
ms.date: 10/14/2024
3
+
description: Learn how to troubleshoot the ERR_VHD_FILE_NOT_FOUND error (65) when you try to create and deploy an Azure Kubernetes Service (AKS) cluster.
#Customer intent: As an Azure Kubernetes user, I want to troubleshoot the ERR_VHD_FILE_NOT_FOUND error code (or error code OutboundConnFailVMExtensionError, error number 50 - or error code ERR_K8S_API_SERVER_CONN_FAIL, error number 51) so that I can successfully create and deploy an Azure Kubernetes Service (AKS) cluster.
9
9
ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
10
10
---
11
-
# Troubleshoot the ERR_VHD_FILE_NOT_FOUND error code (124)
11
+
# Troubleshoot the ERR_VHD_FILE_NOT_FOUND error code (65)
12
12
13
-
This article discusses how to identify and resolve the `ERR_VHD_FILE_NOT_FOUND` error code (error code number 124) that occurs when you try to create and deploy a Microsoft Azure Kubernetes Service (AKS) cluster.
13
+
This article discusses how to identify and resolve the `ERR_VHD_FILE_NOT_FOUND` error code (error code number 65) that occurs when you try to create and deploy a Microsoft Azure Kubernetes Service (AKS) cluster.
14
14
15
15
## Symptoms
16
16
17
17
When you try to create an AKS cluster, you receive the following error message:
18
18
19
19
> VMExtensionProvisioningError: VM has reported a failure when processing extension 'vmssCSE'.
20
20
>
21
-
> Error message: "Enable failed: failed to execute command: command terminated with exit status=124
21
+
> Error message: "Enable failed: failed to execute command: command terminated with exit status=65
22
22
23
23
## Cause
24
24
25
-
Under rare circumstances, the 124 exit code for the Azure Virtual Machine Scale Set custom script extension (`vmssCSE`) might happen instead of the following error codes:
25
+
Under rare circumstances, the 65 exit code for the Azure Virtual Machine Scale Set custom script extension (`vmssCSE`) might happen instead of the following error codes:
title: ERR_VHD_FILE_NOT_FOUND when creating AKS clusters
3
+
description: Learn how to troubleshoot the ERR_VHD_FILE_NOT_FOUND error (65) when you try to create and deploy an Azure Kubernetes Service (AKS) cluster.
4
+
ms.date: 10/14/2024
5
+
editor: v-jsitser
6
+
ms.reviewer: axelg, chiragpa, v-leedennis
7
+
ms.service: azure-kubernetes-service
8
+
#Customer intent: As an Azure Kubernetes user, I want to troubleshoot the ERR_VHD_FILE_NOT_FOUND error code (or error code OutboundConnFailVMExtensionError, error number 50 - or error code ERR_K8S_API_SERVER_CONN_FAIL, error number 51) so that I can successfully create and deploy an Azure Kubernetes Service (AKS) cluster.
9
+
ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
10
+
---
11
+
# ERR_VHD_FILE_NOT_FOUND error code (65) when deploying an AKS cluster
12
+
13
+
This article discusses how to identify and resolve the `ERR_VHD_FILE_NOT_FOUND` error code (error code number 65) that occurs when you try to create and deploy a Microsoft Azure Kubernetes Service (AKS) cluster.
14
+
15
+
## Symptoms
16
+
17
+
When you try to create an AKS cluster, you receive the following error message:
18
+
19
+
> VMExtensionProvisioningError: VM has reported a failure when processing extension 'vmssCSE'.
20
+
>
21
+
> Error message: "Enable failed: failed to execute command: command terminated with exit status=65
22
+
23
+
## Cause
24
+
25
+
Under rare circumstances, the 65 exit code for the Azure Virtual Machine Scale Set custom script extension (`vmssCSE`) might happen instead of the following error codes:
This error occurs if a connectivity issue exists between your AKS cluster and the required Azure endpoints, such as `mcr.microsoft.com` or `acs-mirror.azureedge.net`.
34
+
35
+
## Solution
36
+
37
+
Review [outbound network and FQDN rules for Azure Kubernetes Service (AKS) clusters](/azure/aks/outbound-rules-control-egress) and make sure that all API services FQDN are allowed.
38
+
39
+
For detailed troubleshooting steps, refer to the troubleshooting guides in the following articles:
40
+
41
+
-[Troubleshoot the VMExtensionError_OutboundConnFail error code (50)](../error-codes/vmextensionerror-outboundconnfail.md)
42
+
-[Troubleshoot the VMExtensionError_K8SAPIServerConnFail error code (51)](../error-codes/vmextensionerror-k8sapiserverconnfail.md)
43
+
-[Troubleshoot the VMExtensionError_K8SAPIServerDNSLookupFail error code (52)](../error-codes/vmextensionerror-k8sapiserverdnslookupfail.md)
44
+
45
+
46
+
## References
47
+
48
+
-[General troubleshooting of AKS cluster creation issues](../create-upgrade-delete/troubleshoot-aks-cluster-creation-issues.md)
49
+
50
+
-[Outbound network and FQDN rules for Azure Kubernetes Service (AKS) clusters](/azure/aks/outbound-rules-control-egress)
51
+
52
+
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
0 commit comments