[ISS Support Case] Replication to PI Server
Last updated: October 17th, 2025Description
Customer is using the PI replication feature in Historian 2023. He has other plants where this is setup and working. At this particular plant the Historian keeps going into Store & Forward. As you can see at the end of the attached log file, the system gets disconnected from the PI system and enters S&F (7:19:49 AM). Also attached is a screen shot showing the system in S&F. 11/11/2022: -Teams Meeting, Checked TCP Port, Checked File path, Changed File path, The D: Drive is very full, Customer is going to clean up the D: Drive. -Some Analog tags are set as "Delta" tags, going to change them to a non priority type tag so that the data is not pulling in, in such a vast data pool.
- Author: Kevin Modlin
- Published: October 17th, 2025
Details:
Product: Historian |
Version: 2023 |
Solution: [Solution is visible below when you're logged in and have a current subscription] |
Date Created: | 11/11/2022 |
Case: | 83048 |
Recommended articles
[ISS Support Case] Historian loses connection after shutting down
If the historian is shut down and disabled then re-enabled it doesn't connect to tags that haven't changed. Reboot re-establishes connection.
Read More[ISS Support Case] Trying to access old history blocks
They have a very old system they're trying to open a trend or see the data, but they don't see a trend program and can't figure out how to open the file. They believe they have the data, but it's running in demo mode and won't show data. This is an offline PC and they want to avoid putting it online, so we can't do a screen share.
Read More[ISS Support Case] Trend SQL Login Failure
Client reached out due to receiving time out error message when logging into SQL to View Trends remotely on Development node.
Read More[ISS Support Case] Wanting to pull 9 months of historized data
-Customer is wanting Historized data from the last 9 months in a .CSV file. Or in SQL. and wants to know the best practices.
Read More