Troubleshooting Basic WMI Connection
Troubleshoot Basic WMI connectivity
If you're using Applications Manager version 15470 or above, navigate to Admin > Self Help Tools and select the monitor type to troubleshoot the issue. Click here for more details.
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 in Applications Manager installed machine.
- Navigate to the <Applications Manager Home>\working\conf\application\scripts directory.
- Execute the following command by replacing hostname, username, and password with the credentials of the remote server used in the monitor:(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.
- If an error occurs during the above steps, try running the same query directly in the wbemtest tool on the Applications Manager server by connecting to the remote server. Refer the steps under the section "Checking connectivity with WMI Tester" for instructions on using the wbemtest tool. If an error occurs, troubleshoot using the same KB.
- If an error occurs in the wbemtest tool as well, the issue is likely at the server level itself. In this case, recheck the prerequisites and consult the server team or Microsoft support, as wbemtest is a built-in Windows tool. Only after successfully establishing the connection and running the query in the wbemtest tool will we be able to run the script and collect the data.
If you encounter an error in Self Help Tools or while running the script directly but are able to connect using 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 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 randomly, consider the following possibilities:
- Verify if the account used for monitoring is getting 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.
If there are intermittent issues with WMI itself, these will be reflected in Applications Manager. Thus, it is unlikely to be an issue within Applications Manager, as errors would occur consistently rather than only at specific times. For further troubleshooting, please consult your server team or Microsoft support.
New to ADSelfService Plus?
Related Articles
Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the steps below for troubleshooting: Step 1: Check the RUM Agent configuration Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...Configuring non-admin user account for WMI monitoring
By default, Windows allows only members of the Administrators or Domain Admin groups to read WMI class information. However, you can configure a regular user to access WMI information by performing the following steps on the server that needs to be ...Setting WMI access through Active Directory and Group Policy Object for non-admin user
In our case, we run Active Directory on Windows 2008 R2 and we want to scan the target machine which is Windows 2012 R2 machine. Our domain is called “APMCLU” and we name our dedicated WMI user-account “wmiuser”. First – Setting done from Active ...Troubleshooting WinRM errors
This KB serves as a guide for troubleshooting errors when using the WinRM mode of data collection. First, ensure that all the following conditions are met: Refer to the below link and check if all the WinRM prerequisites have been completed properly ...Steps to verify WMI access for Non-Admin Domain user
This guide provides how to enable and test WMI access with a regular domain user without generic admin rights. Make sure you have followed the steps in the article Setting WMI access through Active Directory & Group Policy Object. This ensures you ...