Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

WMI Error in APM

Hello,

Whenever I attempt to setup a WMI monitor in APM (for instance the "SQL Server Process - WMI" test), I keep getting the following error on any server that I attempt to monitor when I click the "Test" button:

Testing on node SERVERNAME: failed with 'Undefined' status The type initializer for 'System.Management.MTAHelper' threw an exception.

Any ideas?

Thanks in advance!

Find more posts tagged with

Accepted answers

All comments

aLTeReGo

Out of curiosity, what version of APM are you running? This looks like it may be credentials related. Double check the credentials you provided when assigning the application template has sufficient permissions. By default WMI requires local administrator permissions to the monitored host.

Petr.Vilem

According to this article it can be related to damaged registry (on poller machine).

Check the value of HKCR\CLSID\{A8F03BE3-EDB7-4972-821F-AF6F8EA34884}\InprocServer32\(Default)

If you are on 64bit OS and will find C:\WINDOWS\SysWOW64\mscoree.dll try change to C:\Windows\system32\mscoree.dll

rudicd

We are using version 4.0 of APM. The credentials are correct because they work for the other APM performance monitor counters, just not the WMI counters.

rudicd

My registry value is already set to C:\Windows\system32\mscoree.dll so unfortunately, I don't think that's the issue. Thank you for your help!

aLTeReGo

This error is related to a bad WMI repository. To repair the WMI repository complete the following steps on the remotely monitored host.

Open a command prompt.
Type net stop winmgmt and press Enter.
Rename the folder %windir%\System32\Wbem\Repository to %windir%\System32\Wbem\Repository_bad
Open a command prompt and type net start winmgmt and press Enter.

When you've completed these steps you can retry WMI monitor in APM against this machine.

rudicd

I can't imagine the repository is corrupt... I've tried these WMI counters on 5 different servers and I get the same error on all.

It seems to me like it would be an issue with the Orion server (or an APM issue) since it's not working on any of these servers.

aLTeReGo

WMI issues can usually be lumped into three categories

Insufficient privileges (Use local or domain administrator accounts to alleviate this issue)
Firewall Policy, Proxy, or Router Access Control Lists prevent communication between APM and the remote server.
This can be remedied by allowing TCP Port 135 and all ports greater than 1024 between both servers, or by defining a single static port for WMI to use.
WMI repository is corrupt. This usually occurs for only one server, but can be more or all if the repository was corrupted in the original baseline image that the other servers are based on. Also other products such as SCOM agents are notorious for corrupting the WMI repository.

The guide below should help to resolve any WMI issues you encounter.

http://www.solarwinds.com/documentation/apm/docs/APMWMITroubleshooting.pdf