[ISS Support Case] Trends Flat Line from Midnight to Around 6 AM

Last updated: February 4th, 2026

Description

Historian 2023 R2 Customer has data that they are looking at for the day. Sometimes, the trend will show a flat line from midnight until a later point (6 or 6:30 AM). Eventually, that data will come back. If they look at it the next day, the data will be there.

Author: Kevin Modlin
Published: February 4th, 2026

Details:

Product: Historian

Version: 2023 R2

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

Date Created:	06/12/2025
Case:	98063

Give feedback about this article

Recommended articles

[ISS Support Case] Historian Client Unable To Add Server In Server List Configuration

Under Server List Configuration Failed to connect: Unable to reach INSQL/Historian server, make sure that INSQL/Historian server is running

[ISS Support Case] Historian Migration How To 11.0 - 23.0

The old Historian is still in production. Basically, the client is running both App Server 2012 R2 and System Platform 2023 at the same time. Everything is replicated, both the hardware and software. The last step is to get the new Historian to read all the data from the old Historian so that the old Historian (and all the App Server 2012 R2 hardware and software) can be decommissioned. The new Historian does have a few more tags, than the old one, but we dont have to worry about them because I can run a query on those few tags before migrating the old historian data to the new historian. I tried shutting down the new Historian, deleting all the history blocks, copying the history blocks from the old historian, then restarting the Historian. This almost works, however, the data is spotty nulls occur in places in time they shouldnt, for example. Since just copying the history blocks from the old to new didn't work, I attempted the method shown here https://knowledge.insourcess.com/Operational_Efficiency/Historian/Implement_and_Support/Support_Tickets/Installation_and_Configuration/Installation_and_Configuration14/68223_-_Unable_to_see_data_in_imported_History_Blocks I made a backup of the Runtime and Holding database one the old Historian, copied them to the new Historian, and then attempted to restore them to the new Historian. I detached the Runtime database on the new Historian and selected Restore data base, then pointed to the Runtime data from old Historian. However, I received an error message that the Runtime database cant be restored because it is being used by the Runtime 11 database. See attached screenshot. What should my next steps be?

[ISS Support Case] Replication Failure

Client reached out as after configuring simple replication from the Tier 1 Historian to the PI Server the replication was failing.

[ISS Support Case] Updating bad data that's been historized

Got a historian tag with bad data sent it. The issue is suppressing averages. Would like to updated the data to a different value for an 8 hour period. Version (20.1.100)