Rockwell Automation 1756-HIST2G FactoryTalk Historian ME 2.2 - Manual (Page 305)

G • T ROUBLESHOOTING
295
If Data Transfer and
Data Collection are
running on one or
more modules, and
Data Transfer is
stopped and then
started on one module
after some time has
passed, the module
may experience data
interruption:
„
Restarting Data Transfer on the module may cause data
interruption because old timestamps cannot be written to
the current archive.
„
After it is restarted, ensure that Data Transfer remains run-
ning so that transferred events eventually match the archive
event timestamps.
If data in the
FactoryTalk Historian
SE or PI server
contains timestamps
that are not being
updated: Check the status of Data Transfer on the Home page.
„
If Data Transfer status is
“Running”:
„
Go to the Advanced tab
to view the System Log
page. Check the log for
messages about the issue
and export log data.
„
Ensure that the CPU
load is at a normal rate
and not preventing data
from being transferred.
„
Ensure that points are
properly configured with
scan rates that are not too
low.
„
Ensure that Exception
and Compression values
are properly configured
for points.
„
If Data Transfer status is
“Error”:
„
Go to the Web Diagnos-
tics Firmware tab.
Check the Data Trans-
fer page. Process infor-
mation can confirm
whether or not Data
Transfer is in a undesir-
able state. N/A indicates
an error state.
„
Reboot the module.
Data Transfer
Symptom Solution