800xA 5.1 Histroy Service Problem.

We are used 800xA 5.1 FP4 RU1 Installed.

But, Now is secondary connectivity server history service not working.

Current status is repeate the Initial -> Ready -> Initial.

I don't know. Please advicse for me.

Where can i check the my system?

Thank you.

Comments (0) New comment

krnapar Rank: 214

Asked 3 years ago

Answer this question Follow

Voted best answer

I assume Basic History?

Does it output any event to [Workplace Structure]Web System Workplace:System Event List as it start / fail?

If it reaches "Ready" it should have been able to open all log files on disk. In "Ready" state Basic History is starting OPC subscriptions. Then, the problem is likely within data subscription.

Does the process crash (change PID)?

Then I strongly recommend filing a support case with your regional ABB support center. They will likely ask you to temporarily enable "Dump On Exception" to create a full memory dump of the process when it crashes. Dumps can be analyzed by R&D.

Otherwise, you could try disabling ALL logs (easy using Log Summary aspect, don't forget to hit the Save button once you've done Disable all) and see if the service reaches service state. If so, start enabling logs in smaller batches. With additional Log Summary aspects you can start per control network, per controller, etc. until you see the problem again. Likely, the last batch of logs you enabled contain some problem.

Comments (11) New comment

by krnapar Rank: 214 on 6/30/2016 6:46:04 AM | Like (0) | Report

Event list is display the service provider Stopped and Started.
I do not change the PID.
My system use to very big history data.
About 100GB. history data.

by krnapar Rank: 214 on 6/30/2016 6:48:37 AM | Like (0) | Report

Status change time about, from initial to Ready 20-30 min.

by Stefan Stromqvist AKS expert

Rank: 1 on 6/30/2016 6:51:25 AM | Like (0) | Report

Probably too big.

One of the negative things with Basic History is the unknown maximum limits (#of logs, #of secondary aggregated logs, etc)

The good thing is that the above is just about the only bad thing - otherwise Basic History is a fast & reliable historian part of standard install with minimal footprint and license cost.

I assume that you would see Virtual Bytes go close to 2 GB (the limit) if you trace AdvHtHistorySrv.exe using Windows Performance Monitor during startup.

Try reducing your configuration.
- Do not exceed 10.000 logs
- Do not have too many hierarchy levels (not more than a handful)

by krnapar Rank: 214 on 6/30/2016 7:16:11 AM | Like (0) | Report

Thank you for reply.
I check the my server in used 12,540 hierarchy level log.

by krnapar Rank: 214 on 6/30/2016 7:17:14 AM | Like (0) | Report

But, now primary server works. I think the restart the server will not working.

by Stefan Stromqvist AKS expert

Rank: 1 on 6/30/2016 7:21:44 AM | Like (0) | Report

~10.000 primary logs is OK

But probably not having each primary with an additional 9 secondary hierarchical logs (=100.000 logs in total).

Measure Virtual Bytes. If it reaches too close to 2 GB service will fail.

Not just large number of logs may cause memory to run out, there can also be a software problem as well.

But ensure ~10.000 primary and not too many secondary logs.

by krnapar Rank: 214 on 6/30/2016 7:38:45 AM | Like (0) | Report

There are 4 connectivity server in 2 area. 1 area is using the 22000 Logs. but, now is working. I will discuss my customer and delete the history data.

by Stefan Stromqvist AKS expert

Rank: 1 on 6/30/2016 7:41:55 AM | Like (0) | Report

Each service group of Basic History can be set with ~10.000 logs and some number of secondary logs.

If you have 2 pairs, you can have 20k logs in total, 10k in each pair.

by krnapar Rank: 214 on 7/1/2016 12:32:12 PM | Like (0) | Report

Yesterday i was resolved problem. i try to the restart server then same problem.
and then shutdown the system(Power off/on) and works...Thanks for your helps.

by Stefan Stromqvist AKS expert

Rank: 1 on 7/2/2016 1:36:23 AM | Like (0) | Report

I'm not 100% convinced that problem is solved.

Configuration is still like it was before problem, right?

Basic History maximums are lesser known.

I believe problem will return, eventually. Until you have made enough changes to reduce the configuration.

I wish something was made to have it tolerate larger configurations.

by krnapar Rank: 214 on 7/2/2016 2:33:50 AM | Like (0) | Report

Yes, your right.
We will planning the log configuration change. Thanks a lot.

Add new comment

Stefan Stromqvist AKS expert

Rank: 1

Answered 3 years ago

Question details

800xA 5.1 Histroy Service Problem.

Voted best answer

Other questions needing answers

Related topics

AKS experts