UniInt failover-specific messages

16-May-06 10:38:00 OPCInt 1> UniInt failover: Interface in the “Backup” state.

Upon interface startup, the initial transition is made to the backup state. 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 Data Archive 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 can cause the queue to hold up to five failover update intervals worth of data.

16-May-06 10:38:05 OPCInt 1> UniInt failover: Interface in the “Primary” state and actively sending data to PI. Backup interface not available.

In primary state, the interface sends data to Data Archive as it is received. This message also indicates that there is not a backup interface participating in failover.

16-May-06 16:37:21 OPCInt 1> UniInt failover: Interface in the “Primary” state and actively sending data to PI. Backup interface available.

While in this state, the interface sends data to Data Archive 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.

16-May-06 17:29:06 OPCInt 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.

The Active ID tag is not configured properly.

Check validity of point attributes. Make sure the location1 attribute is set to the id parameter of the interface. All failover tags must have the same pointsource and location1 attributes. Modify point attributes as necessary and restart the interface.

16-May-06 17:38:06 OPCInt 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.

The heartbeat tag is not configured properly.

Check validity of point attributes. Make sure the location1 attribute is set to the id parameter of the interface. All failover tags must have the same pointsource and location1 attributes. Modify point attributes as necessary and restart the interface.

17-May-06 09:06:03 OPCint > The UniInt FailOver ID (/UFO_ID) must be a positive integer.

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

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

17-May-06 09:06:03 OPCInt 1> The Failover ID parameter (/UFO_ID) was found but the ID for the redundant copy was not found

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

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

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

The failover control points on the data source are returning an erroneous value to the interface. This error can be caused by creating a non-initialized control point on the data source. This message will only be received if the interface is configured to be synchronized through the data source (Phase 1).

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

16-May-06 17:29:06 OPCInt 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.

The Active ID or heartbeat tag is not configured properly. This message is received only if the interface is configured to be synchronized through the data source (Phase 1).

Check validity of point attributes. Make sure the location1 attribute is set to the id parameter of the interface. All failover tags must have the same pointsource and location1 attributes. Modify point attributes as necessary and restart the interface.

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

The Active ID point value on the data source caused 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.”

Check validity of the value of the Active ID point on the data source.

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

The heartbeat point value on the data source caused 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.”

Check validity of the value of the heartbeat point on the data source

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

The interface is unable to create a new failover synchronization file at startup. The creation of the file 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 probably the result of a permissions problem.

Ensure the account that the interface is running under has read and write permissions for the directory. Set the access control list on the directory to read/write/create access to the account that runs the interface.

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

The interface is unable to open the failover synchronization file. The interface failover continues to operate correctly if 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: the primary interface remains primary and the backup interface remains backup.

Ensure the account that the interface is running under has read and write permissions for the directory. Set the access control list on the directory to read/write/create access to the account that runs the interface.