Citect Interface


System Errors and PI Errors



Download 0.67 Mb.
Page23/26
Date31.07.2017
Size0.67 Mb.
#24967
1   ...   18   19   20   21   22   23   24   25   26

System Errors and PI Errors


System errors are associated with positive error numbers. Errors related to PI are associated with negative error numbers.

Error Descriptions on Windows


On Windows, descriptions of system and PI errors can be obtained with the pidiag utility:

Windows: \PI\adm\pidiag /e error_number


UniInt Failover Specific Error Messages

Informational


Message

16-May-06 10:38:00

Citect 1> UniInt failover: Interface in the “Backup” state.

Meaning

Upon system startup, the initial transition is made to this state. While in this state, the interface monitors the status of the other interface participating in failover. When configured for Hot failover, data received from the data source is queued and not sent to the PI Server while in this state. The amount of data queued while in this state is determined by the failover update interval. In any case, there will be typically no more than two update intervals of data in the queue at any given time. Some transition chains may cause the queue to hold up to five failover update intervals worth of data.




Message

16-May-06 10:38:05

Citect 1> UniInt failover: Interface in the “Primary” state and actively sending data to PI. Backup interface not available.

Meaning

While in this state, the interface is in its primary role and sends data to the PI Server as it is received. This message also states that there is not a backup interface participating in failover.




Message

16-May-06 16:37:21

Citect 1> UniInt failover: Interface in the “Primary” state and actively sending data to PI. Backup interface available.

Meaning

While in this state, the interface sends data to the PI Server as it is received. This message also states that the other copy of the interface appears to be ready to take over the role of primary.

Errors (Phase 1 & 2)


Message

16-May-06 17:29:06

Citect 1> One of the required Failover Synchronization points was not loaded.

Error = 0: The Active ID synchronization point was not loaded.

The input PI tag was not loaded

Cause

The Active ID tag is not configured properly.

Resolution

Check validity of point attributes. For example, make sure Location1 attribute is valid for the interface. All failover tags must have the same PointSource and Location1 attributes. Modify point attributes as necessary and restart the interface.




Message

16-May-06 17:38:06

Citect 1> One of the required Failover Synchronization points was not loaded.

Error = 0: The Heartbeat point for this copy of the interface was not loaded.

The input PI tag was not loaded

Cause

The Heartbeat tag is not configured properly.

Resolution

Check validity of point attributes. For example, make sure Location1 attribute is valid for the interface. All failover tags must have the same PointSource and Location1 attributes. Modify point attributes as necessary and restart the interface.




Message

17-May-06 09:06:03

Citect > The Uniint FailOver ID (/UFO_ID) must be a positive integer.

Cause

The UFO_ID parameter has not been assigned a positive integer value.

Resolution

Change and verify the parameter to a positive integer and restart the interface.




Message

17-May-06 09:06:03

Citect 1> The Failover ID parameter (/UFO_ID) was found but the ID for the redundant copy was not found

Cause

The /UFO_OtherID parameter is not defined or has not been assigned a positive integer value.

Resolution

Change and verify the /UFO_OtherID parameter to a positive integer and restart the interface.

Errors (Phase 2)

Unable to open synchronization file

Message

27-Jun-08 17:27:17

PI Eight Track 1 1> Error 5: Unable to create file ‘\\georgiaking\GeorgiaKingStorage\UnIntFailover\\PIEightTrack_eight_1.dat’

Verify that interface has read/write/create access on file server machine.

Initializing UniInt library failed

Stopping Interface


Cause

This message will be seen when the interface is unable to create a new failover synchronization file at startup. The creation of the file only takes place the first time either copy of the interface is started and the file does not exist. The error number most commonly seen is error number 5. Error number 5 is an “access denied” error and is likely the result of a permissions problem.

Resolution

Ensure the account the interface is running under has read and write permissions for the folder. The “log on as” property of the Windows service may need to be set to an account that has permissions for the folder.

Error Opening Synchronization File

Message

Sun Jun 29 17:18:51 2008

PI Eight Track 1 2> WARNING> Failover Warning: Error = 64

Unable to open Failover Control File ‘\\georgiaking\GeorgiaKingStorage\Eight\PIEightTrack_eight_1.dat’

The interface will not be able to change state if PI is not available

Cause

This message will be seen when the interface is unable to open the failover synchronization file. The interface failover will continue to operate correctly as long as communication to the PI Server is not interrupted. If communication to PI is interrupted while one or both interfaces cannot access the synchronization file, the interfaces will remain in the state they were in at the time of the second failure, so the primary interface will remain primary and the backup interface will remain backup.

Resolution

Ensure the account the interface is running under has read and write permissions for the folder and file. The “log on as” property of the Windows service may need to be set to an account that has permissions for the folder and file.




Download 0.67 Mb.

Share with your friends:
1   ...   18   19   20   21   22   23   24   25   26



The database is protected by copyright ©ininet.org 2024
send message
    Main page
latest version
prior written permission
initial state
same computer
primary interface
osisoft logo