Analyze Tab – No data or inconsistent data

The Analyze tab is a feature that is available for monitoring Windows servers only.

If no data is in the Analyze tab after updating the AimBetter Agent, proceed with the following checks and procedures.

Make sure to proceed with the following checks with the user running the AimBetter Agent

1- Check files in the Server_Performance folder

When AimBetter Agent is working properly, a set of files from which Aimbetter pools the HTML report must exist in the monitored server.

1.1 – Local monitoring

Check these files’ existence:

• Enter the path  C:\PerfLogs\Server\Server_Performance on the File Explorer
• If there’s a folder in this path, check the existence of XML and HTML file types

1.2 – Remote monitoring

For remote monitoring, check from the agent server (where the AimBetter agent is installed) the following path on the File Explorer

 \\{serverIP}\c$\PerfLogs\Server\Server_Performance  

If remote access to this folder is blocked, check with your Network manager to find out how to enable it.

2- Check the Server_Performance task

Go to Computer Management on the monitored server (right click -> run as administrator) -> Performance -> Data Collector Sets -> User Defined and look for the “Server_Performance” task.

2.1- Remote monitoring – RPC server is unavailable

If the message when clicking on more info beside the Monitor Status red light is “RPC server is unavailable,” there may be an issue related to the communication between the agent and the monitored server.

The Perfmon component on which the Analyze depends may rely on a port between 49152 and 65535.

To solve this issue, check that there is a Ping between the agent server and the monitored server and that this port range is open.

You must also enable the Remote Event Log Management exception in the Windows Firewall Settings on the remote server to which you want to connect.

2.2 – Remote monitoring – Access is denied

If the message when clicking on more info beside the Monitor Status red light is “Access is denied,” there may be an issue related to UAC remote restrictions.

You can disable UAC remote restrictions following these steps (source – Microsoft Documentation):

1. Click Start, click Run, type regedit, and then press ENTER.
2. Locate and then click the following registry subkey:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
3. If the LocalAccountTokenFilterPolicy registry entry doesn’t exist, follow these steps:
   1. On the Edit menu, point to New, and then select DWORD Value.
   2. Type LocalAccountTokenFilterPolicy, and then press ENTER.
4. Right-click LocalAccountTokenFilterPolicy, and then select Modify.
5. In the Value data box, type 1, and then select OK.
6. Exit Registry Editor.

After this change, restart the AimBetter Agent and check again if the Server_Performance task was created.

3- Start the Server_Performance task from CMD

3.1 – Local monitoring

For local monitoring, run the following script from the CMD. Make sure to “Run as administrator”.

logman start Server_Performance

Go to Computer Management (right click -> run as administrator) -> Performance -> Data Collector Sets -> User Defined and look for the Server_Performance task.

Check that the Server_Performance task is running. A small running icon will appear beside the task name. If not, proceed to the check 4 below.

3.2 – Remote monitoring

For remote monitoring (where the Agent Server and Monitored Server are not the same), run the following script from the CMD on the Agent Server. Make sure to “Run as administrator”.

wmic /node: "{computer name/IP}" process call create "logman start Server_Performance"

Go to Computer Management on the monitored server (right click -> run as administrator) -> Performance -> Data Collector Sets -> User Defined and look for the Server_Performance task.

Check that the Server_Performance task is running. A small running icon will appear beside the task name.

4- Start the Server_Performance from the Computer Management

If you can’t start the Server_Performance task from the CMD, as explained above (item 3), go to Computer Management on the monitored server (right-click -> run as administrator) -> Performance -> Data Collector Sets -> User Defined and look for the Server_Performance task.

Right-click the Server_Performance task, click “Start.” and check if you receive an error.

4.1-If you receive an Error: “The operator or administrator has refused the request”

On the Windows start button, search for Task Scheduler -> Task Scheduler Library -> Microsoft -> Windows -> PLA.

Right-click on the job “server_performance,” click on “End,” and then “Run.”

4.2- If you receive an Error: “The operator is already in use”

• Go to Computer Management (right click -> run as administrator) -> Performance -> Data Collector Sets -> Event Trace Sessions.

• Search for NT Kernel Logger, right-click, and stop.

• See that the status changes to “stopped.”

5- Check if the Server_Performance task is the only one

In some cases, other tasks in the User_Defined file conflict with the Server_Performance task.

If there are other tasks, they should be deleted.

After any changes, restart the AimBetter Agent Service and repeat the above checks.

6- If the problem persists, delete the Server_Performance task and rebuild the WMI counters

The problem with the Analyze tab may be related to the WMI counters.

If so, you should delete the Server_Performance task and rebuild the WMI counters in the monitored server.

• Go to Computer Management (right click -> run as administrator) -> Performance -> Data Collector Sets -> User Defined and look for the Server_Performance task
• Delete the Server_Performance task.

• Restart the AimBetter Agent service and check that the Server_Performance task was re-created.
• If not, open the CMD (command prompt program) as administrator, and run the following scripts, one script at a time.

WMI rebuild – Script 1

cd c:\windows\system32
     lodctr /R

WMI rebuild – Script 2

 cd c:\windows\sysWOW64
     lodctr /R

WMI rebuild – Script 3

WINMGMT.EXE/RESYNC.PERF

• Restart the AimBetter Agent service and check that the Server_Performance task was re-created.
• If not, proceed with the WMI counters reset, running the following scripts from the CMD as administrator, one at a time.

WMI reset- Script 1

net stop winmgmt

WMI reset- Script 2

winmgmt /resetrepository

• Restart the AimBetter Agent Service.

Notice:

If you receive an error during any of the steps related to WMI rebuild or reset, restart the Windows Management Instrumentation service. This service should run in automatic mode.

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.

Restart the AimBetter Agent Service and repeat the process.

7- Settings Checks

If the above checks didn’t solve the issue with the Analyze tab, check the following settings.

• Check the Firewall Settings
• Check that the AimBetter Agent service is running in “Automatic” mode with the correct user. Click here for more details about the AimBetter Agent Service Settings.
• Check that these additional services are also running in “Automatic” mode: Windows Management Instrumentation, WMI Performance Adapter, and Performance Logs & Alerts. – click here for more details about Additional Services Settings

8- User Permissions

In some specific Windows Server versions, the user who runs the AimBetter Agent Service must have admin permission in the monitored server’s local environment to collect the Analyze Tab data.

In this case, change the Windows OS user in the AimBetter Agent Configuration program to a user with these strong credentials.

9- AimBetter folder logs

If all the previous checks and procedures didn’t solve this issue, follow the instructions to send the AimBetter folder logs to our support team.