800xA 6.0.3, AdvHtHistorySrv load hard drive on operator users
Hi!
We have 2 redundant ASCS servers combined with the Operator Station. When logging on under 800xAAdmin user (IndustrialITAdmin group) its all normally, when trying the same under Operator users AdvHtHistorySrv service take a lot of hard drive resources for a long time.
I thought that this service run under System user and it no depend on logged on users, but we faced with the difference behaviour.
What may be the reason of this?
We have 2 redundant ASCS servers combined with the Operator Station. When logging on under 800xAAdmin user (IndustrialITAdmin group) its all normally, when trying the same under Operator users AdvHtHistorySrv service take a lot of hard drive resources for a long time.
I thought that this service run under System user and it no depend on logged on users, but we faced with the difference behaviour.
What may be the reason of this?
Asked 3 months ago
Voted best answer
1
Sounds very odd.
The behaviour of AdvHtHistorySrv (also known as Basic History) which runs as a background service should not differ depending on logged on user, unless the desktop user (or any other client) makes a trend request.
Basic History perform background sync after a reboot/restart to catch up lost data. This sync is slow and should normally pass undetected as PercentSynchronized property slowly increase towards 100%.
Are there any other clients connected (over network) that could trigger the load? Eg a report run by the Scheduler service?
Is the problem repeatable? Then I suggest filing a support case with your regional ABB support center.
The behaviour of AdvHtHistorySrv (also known as Basic History) which runs as a background service should not differ depending on logged on user, unless the desktop user (or any other client) makes a trend request.
Basic History perform background sync after a reboot/restart to catch up lost data. This sync is slow and should normally pass undetected as PercentSynchronized property slowly increase towards 100%.
Are there any other clients connected (over network) that could trigger the load? Eg a report run by the Scheduler service?
Is the problem repeatable? Then I suggest filing a support case with your regional ABB support center.
Add new comment