Suddenly: [Commander Error] Commander Could Not Launch Bartender.
-
Try this: Stop and then restart detection. If that doesn't help restart the Commander Windows service. If no help then open up and command prompt window (DOS), change directory to where BarTender is installed and enter in the command line: bartend.exe /register
The below Commander trouble shooter might also be of help to you:
http://forums.seagullscientific.com/index.php?/topic/55-commander-troubleshooting/
0 -
i had already tried to stop and start detection several times. i tried again, with no succes. i had already tried to register : i tried again with no succes. after 'start detection' it takes 1 minute to give the error "[Commander Error] Commander could not launch BarTender" i have restarted the service, with no succes. the same problem occurs when running as a service or as an application. i deleted my new tasks (thinking what were the last changes before it stopped working), but with no success. changed commander service logon back to 'local system account', now it will run the tasklist whithout the tasks that require network drive access. as soon as a networked drive task is added, (even disabled) i get the error again. with a service account, that has access to those network dirs, error again. it worked with that user account this morning, in that dir. i am out of ideas. 0 -
When running Commander as a service you should always specify a logon account for the service that has adequate permissions over all the files, folder, databases, and printers that BarTender is likely to use when printing. The BarTender processes that are spawned by Commander will inherit these permissions when running, and thereby not get blocked by user access issues. I believe this is covered in the trouble shooting document I linked you to previously.
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
3 Kommentare