Data transfer issues

Symptom
Solution
The System Status section on the Home page shows that the data transfer is in the "Stopped" mode.
Go to the
Advanced
 tab to view the
System Log
 page. Check the log for messages about the issue and export log data.
  • Go to the
    Configure Historian
     tab. On the
    Data Transfer
     page, click
    Start
     to restart Data Transfer.
  • If Data Transfer does not start:
    • Ensure that the FactoryTalk Historian SE host name or IP address is correct.
    • Ensure that all security settings, including trust connections (if required), have been properly configured.
  • Click Test Connection to ensure a connection to the FactoryTalk Historian SE or PI server can be established.
The System Status section on the Home page shows that the data transfer is in the "Error" mode.
  • Go to the
    Advanced
     tab to view the
    System Log
     page. Check the log for messages about the issue and export log data.
  • Check the module STS LED light. Flashing red indicates that the data transfer is inactive (and the data collection is active.)
  • Go to the
    Web Diagnostics Firmware
     tab and check the
    Data Transfer
     page. Process information can confirm whether or not the data transfer is in an undesirable state.
  • N/A indicates an error state.
Download log files that will assist in troubleshooting as described in the Provide issue information, Reboot the module, and Work in the safe mode sections.
  • Reboot the module.
  • Contact Technical Support if the issue persists.
If the data collection is running on one or more modules and these modules are transferring data to a FactoryTalk Historian SE or PI server, the FactoryTalk Historian SE or PI server will experience a large load and overflow events if the data transfer is stopped for some time and then restarted.
To minimize the load and number of overflow events on the FactoryTalk Historian SE or PI server, go to the
Configure Historian
 tab. On the
Data Transfer
 page, reduce the Maximum Events per Transfer value. This parameter controls the number of events transferred.
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 the 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 the data transfer remains running so that transferred events eventually match the archive event timestamps.
Data in the FactoryTalk Historian SE or PI server contains timestamps that are not being updated.
Check the status of the data transfer on the
Home
 page.
If the 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 the data transfer status is
Error
:
  • Go to the
    Web Diagnostics Firmware
     tab. Check the
    Data Transfer
     page. Process information can confirm whether or not the data transfer is in an undesirable state. N/A indicates an error state.
  • Reboot the module.
The FactoryTalk Historian SE or PI server rejects points from a new module that has been added to an existing collection of modules transferring data to that server.
  • Ensure that the points are created in the FactoryTalk Historian SE or PI server before the data transfer is started. This will ensure that the point database and the archive can be synchronized.
  • The FactoryTalk Historian SE or PI server rejects the points because the archives have shifted several times and are outside the range of the existing archives.
Fewer events than expected have been transferred to the FactoryTalk Historian SE or PI server.
  • Check the module CPU load. The data transfer checks the module CPU load before transferring data. If the load is high, events are transferred at a slower rate.
  • Try changing the rate at which events are transferred. Go to the
    Configure Historian
     tab. On the
    Data Transfer
     page, increase the Maximum Events per Transfer value to allow events to transfer more quickly.
No events are being transferred to FactoryTalk Historian SE or PI server.
Make sure that enough disk space is being allocated in the FactoryTalk Historian SE or PI server to allow the transfer.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal