ABB AdvHtHistorySrv.1 State not Running
We have a setup of 800xA V6 and Knowledge Manager where we have Primary & secondary aspect servers and Primary & secondary connectivity server (AS1,AS2 & CS1 ,CS2)
AS2 (172.16.4.2) has been used in KM PLI as data server and afw.OpcDasurrogat1 been used DA prog id & AdvHtHistorySrv.1 used for HDA.
Required DCOM settings has been performed and Data collection is stable and we are able generate KM logs, When it is checked for HDA in the system logs it is saying
AdvHtHistorySrv.1 Connected
But State - Not running.
Is it because Connectivity servers are having basic history service and we have used Aspect server?
or is it because some other configuration is missiing?
How to test this?
AS2 (172.16.4.2) has been used in KM PLI as data server and afw.OpcDasurrogat1 been used DA prog id & AdvHtHistorySrv.1 used for HDA.
Required DCOM settings has been performed and Data collection is stable and we are able generate KM logs, When it is checked for HDA in the system logs it is saying
AdvHtHistorySrv.1 Connected
But State - Not running.
Is it because Connectivity servers are having basic history service and we have used Aspect server?
or is it because some other configuration is missiing?
How to test this?
Asked 1 month ago
Answers
0
There is a method utilizing the AppLogViewer to test the AdvHtHistory connections in each node. I have attached a procedure that I have utilized in the past.
Regards,
Geof Ledin
Regards,
Geof Ledin
0
The service you mention by progID is called Basic History.
It only runs in nodes where it has been manually deployed from the Configure System Task of SCC. You cannot launch it as a COM service.
Theoretically, you can configure one new service group and provider for use with KM. As long as no History Source points to this new group it will remain a sitting duck.
It only runs in nodes where it has been manually deployed from the Configure System Task of SCC. You cannot launch it as a COM service.
Theoretically, you can configure one new service group and provider for use with KM. As long as no History Source points to this new group it will remain a sitting duck.
Add new comment