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

The channel values of my Exchange Database sensor are broken. What can I do?



I use the Exchange Database (Powershell) sensor to monitor databases on my Exchange server. However, the sensor seems to not work correctly. The Mounted channel does not appear as gauge at all and the values of this channel and the Is Valid channel show a strange message:

1 (configured lookup prtg.standardlookups.yesno_0based.stateyesok is empty or not available)

Is this a bug in the Exchange Database (Powershell) sensor? How can I get correct channel values for my Exchange database?

Broken Channel Values in Exchange Database (Powershell) Sensor

channel error exchange exchange-database exchange-powershell powershell prtg

Created on Nov 4, 2015 12:32:57 PM by  Gerald Schoch [Paessler Support]

Last change on Nov 4, 2015 12:37:46 PM by  Gerald Schoch [Paessler Support]

1 Reply

Accepted Answer



This article applies to PRTG Network Monitor 15.3.18, 15.3.19, 15.4.19, and 15.4.20

Corrupt Channel Values of the Exchange Database Sensor

With PRTG version 15.3.18 we released several improvements for the Exchange Database (Powershell) sensor and the Exchange Mailbox (Powershell) sensor together with the new Exchange Database DAG (Powershell) sensor (see the release notes history for version Unfortunately, this caused another small issue so that the channels Is Valid and Mounted of newly added Exchange Database sensors do not use the correct lookup definitions.

Because of this you see the message 1 (configured lookup prtg.standardlookups.yesno_0based.stateyesok is empty or not available) in these channels. This happens only for Exchange Database sensors that you add to a PRTG installation with version 15.3.18 through 15.4.20.

Correcting Values of Exchange Database Sensor Channels

To correct these malfunctioning sensor channels, just select the correct lookup file in the settings of both channels: prtg.standardlookups.exchangedag.yesno.stateyesok

  1. Open the Overview tab of the Exchange Database (Powershell) sensor.
  2. Open the settings of the channel Is Valid by clicking its name.
  3. For the Value Lookup setting choose the correct lookup prtg.standardlookups.exchangedag.yesno.stateyesok (most probably this is initially set to None).
  4. Click the Apply button.
  5. Choose the channel Mounted from the dropdown list at the top of the Edit Channel window to open its settings.
  6. Choose the lookup prtg.standardlookups.exchangedag.yesno.stateyesok here as well in section Value Lookup.
  7. Click the Ok button to close the window and to save your changes.

Note: If you have more than one Exchange Database (Powershell) sensor with malfunctioning sensor channels, you can use Multi-Edit for these sensors to choose the correct lookup file for all affected sensor channels at once.

The Exchange Database (Powershell) sensor channels Is Valid and Mounted now show the correct lookup values Yes or No. We fixed this malfunction of newly added sensors for the upcoming PRTG version 15.4.21. If you add a new Exchange Database sensor to PRTG, the correct lookup is automatically used as of this version.

Exchange Database (Powershell) Sensor with Correct Values

Note: This fix does not apply to already existing Exchange Database sensors which were added in version 15.3.18 through 15.4.20, so they will not automatically use the correct lookup with version 15.4.21. Either you choose the lookup manually as described above or you have to add these sensors anew.

Created on Nov 4, 2015 12:44:54 PM by  Gerald Schoch [Paessler Support]

Last change on Nov 19, 2015 1:35:03 PM by  Gerald Schoch [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.