How do I enable data collection for Cluster Details in the MS SQL Monitor?
The Cluster Details tab is displayed only when the following prerequisites are met:
- Applications Manager is installed on Windows. (Cluster Details are not supported when Applications Manager is installed on Linux.)
- A Domain Administrator account (or an account with sufficient privileges to execute WMI queries) is available.
- Windows authentication credentials have been configured for the MS SQL monitor, or a Windows monitor has been added for the SQL Server host.
If these prerequisites are satisfied but the Cluster Details tab still displays no data, follow the steps below.
Step 1: Run the cluster verification script
From the Applications Manager server, open a command prompt and navigate to:
<AppManager_Home>\working\conf\application\scripts\
Run the following command:cscript wincluster.vbs <ClusterName> <UserName> <Password> 0
Example:
cscript wincluster.vbs servcluster1 domain\admin admin 0
Step 2: Verify the script output
If the script returns the cluster information successfully
If the script returns the expected data but the Cluster Details tab is still empty, share the following with the Applications Manager Support team:
- Screenshot of the Edit Monitor page
- Screenshot of the Cluster Details tab
- Script output
- Support Information File (SIF)
If the script returns the following error
Copyright (C) Microsoft Corporation. All rights reserved.
Error # Access is denied.
Or if errors are logged, continue with the following checks.
Step 3: Verify WMI connectivity using WBEMTest
From the Applications Manager server:
- Launch WBEMTest.
- Connect using the namespace:
root\mscluster
For a remote cluster, connect using:
\\<Cluster_IP_or_Hostname>\root\mscluster
Using the same Windows credentials configured in Applications Manager.
If the connection is successful:
- Click Query.
- Execute the following WMI query:
SELECT * FROM MSCluster_Resource
Verify that the query returns the cluster resource information.
Step 4: Verify WMI permissions
Ensure that the configured Windows account has sufficient permissions to:
- Access the root\mscluster namespace.
- Execute WMI queries against the cluster.
Note: If the account does not have the required WMI permissions or cannot access the root\mscluster namespace, the Cluster Details tab will display no data.If the issue persists
If all the above checks succeed but the Cluster Details tab still does not display data, refer to the relevant troubleshooting KB article or contact Applications Manager Support with the requested diagnostic information.
New to ADSelfService Plus?
Related Articles
Real User Monitor (RUM) - Troubleshooting guide
If your Real User Monitor has not collected data for an extended period, follow the steps below to troubleshoot the issue. Step 1: Verify the RUM Agent configuration Real User Monitoring requires the RUM Agent to be installed and mapped to ...Troubleshooting Hyper-V-Cluster data collection
In Hyper-V clusters, the data is collected via WMI. So if any of data is not retrieved properly in the UI, you can check and troubleshoot by executing the VBScript. 1) Go to Applications Manager's installed directory and navigate to the path ...How to configure Output Settings for Script Monitor?
Below are the details on how to configure Script Monitor Output Settings and expected output format, Output Configuration: Expected Output File Format: In the output file, Scalar data should be separated by scalar delimiter, here name, cpu, javaHeap ...Script/Custom Monitors - Alarms configured for Table rows were missing
In the Applications manager , users have the ability to manage the table rows of a script or custom monitor type according to their specific requirements. This can be done by enabling the "Enable Script Row Deletion" option. For example, let's ...DNS Monitor - Troubleshooting
Common DNS Monitor Errors and Troubleshooting Guide 1. Host Not Found Description: The DNS server was unable to locate the requested lookup address. Possible Causes: This may happen if the hostname is incorrect, the domain does not exist, or there is ...