Learn about warning messages
- Last UpdatedJan 22, 2025
- 3 minute read
These messages are returned when the function has completed successfully but the results might be different than expected.
|
Message |
<PI point name> (point ID) counter path does not have computer name part |
|
Description |
This message is logged when the interface loads PI point with an extended descriptor attribute that omits the computer name from the performance counter path. If you omit the computer name, the interface monitors localhost, but this omission can cause problems if the interface is later moved to another node or if the counter desired was not associated with the local machine. |
|
Message |
<PI point name> (point ID) calculate value: not enough samples - value is dropped (two samples required to calculate the value) |
|
Description |
Warning message is logged when the interface fails to collect two performance data samples necessary for calculating the value to be sent to the PI Server. The warning may appear in the log when the interface is overloaded by too many devices, scan classes or loaded PI points. |
|
Message |
<PI point name> (point ID) calculate value: bad counter value received - value is dropped (previous sample data must be smaller than the last) |
|
Description |
This message is logged when the interface receives bad data from a performance data provider. Typically, performance data values are calculated using a continuously incremented value and time stamp returned by a provider. This message is logged when the most recent sample's data variable is not greater than the previous sample's data. A similar message is logged for a mismatch between time stamp variables. |
|
Message |
<PI point name> (point ID) calculate value: bad counter value received - value is dropped (invalid frequency value) |
|
Description |
This message is logged when the interface receives bad data from performance data provider. In some cases, performance data providers return samples that contain two pieces of information: (1) sample value and (2) the frequency at which this sample was collected. In the further calculation of the performance data value, the frequency part serves as a denominator, thus its value cannot be 0. This message is logged when the value of the frequency is 0. |
|
Message |
<PI point name> (point ID) calculate value: bad counter value received - value is dropped (invalid time value) |
|
Description |
This message is logged when the interface receives bad data from a performance data provider. In some cases, performance data providers return samples that contain two pieces of information: (1) sample value and (2) time stamp at which this sample was collected. In the further calculation of the performance data value, the time stamp part serves as a denominator, thus its value cannot be 0. This message is logged when the value of the time stamp is 0. |
|
Message |
<PI point name> (point ID) calculate value: bad counter value received - value is dropped (invalid counter type) |
|
Description |
This message is logged when the interface receives bad data from performance data provider. The interface, as a compliant performance data consumer, expects data from performance data providers to be returned in one of the predefined formats. If the data provider fails to send data in the format defined by Microsoft specifications, this data is dropped and the message is logged. |
|
Message |
<PI point name> (point ID) calculate value: bad counter value received - value is dropped (invalid base counter) |
|
Description |
This message is logged when the interface receives bad data from performance data provider. In some cases, the performance data sample returned from the provider contains a "base counter", which is necessary for further calculation of the value. The message is logged when the provider fails to return this base counter in the sample. |
|
Message |
<PI point name> (point ID) calculate value: bad counter value received - value is dropped (encountered an unidentified counter) |
|
Description |
This message is logged when the interface receives bad data from a performance data provider. The interface is written and tested on Windows 8 and Windows 2012 Server, the latest products available from Microsoft, and complies with the latest performance monitoring specifications from MSDN. Future versions of performance data providers that implement data sample formats that are unknown at the time of this interface version release are the most probable cause for the message. |