Historian stop logging after update are made in windowmaker.

hello Flix,

to test if the paroblem is with the tag, please stop historizing the tag, save and check the SMC acquisition and SMC logs if the warning has stopped as well.

secondly, add another tag and Historize it, remember that you WindowViewer must running to Historize the tag values

The problem is not with only one tag. Its all the tag that stop logging. The data seems to get stuck in the store n forward buffer of the intouch node. 

We go that fix by running the osconfiguratorutility.exe

This happened twice last year and I would like to know the root cause of that. Its my only site with that configuration I I would like to migrate the other like that but right now this is causing more issue than its helping.

Hi Flix,

if the data goes to the store and forward which is probably the local InTouch machine, it tells you that the Historian Server becomes inaccessible or unreachable due to several possible issues, maybe blocked ports, if the machines are on the domain, check for group policies that blocks the ports, changes folder access, blocking the network account user. IT department may tell you the list of things they change with policies being pushed through.

when you run the OSConfigUtility, it checks and modify what I mentioned above, Inbound and outbound firewall, folders permissions etc.

Hi Flix,

if the data goes to the store and forward which is probably the local InTouch machine, it tells you that the Historian Server becomes inaccessible or unreachable due to several possible issues, maybe blocked ports, if the machines are on the domain, check for group policies that blocks the ports, changes folder access, blocking the network account user. IT department may tell you the list of things they change with policies being pushed through.

when you run the OSConfigUtility, it checks and modify what I mentioned above, Inbound and outbound firewall, folders permissions etc.

The issse is there, nothing was changed, no new GPO or firewall rule change. This issue will only appear if you do a change in the windowmaker. This is not a coincidence this happened 4 on 4. This is why I think there is an issue in the software.