Learn about error messages
- Last UpdatedJan 22, 2025
- 5 minute read
These messages are returned when the function cannot be complete as requested, and some corrective action might be required.
|
Message |
parse arguments: missing required argument - id |
|
Description |
Error message is logged on interface startup if required. /ID command-line parameter is not specified. After the message, the interface stops. |
|
Message |
<PI point name> (point ID) add tag error: invalid scan class (must be in the range of 1 to X inclusive) |
|
Description |
Error message is logged when the interface loads a PI point with a Location4 attribute that is not in the range of specified /F parameters. After the message, the PI point is rejected by the interface. At least one /F parameter must be specified for the interface. This first parameter correlates with Location4 set to 1 for the PI point. |
|
Message |
<PI point name> (point ID) add tag error: invalid counter path (cannot be empty) |
|
Description |
Error message is logged when the interface loads a PI point with an empty extended descriptor attribute. The attribute must contain a string value representing either a latency point or a performance counter path. |
|
Message |
<PI point name> (point ID) add tag error: invalid point type |
|
Description |
Error message is logged when the interface loads a PI point with a data type that is neither numeric nor digital. The interface supports PI points of the following types: Float16, Float32, Float64, Int16, Int32, and Digital. |
|
Message |
<PI point name> (point ID) add tag error (validation): duplicate tag (latency tag for the scan class for the computer is already loaded - pointid: (point ID) |
|
Description |
Error message is logged when the interface loads a duplicate latency PI point for a given device and scan class. |
|
Message |
<PI point name> (point ID) add tag error (validation): duplicate tag (duplicate tag (tag with the same counter path for the scan class for the computer is already loaded - pointid: (point ID) |
|
Description |
Error message is logged when the interface loads a duplicate data or status PI point for a given device and scan class with the same performance counter path. Note that the interface is capable of loading the same performance counters in different scan classes. |
|
Message |
<PI point name> (point ID) add tag error: invalid tag data type (latency tag cannot be digital) |
|
Description |
Error message is logged when the interface loads a latency PI point with the extended descriptor attribute set to [LATENCY:COMPUTER] and data type digital. Latency points can have only numeric data types. The recommended type is Float32. |
|
Message |
<PI point name> (point ID) add tag error: invalid counter path (invalid computer name) |
|
Description |
Error message is logged when the interface loads a PI point with the extended descriptor attribute containing invalid computer name part. Device name must be at least one character long and satisfy less restrictive NetBIOS naming rules, where the following characters are invalid: ^ \ / : * ? > < | |
|
Message |
<PI point name> (point ID) add tag error: invalid counter path (missing closing ']' character) |
|
Description |
Error message is logged when the interface loads a latency PI point with a extended descriptor attribute missing the closing bracket ( ] ) character. |
|
Message |
<PI point name> (point ID) add tag error: invalid counter path (must start with a '\' character) |
|
Description |
Error message is logged when the interface loads a data or status PI point with an invalid performance counter path in its extended descriptor attribute: the string must start with either one or two backslash ( \ ) characters. One if computer part is not specified (which produces a warning), two - before computer name part. |
|
Message |
<PI point name> (point ID) add tag error: invalid counter path (cannot end with a '\' character) |
|
Description |
Error message is logged when the interface loads a data or status PI point with an invalid performance counter path in its extended descriptor attribute. The string cannot end with backslash ( \ ) character. |
|
Message |
<PI point name> (point ID) add tag error: invalid counter path (length is too small) |
|
Description |
Error message is logged when the interface loads a data or status PI point with an invalid performance counter path in its extended descriptor attribute. Theoretically, the minimum counter path should be no less than 4 characters: (1) '\', (2) 'object', (3) '\', (4) 'counter' (\object\counter). |
|
Message |
<PI point name> (point ID) add tag error: invalid counter path (missing '\' character between computer name and object name) |
|
Description |
Error message is logged when the interface loads a data or status PI point with an invalid performance counter path in its extended descriptor attribute. According to the Microsoft specification, a counter path must have 3 or 4 back-slash characters, which serve as separators between the computer name, the object and the counter parts. |
|
Message |
<PI point name> (point ID) add tag error: invalid counter path (missing '\' character between object name and counter name) |
|
Description |
Error message is logged when the interface loads a data or status PI point with an invalid performance counter path in its extended descriptor attribute. According to the Microsoft specification, a counter path must have 3 or 4 back-slash characters, which serve as separators between the computer name, the object and the counter parts. |
|
Message |
<PI point name> (point ID) add tag error: invalid counter path ('*' character is reserved for wildcard use and not supported by the interface) |
|
Description |
Error message is logged when the interface loads a data or status PI point with invalid performance counter path in its extended descriptor attribute. According to the Microsoft specification, the asterisk ( * ) character can be used in counter paths as a wildcard character, which allows you to specify multiple counters by one path. The interface does not support this. It requires exactly one performance counter path for one PI point. |
|
Message |
<PI point name> (point ID) add tag error: invalid counter path (invalid counter path object name cannot be empty) |
|
Description |
Error message is logged when the interface loads a data or status PI point with an invalid performance counter path in its extended descriptor attribute. According to the Microsoft specification, an object part cannot be empty. For example, this is invalid: \\computer\\counter |
|
Message |
<PI point name> (point ID) add tag error: invalid counter path (invalid counter path counter name cannot be empty) |
|
Description |
Error message is logged when the interface loads a data or status PI point with an invalid performance counter path in its extended descriptor attribute. According to the Microsoft specification, a counter part cannot be empty. For example, this is invalid: \\computer\object\ |
|
Message |
<PI point name> (point ID) add tag error: invalid counter path (no matching '(' character found in object name) |
|
Description |
Error message is logged when the interface loads a data or status PI point with an invalid performance counter path in its extended descriptor attribute. According to the Microsoft specification, an object part may contain '(instance name)'. The error indicates that either an opening parenthesis '(' or a closing parenthesis ')' character is missing. |
|
Message |
<PI point name> (point ID) add tag error: invalid counter path ('\' character is reserved and must be used only for object\counter separation) |
|
Description |
Error message is logged when the interface loads a data or status PI point with an invalid performance counter path in its extended descriptor attribute. According to the Microsoft specification, an object part may contain "(instance name)". The instance name sub-part cannot contain backslash ( \ ) characters. |