We have several HP servers under our control. All of them are running the same ESXi version but 1 of our HP servers returns in prtg with the following message:

Warning. 4 elements return a warning state: Power Supply 3 Power Supplies - unknown; System Board 9 Fans - unknown; System Board 11 Memory: Correctable ECC logging limit reached - unknown; System Board 11 Memory: Uncorrectable ECC - unknown

There is no power supply 3 on the server.

The VMware Host Hardware Status (SOAP) Sensor reports exactly the same errors as reported by the ESXi host, please use vCenter or vSphere to check out Hardware Status of your ESXi host, the error will be displayed there as well, this will allow you to confirm the sensor's message.


Starting on PRTG's version 15.3.19 it's possible to ignore specific Errors or Warning within the Sensor's settings, please check the Manual: VMware Host Hardware Status (SOAP) Sensor for details.


PRTG collects the data from the host that was added as device in PRTG and there might be indeed differences of what you see whether you connect to let's say vCenter or to an ESXi host directly with vSphere.

For example if you have added vCenter as device in PRTG it will poll vCenter for this data, not the ESXi host directly. Now if you are connecting to a single ESXi host with vSphere to check "Hardware Status", you might not see the same data as there might be a syncing issue between vCenter and the ESXi host. If you connect to the same device that you added in PRTG with vSphere, you should the error there too and it might be necessary to restart the management agents to refresh data properly.


Problem was solved in a VMWARE Update : https://docs.vmware.com/en/VMware-vSphere/6.7/rn/esxi670-202008001.html#esxi670-202008102-sg-resolved 

PR 2577878: You see many health warnings in the vSphere Client or vSphere Web Client and mails for potential hardware failure In the vSphere Client or vSphere Web Client, you see many health warnings and receive mails for potential hardware failure, even though the actual sensor state has not changed. The issue occurs when the CIM service resets all sensors to an unknown state if a failure in fetching sensor status from IPMI happens. This issue is resolved in this release.


Disclaimer:
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.