What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

WMI Volume monitoring error after dfs

Votes:

0

I have recently enabled dfs replication on a folder from within a mount point and now my sensor will error stating "Query returned "capacity = 0". Can not process data (code: PE088)".

The sensor is monitoring free disk space, via a wmi volume sensor. The folder is on a mount point, not logical disk on a windows 2012 R2 server.

I have other sensors setup exactly the same way and the sensor was working. How can I get this to work again?

dfs prtg wmi

Created on Apr 26, 2016 4:51:52 AM



4 Replies

Votes:

0

Hi,

Thank you very much for your KB-Post. Please use our WMI Tester, run it on the PRTG Host (or host of the Remote Probe) and scan against this particular target, with the following query: Select DeviceID, FreeSpace,Capacity FROM Win32_Volume WHERE DeviceID LIKE '<deviceid>'

Please replace the deviceid-placeholder with the according device ID, copied from the settings of the according sensor in PRTG, and please post the result of the WMI Tester.

best regards.

Created on Apr 26, 2016 11:59:26 AM by Torsten Lindner [Paessler Support]



Votes:

0

Below please find the result for the entire volume, as you can see the last one returns with no capacity details. Capacity;DeviceID;FreeSpace 366997504;
?\Volume{7bc6b929-a8e7-11e3-80b9-806e6f6e6963}\;63926272 536867762176;
?\Volume{3f1b2449-a901-11e3-80bd-005056200c4c}\;231700377600 107372081152;
?\Volume{37ff2160-2c8e-11e4-80c6-005056200c4c}\;85833850880 1073738674176;
?\Volume{37ff21b2-2c8e-11e4-80c6-005056200c4c}\;148318212096 2040106315776;
?\Volume{37ff21bf-2c8e-11e4-80c6-005056200c4c}\;128201281536 1181112856576;
?\Volume{37ff21c7-2c8e-11e4-80c6-005056200c4c}\;96611848192 322119397376;
?\Volume{37ff21cf-2c8e-11e4-80c6-005056200c4c}\;54705422336 429493579776;
?\Volume{37ff21d7-2c8e-11e4-80c6-005056200c4c}\;136230006784 107372081152;
?\Volume{37ff21df-2c8e-11e4-80c6-005056200c4c}\;27370942464 1632084422656;
?\Volume{37ff21e7-2c8e-11e4-80c6-005056200c4c}\;348751073280 107372081152;
?\Volume{5555a763-bd0c-11e5-80e0-005056200c4c}\;63390490624 64054358016;
?\Volume{7bc6b92a-a8e7-11e3-80b9-806e6f6e6963}\;31751118848 "";
?\Volume{7bc6b92e-a8e7-11e3-80b9-806e6f6e6963}\;""

Created on May 23, 2016 7:03:10 AM



Votes:

0

When query on the deviceid, I got the following result Capacity;DeviceID;FreeSpace "";
?\Volume{7bc6b92e-a8e7-11e3-80b9-806e6f6e6963}\;""

Created on May 23, 2016 7:06:13 AM



Votes:

0

If the WMI System already sends no capacity information, you can only try to repair the WMI on the target: The Repair List for WMI problems

Created on May 23, 2016 7:47:29 AM by Torsten Lindner [Paessler Support]




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.