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
Store

AppBuilder - custom wmi creation - timeout

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 SP2
APM 2.0
OS: Win2K3 R2 STD x64 SP2

Find more posts tagged with

Accepted answers

All comments

josh.clark

How many component monitors do you have configured? Go to APM Settings | License Summary fo a count.

jamesbernhard

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?

FormerMember

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.

Ohmus

I'm getting these same timeout errors when trying to create either a WMI or SNMP monitor. I applied SP1 and it didn't help. I only have 129 monitors.
Thanks

FormerMember

Well, with so few monitors, we're not sure. Could you run Diagnostics, open a Support Ticket, and attach the diagnostics to the ticket?

Ohmus

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.

ctschap

Are there any updates to this issue. I am seeing the same problem. I just applied SP1 this morning.