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 prerequisites to be done Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...
                    • Troubleshoot - RUM Agent silent installation

                      RUM Agent silent installation can fail on various factors based on your environment, troubleshoot with the help of error message shown while running the script. Below are the list of the error messages thrown from the script and its troubleshooting ...
                    • Troubleshoot - Duplicate APMInsight Monitors

                      Introduction Duplicate monitors might be created in APMInsight due to various reasons. This article will help you identify and resolve the issue of duplicate monitors. The common causes include: - Changes in monitor configuration. (apminsight.conf ...
                    • How to troubleshoot when having error 'No data available' in Solaris Monitor in Telnet/SSH Mode

                      Important Note: Establish a Telnet or SSH connection to the remote Solaris machine before proceeding. Use the same user account that is used for monitoring in the product to execute the following commands. 1. Disk Errors: Command: echo ...