Learn about error and informational messages for PI EFGen
- Last UpdatedJan 14, 2025
- 4 minute read
- PI System
- PI Event Frames Generator 5.1.7
- Interfaces
Message logs
To view message logged by PI EFGen, open the Windows Event Viewer.
Messages are written to the Windows Event Viewer as follows:
-
When PI EFGen starts, informational messages are logged.
-
As PI EFGen loads PI points, errors are logged if the interface encounters problems with the configuration of the points.
-
All attempts to create elements, attributes and points are logged.
When you enable debugging, the logging level specifies where the events are logged.
Generally, such errors stop PI EFGen from starting up, because the proper startup state of PI EFGen cannot be achieved. Check whether the interface node can connect with the PI Server node.
|
Error Message |
Description |
|---|---|
|
<source> <error description>. |
PI EFGen node is out of memory. Release some memory by closing unused applications. |
|
<source>: error number<error description>. |
COM errors can occur while the interface is retrieving data from the data source or sending data to the PI Server. For details, refer to the . |
|
<source> OR <source> |
PI EFGen node is out of memory. Release some memory by closing unused applications and restart PI EFGen. |
|
<argumentfile> |
PI EFGen failed to find the batch file associated with the interface instance. Make sure that the batch file name is consistent with the interface instance ID. |
|
|
Check the batch file for missing quotes. |
|
<filename> |
Verify that the specified initialization file exists in ProgramData/OSISoft/Interfaces/EFGEN. |
|
<filename> |
Check the access properties of the initialization file. |
|
<filename> |
Verify that the startup file named <filename> exists in the PIEFGen directory. |
|
<startup file><filename> |
Check the access properties of the specified startup file. |
|
<startup file><filename><error description> |
Check the access properties of the specified startup file. Refer to error number and description for the actual error description. |
|
<filename> |
Verify that the specified file contains a valid event frames hierarchy. |
|
<error description> OR <error description> |
Missing parameters in command line or initialization file required for interface startup. |
|
language |
The value provided for /ns switch in command line parameters is invalid, please check your input. |
|
|
PI EFGen failed to identify the AF SDK version number. Please consult with AVEVA Technical Support to resolve this error. |
|
<minimum SDK version> or higher |
The AF SDK version installed on PI EFGen node is lower than the minimum required by PI EFGen version of the AF SDK. Install required version of AF SDK. |
|
|
PI EFGen failed to broadcast its Global Unique ID to the PI server. Contact AVEVA Technical Support. |
|
<collective name\PI server name> |
The current version of PI EFGen is designed to run only against primary server if used in the Collective configuration. Change the /host switch value and restart PI EFGen. |
|
<object description> |
PI EFGen node is out of memory. Release some memory by closing unused applications and restart PI EFGen. |
|
error number<error description> |
Microsoft Windows error. |
|
<filename> |
Check the access properties of the command file. |
|
<filename> |
Check the access properties of the command file. |
|
thread ID |
PI EFGen node might be out of memory. Release some memory by closing unused applications and restart PI EFGen. |
|
<error description> OR <error description> |
Incorrect data provided while defining Attribute[#] template value structure. Refer to error description and check your input in initialization file. |
Runtime errors
Generally, batch interface errors are triggered by some action that PI EFGen takes while interacting with the PI Server. Most errors contain text returned from the PI Server or AF SDK. PI-server-specific portions generally contain a negative five-digit number (for example, –10401 or –15001), often followed by a description. You can look up these error numbers using the following commands:
pidiag –e <error number>
pilogsrv –e <error number>
AF SDK numbers are generally eight-digit hexadecimal numbers (for example, 0x000403a0). Descriptions are generally appended to the error message, and can be looked up using the AboutPISDK.exe application, which is installed when the AF SDK is installed.
Following are commonly-encountered runtime errors.
|
Error Message |
Description |
|---|---|
|
<source><error description> |
PI EFGen node is out of memory. Release some memory by closing unused applications. |
|
<source>error number<error description> |
COM errors. These errors can occur while retrieving data from the data source and during processing of data to the PI Server. Refer to PI SDK reference manual for PI related COM errors to resolve such errors. |
|
<source><error description> <source> OR <source> |
Memory allocation errors that typically mean that PI EFGen node is out of memory. Release some memory by closing unused applications and restart PI EFGen. |
For all other errors, refer to the error descriptions and contact Technical Support.