Pulse not started after reboot server

Hi,

We got a client they got regular maintenance and reboot the server every Sunday in the morning, but found Pulse services not started after reboot then need to start them manually; confirmed both Pulse services have already been set to “Automatic”, and checked there is no any Pulse related error in Event Viewer, any clue for this…?

Reboot server around 2020/11/29 06:30am (It’s me started service manually around 2020-11-30 10:00am)
Pulse.log (service started)

Server.log (seems no starting service record)

hi @vhsieh,

This most likely is a problem within Windows because there is nothing in the application preventing the start up on account of external dependencies.

Regards,

Erik

I have also seen this quite often. If you change the startup type to “Automatic (Delayed Start)” then this usually fixes it.

@cw-ch-scott,

Thanks, you mean to set both Pulse related services to Delayed Start, right? Will try it and see if this could be solved.

@vhsieh,

you could set up only the Pulse application Server. When this starts it should fire up the Pulse For TM1 Service as the latter is a dependency of the former.

Regards,
Erik

Hi,

Thank all of you, will try it to see if it’s back to normal after next regular maintenance.