I'm having this problem with a number -- although not all -- of Windows 2012 R2 servers. For the WMI sensors for CPU Load and Pagefile Usage I'm getting this through the PRTG interface:

The WMI query does not return any results. The reason might be an issue with the host's WMI system. For more information, see https://helpdesk.paessler.com/en/support/solutions/articles/1093. (code: PE016)

I've been through that and done many of the (less drastic) things suggested there. None of them have helped. The really confusing thing, though, is using PowerShell from the PRTG server returns values!

PS C:\Windows\system32> $adminaccount = "[hostname]\monitor"
PS C:\Windows\system32> $PASSWORD = ConvertTo-SecureString [password] -AsPlainText -Force
PS C:\Windows\system32> $UNPASSWORD = New-Object System.Management.Automation.PsCredential $adminaccount, $PASSWORD
PS C:\Windows\system32> Get-WmiObject -query "SELECT * FROM Win32_PageFileUsage" -ComputerName "[IP address]" -Credential $UNPASSWORD

Caption                                 Name                                                                  PeakUsage
-------                                 ----                                                                  ---------
C:\pagefile.sys                         C:\pagefile.sys                                                            1642

I'm mystified as to why this would work perfectly, just not through PRTG. Any ideas?

Article Comments

Hello,

please use the WMI Tester https://www.paessler.com/de/tools/wmitester to run these query:

SELECT percentusage FROM Win32_PerfFormattedData_PerfOS_PagingFile WHERE Name = '_Total'

(You could also use Get-WmiObject in Powershell of course, to see what you get, but in any case please also test with our app.)

Do you then get a result? As we only read that one property, and also filter with WHERE, the result could be different


Mar, 2022 - Permalink

Testing from PowerShell returns nothing. The WMI Tester app doesn't even appear to be doing anything so I guess that means it's returning nothing. Testing with a known good server works so, yes, it's returning nothing.


Mar, 2022 - Permalink

Hello,

if there is nothing returned, the sensor cannot work either.

If you widen the query (using less filters), can you get at least some output?

If rebooting the computer does not help, please also have a look at the WMI repair list.


Mar, 2022 - Permalink

It turned out that the monitor account had been removed from the Performance Monitor Users group on all the servers with issues. I'm not clear on how that happened but I don't think it has anything to do with PRTG, so problem solved.


Mar, 2022 - Permalink