Just installed APM 2 and cannot get it to poll servers using WMI. The message I get is "Server Unavailable using WMI Unable to connect to "X.X.X.X" for WMI access. I was able to verify that WMI is working on multiple servers with the appropriate credentials using your little free teaser application "Solarwinds Exchange Monitor", so I think that WMI is wokring on the servers. I am guessing that this is coming from the poller, not the servers.
Please let me know what I should look at to troubleshoot . . .
Running NPM 9.1 SP2 w/ APM 2 SP2
Was Exchange Monitor running on the Orion Server or the target node? You need to verify that you have WMI access from the Orion Server to the target node. The error message you are getting indicates that WMI can not connect to the target node.
Here's a link to a tech ref article on how to test WMI connectivity: http://www.solarwinds.com/support/apm/docs/WMITesting.pdf
Josh ClarkSolarWinds Development Team
I am having the same issue and was able to test WMI access from the Orion server. I was able to Enumerate Classes on the target server with no problems. Any ideas?
I'm having the same issue. Enumerating classes using wbemtest works fine. Started ticket 56579.
This was my fault. I didn't click "Set Component Credentials" and then "Submit" when applying the template.
If you edit the application monitor, it will cause the monitors to be polled right then (it may take a few seconds for the results to get back). You don't have to change any of the settings, just open up the edit page and click submit
is it possible that the security rights on the account your using are no longer suffcient to be used for wmi?
Christian
I have this issue as well, NPM9 SP2, APM v2. I also used the wbemtest.exe app and was able to enumerate 895 classes. When I use the default IIS template, only the "service" monitors work, the "counters" monitors fail with "Server unavailable using WMI."
I had the same issue. The way I fixed it was to go into the template, and expand each component type. I set each "Credential for Monitoring" to the correct credential for each component type, then hit "Submit" at the bottom.
30 seconds later, everything showed up green except the one service/process (MSExchangeES) that isn't started (and it doesn't start unless it needs to). Not sure why MSExchangeES was included in that default template. I deleted it.