Commander (As Application) Not Starting Detection Automatically
We have a little problem with our Commander. We have BT10 on a Windows Server 2008 R2 machine. Our Commander starts as application. So whenever that server gets rebooted, the correct user automatically logs in and the Commander automatically starts up. We also want the detection to start automatically especially because there is an option for it: Tools -> General Options -> Detection: Start it says. But it doesn't start.
Has anyone encountered this problem in the past?
These are my settings of the General Options (startup tab):
Task List: Open Specified Task.
List Name: location of the .tl file.
Window State: Restore Last State.
Thank you in advance.
Is there any reason why you don't run Commander as a service, as that way Commander will be started with detection running without a user needing to log into Windows manually. Note that the Commander service can be configured to login with a specific account of your choice.0
Yes, we monitor our BarTender servers and we want to see if the Commander is running or not. We are used to this setup and we like it. Also there is an option to turn this automatical detection on, it's just not working.
Thank you for your help.
Please note that Commander is meant to run as a service, by design, and is designed to solve the problem you have when it's running as a service as part of its normal operation. It seems strange to me that you would want to run it as an application just in order to monitor it thereby causing you to run into the problem you're experiencing. Running as an application is only supposed to be for the purpose of fault finding.
What is the exact version and build of BarTender/Commander that you are running?
You might wish to take a look at the Commander trouble-shooter document for more information: http://forums.seagullscientific.com/index.php?/topic/55-commander-troubleshooting/0
We have BarTender 10.0.
I've just switched to Service, just to test. Seems to be working fine. Although I get another problem now: the BarTender System Service doesn't want to start automatically. I have to go to services and press Start to get it going. His startup type is Automatic and I also tried Automatic (Delayed), both don't work.
Thank you for your kind help.
Set the BarTender System service with the same logon account that you specified for the Commander service. It'll need permissions over all the files, folders, and printers that you're likely to need in a BarTender print job.0