Visual Cron Service is set to automatic start but when server reboot happens the Sagent service do not start automatically.

What is the Sagent service?

---

Sagent Service is the service on which the sagent tool runs. It is available in Administrative Tool --> Services.

Kindly find attached screenshot.

Sagent Service is the service on which the sagent tool runs. It is available in Administrative Tool --> Services.

Kindly find attached screenshot.

So, what has that service to do with VisualCron?

---

If we stop VisualCron service (highlighted in trailing post) then visual cron stops working. My problem is, sometimes due to maintenance activities the server is restarted over the weekend. At this point even though the VisualCron service is set to automatic restart; the service remains in 'STOP' status. This stops the visual cron. Let us know if can schedule call on this.

Hi Team,
Could you please provide an update on this? This is urgent.

Regards,
Abhijeet

Automatic Restart means the service (in this case VisualCron) will start if it fails. It sounds like you expecting something else but this is the behaviour of Windows.

---

Hi Henrik,
If the server is restarted again then I see that the other services are in running status. But this is not the case with VisualCron service. When restart happens then the service moves to STOP mode. We need to manually start the service. This is not the normal behavior of the windows right.

If you restart your personal PC and try to open MS Excel then it will not throw error to start the service related to MS Excel. But this is happening with VC. When I try to open VC it ask to start the service associated to it.

Hi Henrik,
If the server is restarted again then I see that the other services are in running status. But this is not the case with VisualCron service. When restart happens then the service moves to STOP mode. We need to manually start the service. This is not the normal behavior of the windows right.

If you restart your personal PC and try to open MS Excel then it will not throw error to start the service related to MS Excel. But this is happening with VC. When I try to open VC it ask to start the service associated to it.

I am not following you at all. When you say restart service I am not sure if you talk about your service or VC service.

Your example does not make sense as there is no "service" associated with MS Excel at all. At least not to open a normal document.

---

Hi Henrik,
If you don't follow me then let me explain at very very basic level.

1) If you start your computer and go to 'Run' and type services.msc you will find list of local services as per attachment.
2) There is one service related to VisualCron. The name of the service is 'VisualCron'. [Hopefully you might find this the same attachment]
3) As you can see in the attachment then there are other services too along with 'VisualCron'.
4) When the server is restarted then rest of the services remain in 'Started' status but VisualCron service remain in 'Stop' status even though the start type is automatic [please see the same screenshot again for startup type. Column number 4].
5) We want to know why the VisualCron service do not remain in 'Started' status once the server is restarted. We need to manually start this service one time until next server reboot happens.

Hope you understand this. If not kindly call my cell +917757055995 as this is critical and we are chasing for this from long time without any progress.

right, so the Sagent service has nothing to do with this.. You started by posting a screenshot where the sagent service was highlighted, so I was at least as confused as Henrik:)

I'm certainly no expert, but I would try this
1) Check the event log and see if you if you can find any error messages when rebooting server
2) Try changing from Automatic to Automatic Delayed and see if helps
3) You can also add a retry on the recovery tab and see if it helps.

Hi Team,
We have reached out to respective team but nothing was traced in the logs. They updated that this is happing for single application only so reach out to the vendor of VisualCron application.

Also rest of the two options are tried but did not got any positive response.

Have you created some kind of dependency between the Sagent service and VisualCron? I'm asking since you started the thread talking about Sagent and not vc. That part is very confusing. It would be very helpful if you could explain if Sagent has anything to do with this.

Service level there is no dependency.

ok. We can finally ignore Sagent. When you starting the thread with Sagent services, it wasted a lot of time to be honest

In this link there are 5 reasons why services may not start after reboot. You seem to have tried four of them. I would look at the group policy item (nr 4).
https://www.coretechnolo...s-service-start-at-boot/