[ISS Support Case] Historian 2020R2 won't upgrade old Runtime backup
Last updated: March 7th, 2025Description
We have a backup of Runtime database from v2014R2 and the Configurator on new v2020R2 SP1 P01 install will not update the database. Logs show that it is skipping the historian configuration. Tried to also step upgrade 2014R2 > 2017U3 > 2020R2. The first step works but the v2020R2 upgrade fails. Is there a hotfix out there for this? The system is close to being deployed and cutover so we need assistance as soon as possible.
- Author: Kevin Modlin
- Published: March 7th, 2025
Details:
| Product: Historian |
| Version: 2020 R2 |
| Solution: [Solution is visible below when you're logged in and have a current subscription] |
| Date Created: | 07/26/2023 |
| Case: | 84927 |
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.
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