[ISS Support Case] Historian stuck in store and forward after moving the advanced historian

Last updated: October 17th, 2025

Description

They moved their advanced historian outside the network during production and now their tier 1 historians are stuck in store and forward. They are concerned that they will have orphaned data if they stop and start the historian after updating. tested connection over the replication port through powershell, and it shows a good connection

Author: Kevin Modlin
Published: October 17th, 2025

Details:

Product: Historian

Version: 2023 R2

Solution: [Solution is visible below when you're logged in and have a current subscription]

Date Created:	07/30/2025
Case:	98676

Give feedback about this article

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.

[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.

[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.

[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.