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

Windows Servers not showing up for Report selection

I have 2 (out of 100) Windows servers that are not showing up as a report selection. In the Servers web page, I have N/A for Disk, CPU, Mem, Net, and Uptime. I have uninstalled and reinstalled Profiler Agent 4.9.3 but it has not resolved the issue. Any ideas as to how to correct this?

Find more posts tagged with

Accepted answers

ctanner

There were two separate issues in this case:

1) the storage module was hanging due an issue with the HBAAPI.dll. We disabled local storage mapping to resolve the issue.

2) Some of the performance counters that we were requesting were not available

All comments

ctanner

there's a few things to check here:

Are the server's licensed? This can be verified by checking if the license check box in the edit icon of the server console is checked.

Has the server recently collected data? Look on the console for the device and see what the 'Since Last Collect' value is.

Are you able to view the modules status? Click the Stop light icon, can you see modules online and offline?

Does the agent have the most recent configuration? Click the wrench icon and make a change to the configuration and save it. This will trigger a push of the agent configuration.

What report are you trying to run? Do these two servers have data relevant to this report?

rkrejsa

Both servers are licensed.

Last Successful Collect is seconds and a few minutes.

I am able to view the module status for each one.

I changed the configuration for each and still not showing up.

The Quick Report is Storage - Volume Usage Forecast - and they both have local storage associated with them.

ctanner

Try clicking the wrench icon and setting Disable WMI: to true.

After about 15 minutes if it's still not working click the stoplight and click the Rules Module. Copy and paste the last 10-15 lines here for us.

rkrejsa

10 Sep 2010 10:03:59 [Unscheduled Rule Executor] - Running rule "RealTime Traps"
10 Sep 2010 10:03:59 [Unscheduled Rule Executor] - Result for Condition : rtdata_cpu = {cidata=1.08, conditionString=Confidence Interval where System Level == true , cistatus=00, ciwarnotify=false, timestamp=1284130979242, cierrnotify=false, retvalue=true}
10 Sep 2010 10:03:59 [Unscheduled Rule Executor] - Result for Condition : rtdata_mem = {cidata=2.16470323E9, conditionString=Confidence Interval where System Level == true , cistatus=00, ciwarnotify=false, timestamp=1284131038941, cierrnotify=false, retvalue=true}
10 Sep 2010 10:03:59 [Unscheduled Rule Executor] - Result for Condition : rtdata_disk = {cidata=133528.02, conditionString=Confidence Interval where System Level == true , cistatus=00, ciwarnotify=false, timestamp=1284131039144, cierrnotify=false, retvalue=true}
10 Sep 2010 10:03:59 [Unscheduled Rule Executor] - Result for Condition : rtdata_net = {cidata=126.590004, conditionString=Confidence Interval where Unknown == true , cistatus=00, ciwarnotify=false, timestamp=1284131039035, cierrnotify=false, retvalue=true}
10 Sep 2010 10:03:59 [Unscheduled Rule Executor] - Result for Condition : rtdata_uptime = {uptime_in_ms=2.52157645E9, conditionString=Extract, timestamp=1284131038832, retvalue=true}
10 Sep 2010 10:03:59 [InvokerThread[mod.adm.rules.Rules.REMOTE_putevalresult]] - RuleEvalStore putting eval result for rtdata_cpu
10 Sep 2010 10:03:59 [InvokerThread[mod.adm.rules.Rules.REMOTE_putevalresult]] - RulesScheduler Received notification on rtdata_cpu
10 Sep 2010 10:03:59 [Unscheduled Rule Executor] - Starting RuleSet --> "TekTools"
10 Sep 2010 10:03:59 [Unscheduled Rule Executor] - Running rule "RealTime Traps"
10 Sep 2010 10:03:59 [Unscheduled Rule Executor] - Result for Condition : rtdata_cpu = {cidata=0.84, conditionString=Confidence Interval where System Level == true , cistatus=00, ciwarnotify=false, timestamp=1284131039222, cierrnotify=false, retvalue=true}
10 Sep 2010 10:03:59 [Unscheduled Rule Executor] - Result for Condition : rtdata_mem = {cidata=2.16470323E9, conditionString=Confidence Interval where System Level == true , cistatus=00, ciwarnotify=false, timestamp=1284131038941, cierrnotify=false, retvalue=true}
10 Sep 2010 10:03:59 [Unscheduled Rule Executor] - Result for Condition : rtdata_disk = {cidata=133528.02, conditionString=Confidence Interval where System Level == true , cistatus=00, ciwarnotify=false, timestamp=1284131039144, cierrnotify=false, retvalue=true}
10 Sep 2010 10:03:59 [Unscheduled Rule Executor] - Result for Condition : rtdata_net = {cidata=126.590004, conditionString=Confidence Interval where Unknown == true , cistatus=00, ciwarnotify=false, timestamp=1284131039035, cierrnotify=false, retvalue=true}
10 Sep 2010 10:03:59 [Unscheduled Rule Executor] - Result for Condition : rtdata_uptime = {uptime_in_ms=2.52157645E9, conditionString=Extract, timestamp=1284131038832, retvalue=true}

ctanner

There were two separate issues in this case:

1) the storage module was hanging due an issue with the HBAAPI.dll. We disabled local storage mapping to resolve the issue.

2) Some of the performance counters that we were requesting were not available