800xA for Advant Master 4.0.1. History and trend issue
So, with your permission I’ll continue our dialog on the score.
It’s connected the files concerning your offerings. What will be your react on them?
Can the problem be connected with the Server technical characteristics, as for example disk access speed/free space, RAM/VirtualMemory speed/volume?
As you see on picture 3.jpg History Service Provider left service state and in 10-15 minutes reached service state. And this “sudden” as a rule happens at the time of manipulation with trends as changing/moving Time scope, Display Time – data collection status rectangles begin to blinkyellow and everything suspends.
And also it can be seen here that some points data collection status rectangles are green and some ones are red – points trends aren't renewed continuously, i.e.history and run-time data are not seamlessly integrated. What is the reason?
And what does your phrase “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.” mean? What should be perpetrated?)
I really do appreciate your attention.
I have very limited time to put on this forum - for professional support, please have a support case logged with your regional ABB support center.
You did not supply memory usage according to my instruction (use Windows Performance Monitor, *not* Task Manager)
The configuration of 366 logs and roughly estimated 20 GB of disk space (364*56701kB) does not sound oversized at a first glance, but 20 GB is not small either...
Do you see any exception logs becoming updated with new modification time when the crash occur?
C:\Documents and Settings\admin>dir /s c:\*exception*.*
Directory of c:\Documents and Settings\800xaserviceaccount\Local Settings\Temp
04/11/2013 15:03 13,926 Exception_AdvAeAlarmManager.txt
11/13/2014 03:09 16,568 Exception_AdvAeEventCollector.txt
12/07/2016 09:27 4,056 Exception_AdvHtHistorySrv.txt
1) Try creating some smaller logs (not 56 MB large as the current) - do such work better?
2) Try using Log Summary to deactivate 50% of the logs - does it help?
3) Try Consistency Check of the logs and templates - see System Version 4.1 Configuration User's Guide (3BDS011222R4101)