Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

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

0
Posted

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

0

Reason: This is because the WMI class is not available or not registered. Solution: Step 1: Execute the following command in the remote machine where .NET is running. This will reconstruct and register the WMI classes. Then in Applications Manager go to the .NET monitor page, click Edit Monitor link on the right side, give the password and save the settings. Then check whether the data is collected for the attributes for which Troubleshoot link was shown. Step 2: In case even after this, if data is not shown, kindly send us the following details to support@appmanager.

0

Reason: This is because the WMI class is not available or not registered. Solution: Step 1: Execute the following command in the remote machine where .NET is running. This will reconstruct and register the WMI classes. Then in Applications Manager go to the .NET monitor page, click Edit Monitor link on the right side, give the password and save the settings. Then check whether the data is collected for the attributes for which Troubleshoot link was shown. Step 2: In case even after this, if data is not shown, kindly send us the following details to appmanager-support@manageengine.com • 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 following folder C:\WINDOWS\system32\wbem\Logs\wmiadap.log • In Applications Manager machine, go to the directory. Kindly invoke the wmiDotNetDebug.vbs file – cscript wmiDo

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123