[ISS Support Case] 2020 Historian data storage issue
Last updated: October 17th, 2025Description
The 2020 R2 Historian is storing a null when an DA server goes offline and then when it comes back online, if the tag does not change from the value prior to the null, it does not insert the current value and the null stays until the value changes. For a setpoint this caused a 5 day gap in the value on the Active Factory trend due to the null being stored. See notes below: Please respond by email., i work part time, remotely from pacific time zone. 2020 R2 SP1 Historian Tagname DateTime Value vValue StartDateTime 1601G-TE-105.2_SP 3/19/2022 8:15:19 AM 209.6 209.59999999999999 3/19/2022 8:15:19 AM 1601G-TE-105.2_SP 3/19/2022 12:40:44 PM (null) (null) 3/19/2022 12:40:44 PM 1601G-TE-105.2_SP 3/23/2022 8:51:38 AM 209.5 209.5 3/23/2022 8:51:38 AM 1601G-TE-105.2_SP 3/23/2022 8:51:43 AM 209.6 209.59999999999999 3/23/2022 8:51:43 AM 2014 R2 SP1 Historian Tagname DateTime Value vValue StartDateTime 1601G-TE-105.2_SP 3/19/2022 8:15:19 AM 209.6 209.59999999999999 3/19/2022 8:15:19 AM 1601G-TE-105.2_SP 3/23/2022 8:51:38 AM 209.5 209.5 3/23/2022 8:51:38 AM 1601G-TE-105.2_SP 3/23/2022 8:51:43 AM 209.6 209.59999999999999 3/23/2022 8:51:43 AM The above are delta retrievals via 2014 Active Factory Web Query. Both Historians are configured for Delta storage with a time deadband of 1000 ms and both historians point to the same remote DA server (DASMBTCP). The tag is a setpoint which rarely changes. There was some issue with the remote DA server machine, and it wasnt until the setpoint was manually adjusted did the 2020 Historian record the new value to replace the stored null. Is there any way to ignore nulls on an Active Factory trend retrieval? Why does 2020 R2 SP1 Historian insert the null compared to the 2014 Historian?
- Author: Kevin Modlin
- Published: October 17th, 2025
Details:
| Product: Historian |
| Version: 2020 R2 |
| Solution: [Solution is visible below when you're logged in and have a current subscription] |
| Date Created: | 04/12/2022 |
| Case: | 81299 |
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