Commander Running As A Service

Legacy Poster

• 15 de abril de 2013 09:15

Hello,

 

we are running Commander 10.0 SR2, build 2863  on Windows Server 2008 R2 Datacenter [x64], SP1

Commander is running as a service (automatic delayed)

 

This weekend the server was rebooted due to Windows updates.

This morning labels didn't print automatically.

 

Commander service was running, trigger file was there, not renamed.

When I manually clicked on start detection <F3> label was printed.

 

So it looks like after reboot and restart of server, service Commander is in mode 'stopped'.

How can I change ?

 

 

Best regards

Michael

 

 

 

 

0

• 

  Domingo Rodriguez

  Moderador

  ★ BarTender Hero ★

  • 15 de abril de 2013 14:27

  Please update BarTender (and Seagull License Server) to the latest service release, which is 10.0 SR4:

  http://www.bartenderbarcodesoftware.com/label-software/fixes_100.aspx

   

  This was a bug in Commander which was fixed in SR3.

  0
• 

  Legacy Poster

  ★ BarTender Hero ★

  • 18 de abril de 2013 04:21

  I did this.

  And now there is NO commander service installed.

  0
• 

  Legacy Poster

  ★ BarTender Hero ★

  • 18 de abril de 2013 04:28

  Corrected by using SC to create the Commander Service entries

  0

Iniciar sesión para dejar un comentario.