Commander Service No Longer Starting Automatically After Windows Update
Hello,
We are running Commander as a service (BarTender suite 10.1 SR4) on several computers using Windows 7 Professional (64 bits version) up to date. The service is set to start automatically without delay. It relays on a service account to get access to a network interface directory containing the files used as triggers.
Until recently it worked flowlessly when Windows updates took place. However, since a few weeks we have discovered that after some updates, Commander service no longer restarts automatically. We have to restart the service manually despite the fact it is properly set in the services' panel.
I have contacted our IT department in charge of desktops' management. They told me nothing has changed in the Windows update process. In looking in the forum, I found that thread : http://forums.seagullscientific.com/index.php?/topic/3631-bartender-commander-service-auto-start-when-pc-start-up/
I'm going to apply this on our PC. In the meantime I would be glad to know if you got feedback about such behavior our if you would have any advice about this ?
Thanks
Christophe
-
Yes, I would suspect the Commander service needs to wait on a prerequisite, and therefore the automatic (delayed) start on the Commander service should do the trick. I believe we've seen this happen a few times after a system gets updated.
0 -
Hello Ian,
Thanks for the information. I will then turn the automatic start to automatic (delayed) and notify the users not to do SAP receipt entries for the first couple of minutes after the computer reboot.
Christophe
0
Vous devez vous connecter pour laisser un commentaire.
Commentaires
2 commentaires