Commander Running As A Service 追蹤
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 ?