GridProtectionAlliance/openHistorian

OpenHistorian Action Adapter Unknown Stop

wwang72 opened this issue · 4 comments

wwang72 commented

Hello,

Recently we have seen an unknown stop among our action adapters. we had 4 action adpater instances that using a same .dll file. In the mid April, one of them stopped working for about 8 hours until we re-initialized it, but at the same time the other three adpter instances worked well. Not sure if you know this issue or you have fixed it in the later versions.

Regards,
Ferriad
FNET@UTK

wwang72 commented

Hi,

Although this issue persists, I would like to by-pass it by reinitialize the trigger using program. Is there any API I can use to initialize a trigger?
Thanks,
Regards,
Ferriad

ritchiecarroll commented

You can issue an "initialize <adaptername | ID>" to the service console. Are you wanting to automate this?

StephenCWills commented

From the command line, something like echo initialize MY_ADAPTER | "C:\Program Files\openHistorian\openHistorianConsole.exe" should work.

  • 👍2
wwang72 commented

Thank you both Ritchie and Stephen, this way works at our side