Has anyone run across this yet when attempting to enumerate a node to select a wmi entry to monitor?
"Timeout while waiting for job result. "
This occurs when I select any windows server, including the collector itself. The credentials used are correct b/c it's the same one that is used to collect data on the legacy apm 1.0 functions. I see the wmi performance adapter starting then stopping immediately on the remote host. No other error messages or on the collector.
Collector:NPM 9 SP2APM 2.0OS: Win2K3 R2 STD x64 SP2
How many component monitors do you have configured? Go to APM Settings | License Summary fo a count.
Josh ClarkSolarWinds Development Team
3106
I guess I am curious what this would matter... I kind of figured this was simply going to enumerate the remote host for available win32_perf* classes?
There's a known issue relating to large numbers of monitors. We have a fix that's currently in test and should be out with SP1.
Denny LeCompte Sr. Product Manager, Orion SolarWinds Austin, TX
Well, with so few monitors, we're not sure. Could you run Diagnostics, open a Support Ticket, and attach the diagnostics to the ticket?
denny.lecompte: Well, with so few monitors, we're not sure. Could you run Diagnostics, open a Support Ticket, and attach the diagnostics to the ticket?
Done. Case # 59541.
Thanks.
Are there any updates to this issue. I am seeing the same problem. I just applied SP1 this morning.
Chad TschappatSioux Falls, SD
(2) Orion 9.1 SP2 SLX(1) Orion 9.1 SP2 SLX Poller(1) Orion 9.1 SP2 SLX Hot-Standby APM v2 SP2 AL500 6200+ elements and counting
I was instructed to un-install/re-install APM and re-apply SP1. I haven't had a chance to do that yet. I'll let you know how it goes.
I just tried that. It did not work. I am still getting the timeout error.
ctschap:I just tried that. It did not work. I am still getting the timeout error.
Any further word from Support yet?
This issue should be fixed in an upcoming service pack.
