Learn about delayed validation errors
- Last UpdatedJan 22, 2025
- 3 minute read
The following error messages are logged when the interface fails to validate already-loaded PI points. This validation is required for the interface to service PI points from different devices without delay. If validation fails, the PI point remains loaded, but the interface writes its status only once. To resolve the issue, correct the point configuration. When the interface detects that one of its points has been modified, it reloads the point.
|
Message |
<PI point name> (point ID) add tag error (validation): invalid counter path (counter object not found) |
|
Description |
Error message is logged when the interface fails to find the specified counter object on the monitored device. Typically, this indicates either a typo in the object name of the performance counter path, or a non-existent counter object. For example, if a PI point is configured to collect performance data from another PI interface which is not currently installed as a service on the monitored device, then by default the /ReloadPerfData startup parameter is not specified and the PI Performance Monitor interface is not able to dynamically tell whether the monitored interface is installed on the device or not. For data points, if no /NoErrorStatus startup parameter is specified, the status is set to CONFIGURE. For status points, the status is set to NO OBJECT from the PI Performance Monitor digital state set. |
|
Message |
<PI point name> (point ID) add tag error (validation): invalid counter path (counter object not returned) |
|
Description |
Error message is logged when the performance data provider does not return the requested object. Note that the object exists in the performance counter configuration on the monitored machine, but the provider does not return it. For data points, if no /NoErrorStatus startup parameter is specified, the status is set to CONFIGURE. For status points, the status is set to NO OBJECT from the PI Performance Monitor digital state set. |
|
Message |
<PI point name> (point ID) add tag error (validation): invalid counter path (counter for the object is not found) |
|
Description |
Error message is logged when the interface fails to find the specified counter of the object on the monitored device. Typically, this indicates a typo in the counter name of the performance counter path, for example, \\computer\Processor(_Total)\NOT EXISTING COUNTER. For data points, if no /NoErrorStatus startup parameter is specified, the status is set to CONFIGURE. For status points, the status is set to NO COUNTER from the PI Performance Monitor digital state set. |
|
Message |
<PI point name> (point ID) add tag error (validation): invalid counter path (object instance is not specified) |
|
Description |
Some performance counters require the instance of the monitored object to be specified. For example, for the Processor object, the system needs to know whether to return data for all processors or a specific processor. For data points, if the /NoErrorStatus startup parameter is omitted, the status is set to CONFIGURE. For status points, the status is set to NO INSTANCE from the PI Performance Monitor digital state set. |
|
Message |
<PI point name> (point ID) add tag error (validation): invalid counter path (object instance is not found) |
|
Description |
Error message is logged when the interface fails to find any instance of the counter object running on the device. For example, if the interface is configured to monitor another PI interface, and the PI point for monitoring this interface is loaded before the interface startup, then by default /ReloadPerfData startup parameter is not specified and the PI Performance Monitor interface is not able to dynamically tell whether the monitored interface started or not. For data points, if no /NoErrorStatus startup parameter is specified, the status is set to CONFIGURE. For status points, the status is set to NO INSTANCE from the PI Performance Monitor digital state set. |
|
Message |
<PI point name> (point ID) add tag error (validation): invalid counter path (base counter used) |
|
Description |
Error message is logged when the interface encounters a "base counter" being specified in a performance counter path. According to Microsoft specifications, base counters cannot be used directly to report any performance data. For data points, if no /NoErrorStatus startup parameter is specified, the status is set to CONFIGURE. For status points, the status is set to INVALID COUNTER from the PI Performance Monitor digital state set. |
|
Message |
<PI point name> (point ID) add tag error (validation): invalid counter path (counter not supported) |
|
Description |
Error message is logged when the interface encounters an unsupported counter being specified in the performance counter path. According to Microsoft specifications, the following counters are not currently supported: test counter, no data counter and histogram counter. For data points, if no /NoErrorStatus startup parameter is specified, the status is set to CONFIGURE. For status points, the status is set to INVALID COUNTER from the PI Performance Monitor digital state set. |