800xA for Advant Master 4.0.1. History and trend issue
Periodically (approximately one time a day) the following messages arise, history data get lost for the time.
16-12-03 08:27:28:706 Basic History_Basic_PC-OS-1 AfwServiceManager Service provider reached service state
16-12-03 08:21:21:488 Basic History_Basic_PC-OS-1 AfwServiceManager Service provider started
16-12-03 08:21:10:238 Basic History_Basic_PC-OS-1 ServiceStop CLEARED AfwAlarmEvent Service provider stopped
16-12-03 08:21:04:832 Basic History_Basic_PC-OS-1 ServiceStop AfwAlarmEvent Service provider stopped
16-12-03 08:21:04:832 Basic History_Basic_PC-OS-1 AfwServiceManager Service provider stopped
16-12-03 08:20:46:207 Basic History_Basic_PC-OS-1 AfwServiceManager Service provider left service state
16-12-03 08:20:43:738 Basic History_Basic_PC-OS-1 AfwServiceManager Status poll timeout.
SOME points trends aren't renewed continuously, i.e. history and run-time data are not seamlessly intergated.
What does the problem connect with, what should be done to deal with it?
Thanks in advance!
Status poll timeout = service froze and will be automatically killed + restarted by the System 800xA Service Framework.
Its difficult to say what causes this lockup so let me offer this smörgåsbord of suggestions:
1) Ensure you are not exceeding 10.000 primary logs
2) Ensure number of secondary logs per primary stays at one or two
3) Consistency Check Log Templates
4) Consistency Check Log Configurations
Counting logs. DirectLogs = Primary Logs.
Unfortunately, SV4 does not have the desktop consistency check tool. In SV4 you must use the consistency check aspect which means "Find Tool + Drag N Drop" is not possible. Possibly, you must check all aspects of an object and not only the LT / LC the Find Tool + Drag N Drop method offer.
Another contingency procedure would be to use Log Summary to disable 50% of the logs and see if the problem goes away. After a few iterations (50%) you should be down on a few tens of logs to examine for errors.
However, if a 50% reduction removes the problem regardless of what part you disable it might be a volume problem after all (see item #1 and #2).
You could also let Windows Performance Monitor measure the Virtual Bytes used by the AdvHtHistorySrv.exe process - it must not go above 1500 MB.