Performance Module – No Data or Partial Data

Notice

Update the AimBetter Agent as the first measure.

If there is no data on the Performance Module after updating the AimBetter Agent,

It may be related to the following reasons:

There is no data at all

Check this No data at all troubleshooting.

WMI Performance Counters issue

It may be necessary to rebuild the WMI Performance Counters on the monitored server by running the following scripts from CMD as administrator on the monitored server, one at a time.

Script 1 – WMI Rebuild 64-bit performance counters

cd c:\windows\system32
     lodctr /R

Script 2 – WMI Rebuild 32-bit performance counters

Both steps are required, even on 64-bit systems, because some providers register counters under WOW64.

 cd c:\windows\sysWOW64
     lodctr /R

Script 3 – Resynchronize WMI with Performance Counters

This forces WMI to reload and rebind its Win32_Perf* classes to the rebuilt counters.

WINMGMT.EXE/RESYNCPERF

Restart required services

Press Windows + R, type services.msc, and press Enter.

Restart Windows services:

Windows Management Instrumentation
Performance Logs & Alerts
AimBetter Agent service

Check if there is data on the Performance Tab.

Reset WMI Repository

If there is no data on the Performance Tab after the previous steps, reset the WMI repository by running the following scripts in Command Prompt (cmd) as an administrator on the monitored server, one at a time.

Script 4 – Stop WMI service

net stop winmgmt

Script 5 – Reset repository

winmgmt /resetrepository

After it finishes, you should see “WMI Repository has been reset.” Then rerun Script 3 (winmgmt /resyncperf)

WINMGMT.EXE/RESYNCPERF

Restart the services again:

Windows Management Instrumentation
Performance Logs & Alerts.
AimBetter Agent Service

Check if there is data on the Performance Tab.

Notice

The following services must be running and in automatic mode:

Windows Management Instrumentation (WMI)

WMI Performance Adapter

Windows Remote Management (WinRM)

Performance Logs & Alerts

SSMS SQL (for MSSQL Servers monitoring)

Oracle (for Oracle Database Servers monitoring)

Restarting Windows Management Instrumentation Service takes a while, and while restarting it may become stuck as well. When stuck, not even partial monitoring will run on this server until the entire server has restarted.

Configure WinRM for WMI connectivity

Ensure the network profile is set to Private or Domain (Public blocks firewall rules).

Run:

winrm quickconfig

Should return: WinRM service is already running. WinRM firewall exception enabled.

Verify connectivity:

winrm id

Restart the AimBetter Agent service and check if there is data in the Performance tab

Reboot

In most cases, the steps above restore functionality without a reboot. However, if issues persist (perhaps due to locked files or services), a full server reboot will cleanly restart WMI and performance services. A reboot forces Windows to reload all counters and services from scratch, clearing transient issues. Schedule a reboot during maintenance hours if possible. Avoid unnecessary reboots by first confirming that the steps above resolve the issue.

Remote monitoring – Access is denied

If the message that appears when you click More Info next to the Monitor Status red light is “Access is denied,” proceed with WMI Troubleshooting.

No Data in MSSQL/Oracle tabs

If monitoring data is available throughout AimBetter except in the database-specific tabs (MSSQL, Oracle, DB, or Tablespace), verify that the database server appears under its corresponding Host in the Server Tree.

If the database server is not beneath the Host level, open Server Settings, disable database server monitoring for that server, and then re-enable it. This refreshes the monitoring configuration and restores the database server association.