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 ADManager Plus?

                    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 ...
                      • How to monitor the .NET Core app which was published in the self contained mode?

                        To learn how to monitor the .NET Core app which was published in the self contained mode, refer this link.
                      • Frequently asked questions - SAP monitor

                        1. SAP monitor's Health is always critical/warning state along with "System Error occurred" alert message. What should I do? These alerts are triggered when Applications manager receives Alerts from the SAP server itself. The same can be viewed under ...
                      • How to identify and resolve conflicts between other APM products and the APM Insight .NET agent?

                        If you are experiencing any of the issues mentioned below and you suspect that another APM product is interfering with the Applications Manager .NET agent, you can follow the steps given in this article to troubleshoot and fix the issues: 1. The .NET ...