Commander Is Incosistent And Does Not Always Print
Hi
I am on version 10.0.0 SR1 and run bartender as an application. It has been working fine for a month. It prints to a CAB A+ printer and has a bartender printer driver. Over the last 2 weeks have recently noticed that...
1. Sometimes it does not print any labels. Commander receives the file, but nothing is sent to the printer (I can send a test print from windows printer, I can print from bartender)
2. Commander receives the file, sends it to the printer, but the fonts have all decreased in size and page layout has moved
To remedy both of those issues above, I would stop and start the detection.
Anyone know how I can fix this or stop this from occuring?
Thanks
-
Make sure that BarTender is at its latest 10.0 service release, and that the Seagull drivers are at its latest version.
For BarTender v10.0: http://www.bartenderbarcodesoftware.com/label-software/fixes_100.aspx
For Seagull drivers: http://www.bartenderbarcodesoftware.com/drivers/windows-printer-drivers-download.aspx
Are you running Commander as an application? You've mentioned about BarTender, but I'm not sure if you mean that Commander is running as an application (rather than as a system service). Please confirm.
0 -
Hi,
Yes that was a typo. I am running commander as a application.
Thanks.
0 -
Please update BarTender to latest service release and drivers to latest versions. If the problem should reoccur, as a test, once the issue appears, choose the "Detection > Show all running BarTenders" Menu in Commander. This will make the underlying BarTender process visible. Send now the trigger file causing the problems, switch to the BT process and describe what you're seeing. Does the BT document open? Do you see any error message? What happens when you press the "Print" button?
0 -
Hi, As this doesnt occur all the time and I can not replicate the error, I will follow these steps next time they occur. Also I will update to the latest bartender service release and driver to the latest version.
Thanks
0 -
Hi
I have similar issue to the original topic, but
I am on version 10.0.0 SR1 and run bartender as a service. It prints to a Zebra GX240T printer and has latest seagull printer driver. Since we have started a mfg environment we experience the below issue:
1. In our mfg environment we run customer orders in batches. Commander receives the file, sends to the printer, but the font of the initial part in the order prints is wrong, should be BOLD, but is not. If we switch to another networked printer and reprint the file it prints BOLD. Then if we reprint the label on the original printer the label prints BOLD. If we run the same order all subsequent parts print BOLD, but when we switch to a new order we have to execute the procuedure above again.
Anyone know how I can fix this or stop this from occuring?Thanks
0 -
Do you also experience the same problem with BT's latest 10.0 SR4 service release and when Commander runs as an application instead of as a service?
What fonts are you using for these text objects? Is this a Windows font or an internal printer font? It might also be the case that you've enabled the "Substitute with Best Matching Printer Font" checkbox under the "Advanced" sub-tab of the "Font" tab for the text object properties.
Once you've tested this, if the issue persists, you might want to attach the BT document, trigger file and Commander task list for me to examine (use the "More Reply Options" button when replying).
0 -
Hi,
To resolve this issue, I added the printer as a local printer on the same server as commander instead of mapping a networked printer.
Thanks
0
Iniciar sesión para dejar un comentario.
Comentarios
7 comentarios