Historian trend Client graph do not update with Historize value

Hi Hemant, What happens if you view a Historian System tag ,such as SysTimeSec or SysPulse, will that display data on the faulty client?

I check SysPulse it shows OFF value....

If i go in live mode to view tag value, i can see value changing at Cursor value but if stop live mode and go in Histoianmode graph again becomes straight line..

A thing to check, is the client DateTime aligned with the Historian server?

I think Richard has the right idea: The date/time for the new client isn't correct. However, my guess is that the problem isn't with the system time, but with the date order. A quick check of this is to select a historical time period that will be in the past even in cases where the date order is different (e.g. 2-Feb-2024).

If Trend works as expected in the case, the real fix probably has to do with the default language (and associated date order) assigned for the SQL Login used by the client. You can change this several ways, including through the SQL Server Management Console. You may also want to change the default language for new logins to reduce the risk of repeating the problem.

By default the SQL Server "english" language uses U.S. date order of "M-D-Y" and the "uk_english"  language uses "D-M-Y" order used in most of the rest of the world.

I checked data/time as well which were already matching with the server...

Then i run SQL query for historial values of a TAG which gives me Identical samples from server which we cross verify with the server.

Then on Trend when we save Data for same tag we can see only two values..

From above results, i check the options of a tag where we observed QUERY ROW LIMIT was changed to 2 from default value of 0. On making this value back to default 0, we are getting the graph with actual values of varring.

Thank you all for your help..

regards

Hemant