Historian Creating History Blocks in the future

I have an issue where my Historian has created 3 History blocks 4 months in the future.

It is storing a reasonable amount of valid process data there.

All platforms seem to have the correct time on them.

The Historian looks like it is struggling to manage this data and is responding poorly to data queries.

What would be the reason it stores data so far into the future.

AFAIK the time stamp of a Historized tag is determined at source on the application server where the data originates.

The Historian merges the data from all platforms and then stores the data into the appropriate block for the day.

Does anyone have any idea why this could be happening?

Thanks

Richard

Parents
  • Hi Richard,

    Did you manage to find a solution? We're experiencing the same issue — and interestingly, it's also exactly 4 months. We're on Platform ver. 2017.

    Deleting the datablocks while Historian was turned off didn’t solve the problem for us. Tracing on the Application Object Server side shows that the data being sent is correct, but tracking on the Historian side indicates that the "Origin time" is wrong.

    We've contacted support, but so far it hasn’t been very helpful, so we’re reaching out to the community in hopes of finding someone who’s resolved this.

    Thanks in advance!

Reply
  • Hi Richard,

    Did you manage to find a solution? We're experiencing the same issue — and interestingly, it's also exactly 4 months. We're on Platform ver. 2017.

    Deleting the datablocks while Historian was turned off didn’t solve the problem for us. Tracing on the Application Object Server side shows that the data being sent is correct, but tracking on the Historian side indicates that the "Origin time" is wrong.

    We've contacted support, but so far it hasn’t been very helpful, so we’re reaching out to the community in hopes of finding someone who’s resolved this.

    Thanks in advance!

Children
  • Hi Lukasz

    This site is on SP2023R2SP1 so a fairly late version.

    Support has been initiated by the customer, but the initial troubleshooting has been woeful so I'm hoping it moves to the Historian team and they identify where in the chain of the data flow from device to OPC server to Application Engine and then to Historian it is going wrong.

    One future History block that I was shown contains actual process data, another is data from a platform which is some of the system tags (%CPU usage RAM etc). This data is not from a PLC. That platform just hosts a View App.

    All very strange. The site does have a very unusual architecture so I am keen to see what Aveva support eventually find.

    Will let you know.