• State Not Answered
  • Replies 1 reply
  • Subscribers 12 subscribers
  • Views 458 views
  • Users 0 members are here
Options
Related

Historian not logging when re-enabling after shutdown, through SMC

Jakob Agustsson

Hi, I sometimes need to rename historian tags by using the rename utility from Aveva, this requires temporarely disabling the historian. This is done through the Historian Management in the  SMC. i.e. Right click Status -> shutdown and disable historian.  After enabling it again it shows a very low datarate in the status window and only logs to the buffer path.

I have solved this by restarting the windows server completely and the everything goes back to normal. The server is also running app engines and other stuff so I try to avoid that of course. 

I want to get to the bottom of this and somehow get this working without restarting the windows server completely.  Is there something else i could do instead of restarting the entire machine?

System Platform 2021

Historian 2021

rgds

Jakob

Parents
  • 0

    Hi Jakob, 

    When this happens, is your engine stuck in store forward mode?

    Check the Historian status in Object viewer.

    "EngineName".Engine.Historian.InStoreForward

    If this is the case then we have seen this in several installations, but only on version 2020 and there should be a patch/hotfix for this.

    Engine display Historian.ConnectionState = true even though its in store forward.


    And if this is the case it should be ok to stop the engine and start it again using SMC/Platform Manager to get it running again, without rebooting the server, in some scenarios it has been enough to take the engine off scan and then on scan again.

    Also verify your version in Apps and Features in windows, correct version and build should be listed here.

    There could of course be other reasons for this issue, but this was a a thing I have seen in several installations and is worth to check out.

Reply
  • 0

    Hi Jakob, 

    When this happens, is your engine stuck in store forward mode?

    Check the Historian status in Object viewer.

    "EngineName".Engine.Historian.InStoreForward

    If this is the case then we have seen this in several installations, but only on version 2020 and there should be a patch/hotfix for this.

    Engine display Historian.ConnectionState = true even though its in store forward.


    And if this is the case it should be ok to stop the engine and start it again using SMC/Platform Manager to get it running again, without rebooting the server, in some scenarios it has been enough to take the engine off scan and then on scan again.

    Also verify your version in Apps and Features in windows, correct version and build should be listed here.

    There could of course be other reasons for this issue, but this was a a thing I have seen in several installations and is worth to check out.

Children
No Data
© 2024 AVEVA Group Limited or its subsidiaries. All Rights Reserved.