AlarmLogger Service does not startup properly
I'm using the ABB AlarmLogger service to print events to a TCP/IP printer that sends the events to an SQL database. The system works fine with a service provider on redundant connecetivity servers. However, if I shut down one of the machines the service goes to error state when I power up again saying that it is not connected to a service. I then need to disable/enable the service provider that is in error and it then works immediately. Also the redundant service provider takes over but still this is an unacceptable situation as manual intervention is needed after a reboot.
Any ideas on how to make the service recover automatically? I can see that the AlarmLogger service (ABB.AdvAeLoggerServer.1) has the supervision parameters set to:
Status Poll timeout = 5 minutes, Action = Kill
Command timeout = 50 minutes, Action = Kill
I cannot change these parameters from the Service structure.
Please check whether the windows printspooler is running in the machine where Alarm logger service went to error state. If not, then this could be the reason.
Also check the Alarm Logger configuration done as per the 3BDS011222-510_en_System_800xA_5.1_Configuration.pdf.
However I suggest you to conatct your nearest supportline for further assitance.
It sounds like your TCP/IP printer is not ready when your alarm logger service starts. I'm not sure that changing the parameters you mention would resolve this problem, unless it already resolves itself after 50 minutes with the current settings.
It is probaly worth some experimenting to see which of your services (eg print spooler, sql database etc ) is the last to start up. Check to see that there are no unexpected dependencies that might be delaying startup.
While its probably not an ideal solution, you could possibly also add a dependancy or delay to the AfwSystemService, which is the core ABB setvice that starts everything else.