Overview

This article provides troubleshooting steps to identify and resolve data collection failures for Windows monitors configured in WMI mode. If one or more metrics are not being collected, the steps in this article will help determine whether the issue is caused by:

• Applications Manager script execution

• WMI connectivity between the Applications Manager server and the target server

• WMI query execution

• WMI configuration on the target Windows server

Follow the validation methods below in the given order to isolate the root cause.

Validation Methods

1. Execute the metric using the Self Help Tool.

2. Execute the corresponding VBS script from the Applications Manager server.

3. Execute the WMI query from the Applications Manager server using WBEMTEST.

4. Execute the same WMI query directly on the target Windows server.

1. Validate Data Collection Using the Self Help Tool

The Self Help Tool allows you to execute Windows monitoring scripts directly from the Applications Manager UI and verify whether the required metrics are being collected successfully.

Steps

1. Navigate to Settings → Tools → Self Help Tools.

2. Select the required server from the Choose the Host drop-down list.

3. In the Type field:

   • Select Monitor Type.

   • Choose Windows as the monitor type.

4. Select the required metric(s).

5. Click Execute.
   

2. Execute the VBS Script from the Applications Manager Server

Applications Manager collects Windows metrics using VBS scripts. Executing the script manually helps verify whether the issue is related to script execution, authentication, or WMI connectivity.

Steps

1. Log in to the server where Applications Manager is installed.

2. Open Command Prompt with Run as Administrator.

3. Navigate to:

   <Applications Manager Home>\working\conf\application\scripts

4. Execute the appropriate script.
   

1. For a remote Windows server:
   

1. 

   cscript cpu.vbs <HOSTNAME> <USERNAME> <PASSWORD>

1. For the local Applications Manager server:
   

1. 

   cscript cpu.vbs localhost

Note:
Refer to the Script, Namespace, and WMI Class Used KB to identify the corresponding VBS script for each Windows metric.

3. Execute the WMI Query from the Applications Manager Server

If the VBS script fails, verify whether the Applications Manager server can execute the WMI query directly using WBEMTEST.

Steps

1. Open WBEMTEST on the Applications Manager server. (Refer to the steps provided under the section "Checking connectivity with WMI Tester" for instructions on using the WBEMTEST tool.)

2. Connect to the target Windows server using the required WMI namespace.

3. After the connection is established, click Query.

4. Copy the WQL query corresponding to the required metric from the Script, Namespace, and WMI Class Used KB.

5. Execute the query.

Important: Ensure that you connect using the correct WMI namespace required by the query.

Result Interpretation

• If the query executes successfully, WMI connectivity is functioning correctly.

• If the query fails, verify the reported error and continue with the next validation method.

4. Execute the WMI Query Directly on the Target Windows Server

If the WMI query fails from the Applications Manager server, execute the same query locally on the target server to determine whether the issue is related to the Windows system itself.

Steps

1. Log in to the target Windows server.

2. Open Windows Management Instrumentation Tester (WBEMTEST):

   • Open Run.

   • Type wbemtest.

   • Click Connect.

3. Connect to the required WMI namespace.

4. Click Query.

5. Execute the same WQL query used in the previous step.

Result Interpretation

• If the query succeeds locally but fails from the Applications Manager server, the issue is related to remote WMI connectivity, firewall settings, DCOM configuration, or user permissions.

• If the query also fails locally, the issue is related to the target server's WMI configuration, missing WMI classes or namespaces, corrupted WMI repository, or disabled performance counters.

Next Steps

Based on the validation results:

• If script execution fails with a specific WMI error, refer to the WMI Error Troubleshooting Guide.

• If authentication or RPC errors are encountered, refer to the Windows Monitoring - FAQ.

• If performance counter classes return no data, Enable Windows Performance Counters Through Registry.