Rockwell Automation FactoryTalk Historian SE 3.0 H2H Interface User Guide - Manual (Page 145)

FactoryTalk Historian To Historian Interface User Guide 139
UniInt Failover Specific Error Messages
Informational
Message
16-May-06 10:38:00
PItoPI 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 Historian 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
PItoPI 1> UniInt failover: Interface in the “Primary”
state and actively sending data to Historian. Backup
interface not available.
Meaning While in this state, the interface is in its primary role and sends data to the Historian
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
PItoPI 1> UniInt failover: Interface in the “Primary”
state and actively sending data to Historian. Backup
interface available.
Meaning While in this state, the interface sends data to the Historian 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
PItoPI 1> One of the required Failover Synchronization
points was not loaded.
Error = 0: The Active ID synchronization point was not
loaded.
The input Historian 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.