Trigger Sends Correct Command But No Printing
I am using a windows 8 machine and bartender 10 SR4 and the commander as an application to print labels from a file trigger.
I created a sample label with a sample data file that holds one field to test the printing.
the command that was created by the commander is C:\PROGRA~2\Seagull\BARTEN~1\BarTend.exe /AF="C:\temp\Test.btw" /PRN="OKI MC360" /PD /D="C:\temp\Data.txt"
When I copy the text file to the temp folder its been renamed but not printed.
When I flaged the open print dialog box it pops up and when pressing print nothing happens, if I press test print I can see in the printers que a print job.
When I copy and paste the command line to windows command prompt it works and prints.
Any Idea why I cant get the commander to print?
Check out the Commander troubleshooting guide. It walks through some steps that might get you printing again.
Don't use the /PD command option unless you are running Commander as an application. Rather, use /P instead For fault finding, temporarily run Commander as an application, show all running BarTenders via the "Detection" menu, and don't specify the command option to delete /DD the trigger file. In this way you can test inside BarTender as to why something might not be printing. Often it is because no records are being found if it has nothing to do with the user account under which the Commander service is running.0
This is the same problem I am having. I used the trouble shooting process and when I executed the command directly, it worked - after asking for my password for access to the database.
I was unable to find a place to store a password anywhere. Is there one, and I just can't find it?
UPDATE: I found where the password can be saved - I saved it and still the labels only print when I paste the command into the command line - nothing prints when using Commander.0
How did "eyalk" get on in the end? Did you manage to solve the problem?
Out of interest, do you have any logon credentials specified for the BarTender command handler? When running Commander as an application for fault finding purposes, you should not specify any credentials in the "Logon" tab of the command handler.0
I have basically the same problem as eyalk. But everything worked fine until last week, and there are to my knowledge nothing changed on either the computer or the network.
I can print the labels manually and in the DOS-promt with the command line generated with Commander, but Commander gets stuck processing the last file triggered. Here's from the log file:[Task Name] Z1CPAPBOX[Date/Time] 2015-02-25 12:54:32[BarTender Command] Command Handler: BarTender1 - C:\PROGRA~2\Seagull\BARTEN~1\bartend.exe /AF="C:\Users\breas_production\Desktop\Trigger Z1\SN Z1 Unit Carton Base System_52205.btw" /PRN="Intermec PC43t (300 dpi) - DP" /P /D="C:\Commander\Scan\Z1CPAPBOX(2).dat" /DD[Task Name] Z1CPAPBOX[Date/Time] 2015-02-25 12:54:48[BarTender Command] Command Handler: BarTender1 - C:\PROGRA~2\Seagull\BARTEN~1\bartend.exe /AF="C:\Users\breas_production\Desktop\Trigger Z1\SN Z1 Unit Carton Base System_52205.btw" /PRN="Intermec PC43t (300 dpi) - DP" /P /D="C:\Commander\Scan\Z1CPAPBOX.dat" /DD[Information message] BarTender is still processing the last command. You could experience a performance increase by increasing the number of processes the BarTender Command Handler is using.Any ideas?0
BreasBarTender: Do some of your print requests actually not get printed? Or do all labels get printed as expected, but the information message worries you? All this information message means is that all BarTender processes for the command handler were busy at the time of the request, so therefore it got queued until such time as a BarTender process becomes available. To avoid this either increase the number of BarTender processes for the command handler, and/or upgrade to the Enterprise Automation edition that allows for this.0
Thanks for the answer.
We finally found the problem. There was an electronic signature requirement for modify database setup. Found out by activating the logs in Bartender. Why does Commander or Bartender need to modify the database setup?
We use Enterprise Automation, FYI.0
Because Commander switches the data file that the document connects to at print time. If you are already running an Enterprise Automation edition then you might wish to consider increasing the number of BarTender processes running in the BarTender command handler.0
I'm also getting the error below... I'm new to Commander, how do you increase the number of BarTender processes?
We are running Automation Edition 10.1 SR4
[Information message] BarTender is still processing the last command. You could experience aperformance increase by increasing the number of processes the BarTender Command Handler is using.0
jxg16: The Automation edition is limited to a single process per command handler. Either upgrade to Enterprise Automation in order to scale the solution, or work around the limitation by having additional command handlers. Of course that would mean you'd need to set up an additional task, and then have your system trigger each task in a round robin fashion.0