Azure Kubernetes Service (AKS) - Utility Installation Troubleshooting steps
Overview
This KB provides troubleshooting steps to resolve Azure Kubernetes monitoring failures that occur when
kubectl data collection fails due to missing or inaccessible utilities (azure-cli, kubectl, kubelogin). These issues typically occur when the
prerequisite utilities are not installed or installed by a different user than the Applications Manager service logon user.
Installation and Permission Restricted Errors
Note: The error messages mentioned below are the updated messages displayed from Applications Manager v17.82.00
Error 1: Azure CLI Utility Not Found
- Error Message: Data collection has stopped because the azure-cli utility is not found. Error: Exception :: Cannot run program "az.cmd": CreateProcess error=2, The system cannot find the file specified. Ensure that azure-cli is installed and accessible to the Applications Manager service logon user ({UserName}), or start the Applications Manager with a user account that can access azure-cli. Please refer troubleshooting for more information.
- Verify Azure CLI Installation
- Open Command Prompt (Windows) or Terminal (Linux)
- Run the following command: az version
- Expected Output: Displays the Azure CLI version information.
- If the command is not recognized: Azure CLI is not installed.
- If Azure CLI is not installed,
- Install the Azure CLI on an Applications Manager-installed machine (Windows or Linux) to configure the cluster with kubectl for monitoring. Learn more.
- If Azure CLI is installed, ensure it is accessible to Applications Manager logon user.
Error 2: kubectl Utility Not Found
- Error Message 1: The below message appears when the kubectl's default installation path for the Applications Manager service logon user is present in the environment variable 'Path', but kubectl is still not accessible.
- Data collection has stopped because the kubectl utility is not found. Error: Exception :: Cannot run program "kubectl": CreateProcess error=2, The system cannot find the file specified. Ensure that kubectl is installed and accessible to the Applications Manager service logon user ({UserName}), or start the Applications Manager with a user account that can access kubectl. Please refer troubleshooting for more information.
- Error Message 2: The below message appears when the kubectl's default installation path for the Applications Manager service logon user is not present in the environment variable 'Path'.
- Data collection has stopped because the kubectl utility is not found. Error: Exception :: Cannot run program "kubectl": CreateProcess error=2, The system cannot find the file specified. Ensure that kubectl is installed and accessible to the Applications Manager service logon user ({UserName}), or start the Applications Manager with a user account that can access kubectl. Also, the default installation path '%USERPROFILE%\\.azure-kubectl' is not set in the environment variable for the logon user. Please refer troubleshooting for more information.
- Verify kubectl Installation
- Open Command Prompt (Windows) or Terminal (Linux)
- Run the command: kubectl version --client
- Expected Output: Displays the kubectl client version.

- If the command is not recognized: kubectl is not installed.
- If the kubectl utility is not installed, install the compatible 'Kubectl' utility executable file (kubectl.exe) by following the prerequisite steps.
- If the kubectl utility is installed, ensure it is accessible to Applications Manager logon user. Refer to the troubleshooting steps for utility access issue encountered on Windows.
Error 3: kubelogin Utility Not Found
- Error Message 1: The below message appears when the kubelogin's default installation path for the Applications Manager service logon user is present in the environment variable 'Path', but kubelogin is still not accessible.
- Unable to collect kubectl performance metrics due to an error with the 'kubelogin' command: kubelogin convert-kubeconfig -l azurecli. Error: Exception :: Cannot run program "kubelogin": CreateProcess error=2, The system cannot find the file specified. Ensure that kubelogin is installed and accessible to the Applications Manager service logon user ({UserName}), or start the Applications Manager with a user account that can access kubelogin. Please refer troubleshooting for more information.
- Error Message 2: The below message appears when the kubelogin's default installation path for the Applications Manager service logon user is not present in the environment variable 'Path'.
- Unable to collect kubectl performance metrics due to an error with the 'kubelogin' command: kubelogin convert-kubeconfig -l azurecli. Error: Exception :: Cannot run program "kubelogin": CreateProcess error=2, The system cannot find the file specified. Ensure that kubelogin is installed and accessible to the Applications Manager service logon user ({UserName}), or start the Applications Manager with a user account that can access kubelogin. Also, the default installation path '%USERPROFILE%\\.azure-kubelogin' is not set in the environment variable for the logon user. Please refer troubleshooting for more information.
- Verify kubelogin Installation
- Open Command Prompt (Windows) or Terminal (Linux)
- Run the command: kubelogin --version
- Expected Output: Displays the kubelogin version.

- If the command is not recognized: kubelogin is not installed.
- If the kubelogin utility is not installed, install the compatible kubelogin.exe along with kubectl.exe by following the prerequisite installation steps.
- If the kubelogin utility is installed, ensure it is accessible to Applications Manager logon user. Refer to the troubleshooting steps for utility access issue encountered on Windows.
Troubleshooting Utility Access Issue (Windows)
- Issue: Applications Manager running in Service mode uses the 'Local System account' as Log On user by default. If kubectl and kubelogin are installed via "az aks install-cli --client-version [client-version]" they are placed in user-specific folders and added to that user’s 'Path' Environment Variable. Since the service runs under the 'Local System account', it cannot access the utilities installed to specific user, causing data collection to fail.
- How to fix:
Check the Logon User of Applications Manager
Open Services (services.msc).
Locate the service ManageEngine Applications Manager (or similar).
Right-click → Properties → Log On tab.
Note the Log on as user account (e.g., Local System, Administrator, or a domain user).
- Ensure Applications Manager Logon User Has Access to Utilities
Verify that the user running Applications Manager has performed the Azure Kubernetes Service monitor
prerequisites by installing the required utilities (azure-cli, kubectl, kubelogin).
If the logon user is different from the user who installed the utilities, perform one of the following actions:
Option 1: Change the Applications Manager service logon user (via Services) to the user who has access to the utilities.
Option 2: Log in as the Applications Manager's
logon user and
install the required utilities by performing the AKS monitor
prerequisites.
New to ADSelfService Plus?
Related Articles
Azure Kubernetes Service(AKS) Troubleshooting FAQs
Azure Kubernetes Service (AKS) monitor can be configured only if you have already added a Microsoft Azure monitor in Applications Manager. Ensure that you have met all the prerequisites for the Microsoft Azure monitor before monitoring Azure ...
Amazon Elastic Kubernetes Service (EKS) - Utility Installation Troubleshooting steps
Amazon Elastic Kubernetes Service (EKS) - Utility Installation Troubleshooting Steps This article provides troubleshooting steps to resolve AWS Kubernetes (EKS) monitoring failures that occur when data collection stops due to missing or inaccessible ...
Absence of data in the Pods tab or some tabs in the Kubernetes monitor
This is a known issue in the older version of Applications Manager, which is fixed in APM v16800. So, we recommend upgrading the Applications Manager to the stable version to properly fix this issue. To collect data for the Kubernetes Monitor, ...
How to connect Azure Kubernetes Service(AKS) Cluster and run Kubectl commands
This KB has information about connecting the Azure Kubernetes Cluster using Azure CLI and kubectl commands. Verify both Azure CLI and kubectl are configured in Applications Manager installed server as mentioned in our prerequisites. This document ...
Unable to Add Kubernetes Monitor
If you are having trouble adding a Kubernetes monitor in Applications Manager, ensure that the the prerequisites have been met: Verify whether you can establish an SSH connection to the Kubernetes server from the APM installed machine. Use the ...