Why am I getting a troubleshoot link for the attributes shown in .NET monitor pages?

Why am I getting a troubleshoot link for the attributes shown in .NET monitor pages?

Reason:

The WMI class is not available or not registered.

Solution:

1. Execute the following command, in the remote machine where .NET is running : 

      <wmiadap /f>

This will reconstruct and register the WMI classes. 

2. In Applications Manager, go to the problematic .NET monitor details page and click the 'Edit Monitor' link present in the right side menu. This opens the monitor configuration page.

3. In the monitor configuration page, give the password and save the settings. 

4. Check whether the data is collected for the attributes for which the troubleshoot link was shown.

5. If the data is still not shown, contact our support portal, at appmanager-support@manageengine.com, with the following details: 

  • OS version and Service Pack details of remote machine. Say for example Windows 2003 with Service Pack 1.
  • WMI ADAP log file in the remote machine. This is present in the folder 'C:\WINDOWS\system32\wbem\Logs\wmiadap.log'.
  • In the Applications Manager host machine, navigate to 'APPMANAGER_HOME/working/conf/application/scripts'.
  • Kindly invoke the 'wmiDotNetDebug.vbs' script with the syntax as follows : 

    cscript wmiDotNetDebug.vbs<Hostname> <username> <passdowrd> >> debug.txt

  • After executing the above command, you will get a debug.txt file. Send this file, to the support portal mentioned above, along with the other details requested. 

                  New to ADSelfService Plus?

                    • Related Articles

                    • Troubleshooting URL Monitor

                      Here are few of the common errors you may come across in URL monitor, we have mentioned the steps you can follow to troubleshoot them. General troubleshooting for URL monitor Ensure that the URL is accessible from the server in which Applications ...
                    • 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 ...
                    • 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 ...
                    • 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 ...
                    • Mail Server Monitor - Troubleshooting

                      Common Mail Server Monitor Errors and Troubleshooting Guide 1. Unknown Host Error Description: This error occurs when the mail client cannot resolve the hostname of the mail server to an IP address. The issue typically arises from DNS resolution ...