UniInt failover-specific messages

This section contains informational messages and their meanings, and error messages and their causes and resolutions.

Informational messages:

16-May-06 10:38:00
ifc 1> UniInt failover: Interface in the "Backup" state.

Meaning: At system startup, the interface assumes the backup role and 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 Data Archive while in backup mode. The amount of data queued while in this state is determined by the failover update interval. Typically no more than two update intervals of data reside in the queue, though state negotiations can cause the queue to hold up to five failover update intervals worth of data.

16-May-06 10:38:05
ifc 1> UniInt failover: Interface in the "Primary" state and actively sending data to PI.

Meaning: The interface is collecting data and sending it to Data Archive.

16-May-06 16:37:21
ifc 1> UniInt failover: Interface in the "Primary" state, Backup interface available.

Meaning: The interface is collecting data and sending it to Data Archive. The other copy of the interface is ready to take over the role of primary if failover occurs.

16-May-06 16:37:21
ifc 1> UniInt failover: Interface in the "Primary" state, Backup interface not available.

Meaning: The interface is collecting data and sending it to Data Archive. However, the other copy of the interface is not ready to take over the role of primary if failover is triggered.

Error messages:

16-May-06 17:29:06
ifc 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 point is not configured properly.

Resolution: Check validity of point attributes. Make sure the location1 attribute is valid for the interface. All failover points must have the same settings for the pointsource and location1 attributes. Modify point attributes as necessary and restart the interface.

16-May-06 17:38:06
ifc 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 point is not configured properly.

Resolution: Check validity of point attributes. Make sure the location1 attribute is valid for the interface. All failover points must have the same settings for the pointsource and location1 attributes. Modify point attributes as necessary and restart the interface.

17-May-06 09:06:03
ifc> 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 the parameter to a positive integer and restart the interface.

17-May-06 09:06:03
ifc 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 the parameter to a positive integer and restart the interface.

17-May-06 09:06:03
ifc 1> UniInt failover: Interface in an "Error" state. Could not read failover control points.

Cause: The failover control points on the data source are returning an erroneous value. The error can be caused by creating a non-initialized control point on the data source. (Phase 1 failover only.)

Resolution: Check validity of the value of the control points on the data source.

16-May-06 17:29:06
ifc 1> Loading Failover Synchronization tag failed
Error Number = 0: Description = [FailOver] or HeartBeat:n] was found in the exdesc for Tag Active_IN but the tag was not loaded by the interface.
Failover will not be initialized unless another Active ID tag is successfully loaded by the interface.

Cause: The active ID or heartbeat point is not configured properly. (Phase 1 failover only.)

Resolution: Check validity of point attributes. For example, make sure location1 attribute is valid for the interface. All failover points must have the same pointsource and location1 attributes. Modify point attributes as necessary and restart the interface.

17-May-06 09:05:39
ifc 1> Error reading Active ID point from data source
Active_IN (Point 29600) status = -255

Cause: The active ID point value on the data source produced an error when read by the interface. The value read from the data source must be valid. As a result of receiving this error, the interface enters the Backup in Error state.

Resolution: Check validity of the value of the active ID point on the data source. For example, if the value for the active ID point shows up as *** on the Cimplicity Point Control Panel, modify the value of the point to a valid value.

17-May-06 09:06:03
ifc 1> Error reading the value for the other copy’s Heartbeat point from data source
HB2_IN (Point 29604) status = -255

Cause: The heartbeat point value on the data source produced an error when read by the interface. The value read from the data source must be valid. Upon receiving this error, the interface enters the Backup in Error state.

Resolution: Check validity of the value of the Heartbeat point on the data source. For example, if the value for the heartbeat point shows up as *** on the Cimplicity Point Control Panel, modify the value of the point to a valid value.

27-Jun-08 17:27:17
PI Eight Track 1 1> Error 5: Unable to create file ‘\\georgiaking\GeorgiaKingStorage\UniIntFailover\\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 is logged 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 that the account that the interface is running under has both read and write permissions for the folder. Change the folder permissions to allow the account in the Log on as property of the Windows service to create files in the folder.

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: The interface is unable to open the failover synchronization file (phase 2 failover). The interface failover operates correctly as long as communication to Data Archive is not interrupted. If communication to Data Archive is interrupted while one or both interfaces cannot access the synchronization file, the interfaces remain in the state they were in at the time of the second failure, so the primary interface remains primary and the backup interface remains backup.

Resolution: Change the folder or file permissions to allow the account in the Log on as property of the Windows service to read and write the failover synchronization file.