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

FactoryTalk Historian To Historian Interface User Guide 141
Errors (Phase 2)
Unable to open synchronization file
Message
27-Jun-08 17:27:17
Historian Eight Track 1 1> Error 5: Unable to create file
„\\georgiaking\GeorgiaKingStorage\UnIntFailover\\PIEightT
rack_eight_1.dat‟
Verify that interface has read/write/create access on
file server machine.
Intializing 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
Historian Eight Track 1 2> WARNING> Failover Warning:
Error = 64
Unable to open Failover Control File
„\\georgiaking\GeorgiaKingStorage\Eight\PIEightTrack_eigh
t_1.dat‟
The interface will not be able to change state if
Historian 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 Historian Server is not interrupted. If communication to Historian
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.