Troubleshooting WMI Connectivity
Troubleshoot WMI connectivity
Note: If you're using Applications Manager version 15470 or later, navigate to Admin > Self Help Tools and select the monitor type to troubleshoot the issue. For more information, see the Self Help Tools documentation.
If you encounter an error in the Self Help Tools, follow the steps below to check the WMI connection using the VBScript used in the monitor.
- Open Command Prompt in Administrator mode on the Applications Manager-installed machine.
- Navigate to the <Applications Manager Home>\working\conf\application\scripts directory.
- Execute the following command (replace hostname, username, and password with the values configured for the monitored server):(For Windows monitors)cscript conf-os-info.vbs hostname username password(For Exchange Server, SharePoint Server, IIS Server, Microsoft MQ monitors)cscript wmiget.vbs hostname username password "Select * from Win32_PerfRawData_PerfOS_Processor where Name='_Total'"(For Active Directory, Microsoft Dynamics CRM / 356 On Prem, Microsoft Dynamics AX, Microsoft Skype for Business, Network Policy Server, Microsoft Biztalk monitors)cscript wmicheckauthentication.vbs hostname username password "Select * from Win32_PerfRawData_PerfOS_Processor where Name='_Total'"
- Check the output of the command to verify the connection and identify any issues.
Note:
- If the script returns an error, try running the same query directly in the WBEMTest tool on the Applications Manager server. Refer to the Checking connectivity with WMI Tester section for instructions on using the WBEMTest tool. If an error occurs, continue troubleshooting using the same KB.
- If an error occurs in the WBEMTest tool as well, the issue is likely at the server level. In this case, recheck the prerequisites and consult the server team or Microsoft support, as WBEMTest is a built-in Windows tool. The script can collect data only after the connection is successfully established and the query executes successfully in the WBEMTest tool.
- If you are unable to find the WMI class in the WBEMTest tool, try reconstructing the WMI repository by following this KB.
If Self Help Tools or the script returns an error, but the connection succeeds in the WBEMTest tool, please reach out to our support team at appmanager-support@manageengine.com with the error or output received from the above steps. Additionally, include the latest Support Information File (SIF) from Applications Manager with 'Print all logs' enabled and the issue reproduced for further analysis.
What to do if you experience intermittent WMI connectivity errors
If you've completed the above steps and can connect to the remote server, but the WMI test fails intermittently, consider the following possibilities:
- Verify if the account used for monitoring is being locked for any reason.
- Check the Event Logs for any unusual occurrences at the time of the error, including DCOM errors.
- Ensure there have been no changes to the permissions of the monitoring account.
- Double-check the credentials used for monitoring.
- Try reconstructing the WMI repository.
- Check the Alarm History of the affected monitor to know the type of WMI error that occurs intermittently.
Note: If there are intermittent issues with WMI itself, these will be reflected in Applications Manager. If Applications Manager were the cause, the errors would occur consistently rather than intermittently. For further troubleshooting, please consult your server team or Microsoft support.What to do if you get an "Access Denied" error
During WMI connectivity, an Access Denied error usually occurs when the credentials used for that connection are incorrect, or the user account used for monitoring does not have enough permissions to make a WMI connection. Consider the following possibilities to troubleshoot Access Denied issues:
- Verify the connection using both the script execution method and the WBEMTest tool described above.
- Try using the hostname, IP address, or FQDN of the host. Determine which format works successfully and ensure the same is configured in the respective monitor.
- Ensure that the username includes the domain name (for example, DOMAIN\username).
- Make sure there aren't any leading or trailing spaces in the credentials used for monitoring.
- If you are using a non-admin user for monitoring, ensure that the steps in this KB have been followed correctly.
New to ADSelfService Plus?
Related Articles
WMI Error Troubleshooting Guide
This Knowledge Base provides troubleshooting guidance for commonly encountered Windows Management Instrumentation (WMI) errors that may occur while adding a Windows monitor or collecting metrics using WMI mode in Applications Manager. WMI errors can ...WMI/RPC Communication Errors
Applicable WMI Error Codes 0x800706BE – The remote procedure call failed 0x80010002 – Call was canceled by the message filter Overview These errors occur when Applications Manager is unable to establish or maintain WMI/RPC communication with the ...WMI Namespace and Provider Errors
Applicable WMI Error Codes 0x8004100E - Invalid Namespace Overview This error occurs when the specified WMI namespace cannot be found or accessed during monitor addition or data collection. An incorrect namespace, a missing or unregistered WMI ...WMI Query and Class Validation Errors
Applicable WMI Error Codes 0x80041017 - Invalid Query 0x80041010 - Invalid Class Overview This error occurs when the WMI query executed during monitor addition or data collection is invalid, references unavailable WMI classes or performance counters, ...WMI/DCOM Communication and Network Resolution Errors
Applicable WMI Error Codes 0x80070776 — The object exporter specified was not found. Overview This error occurs when AppManager is unable to establish WMI/DCOM communication with the target Windows server during monitor addition or data collection. ...