Commander Service Starts After Reboot, But Detection Is Disabled/stopped S’abonner

0
Avatar
Legacy Poster

Commander service starts after reboot, but detection is disabled/stopped. 

 

Can manually start Commander, select Detection -> Start Detection, and everything is fine.  However, I would like detection to start automatically when service starts.

 

Commander

Edition: Enterprise Automation (100 Printers)
Version: 9.3 SR2
Build: 2725
Windows Server 2003 standard edition(x86),SP2

5 commentaires

0
Avatar
Ian Cummings
Modérateur
Actions pour les commentaires Permalien

Choose "Automatic (Delayed)" for the startup type of the Commander service, and "Restart Service" for the first two recovery options.  Also, make sure a valid logon account is specified for the service, that has enough permissions to carry out the tasks of Commander and BarTender.

0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

Since we are using Windows Server 2003,the "delayed automatically restart" option is not available.

Please note the issue is intermittent so we have check if the task are running or not  manually every time we re start the server.is there a way where we can set-up a alert to to be sent as email is the detection has stopped.

 

one more issue we are able to successfully print the labels but once or twice a week the labels stops printing .When we check the service n server everything seems to be fine,then when we restart the server bartender prints labels successfully again.I have checked the logs but couldn't find any issue.

 

can you please advice where/what can we checked to identify the cause of the issue?

0
Avatar
Ian Cummings
Modérateur
Actions pour les commentaires Permalien

Try this:

 

1. Run the below command line from the directory where BarTender/Commander is installed.

 

cmdrsrv.exe /register

 

2. From the Windows "Start>Control Panel>Internet Options" item, under the "Advanced" tab, disable the "Check for publisher's certificate revocation" checkbox option.  This setting is a per user setting and will only apply to the current user you're logged in as.  Therefore be sure to be logged on as the same account that the Commander service uses to logon.

0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

Thanks Ian, will try what u have suggested

 

can you let if we can set-up a alert to to be sent as email is the detection has stopped.

0
Avatar
Ian Cummings
Modérateur
Actions pour les commentaires Permalien

Oops, I forgot that.  Via the "Administer>Alert Setup" you can configure an alert email to be sent for all application messages that might be generated.  Enable this and select the messages as pertains to detection stop, or anything else that might be of value.

Vous devez vous connecter pour laisser un commentaire.