Two Tasks In .tl, Same Printer, First Task Created Works, Second Doesn't
Hello,
I have a task list (.tl) with two tasks. Both tasks point to the same printer (Dymo LabelWriter Twin Turbo) and monitor the same folder. The trigger files for both tasks are named differently. One task looks for a file named ShippingLabel.txt, the other looks for ItemLabel.txt.
The ShippingLabel.txt task was the first created and works all the time. The second task never works. For both tasks, the file gets dropped into the folder, and gets renamed to .old, but I never see the printer spool the job for the second task. The first task works every time however.
Any ideas?
Here's how my environment is setup:
Bartender:
Automation Version 10.1 SR2 Build 2945
OS:
Windows Server 2008 R2 Datacenter (x64) SP1
Printers:
Dymo Labelwriter Twin Turbo Model# 93085
UPS Thermal Model# Eltron 2844 CTP
-
Any chance you could attach your Commander task list file (.tl), the BarTender document and trigger file which fail to print? Use the "More Reply Option" button to include these files.
As a quick test, switch Commander to run as an application rather than as a service (do this via the "Administer > Service Setup" dialog). Start Detection in Commander, and before sending the trigger file, choose "Detection > Show all running BarTenders". The underlying BT process should appear now. Send the trigger file and observe what occurs in BarTender. Does the BT document open, does any error message appears?
0 -
Hello,
About your issue, please try this steps:
1. Open and print the label directly from BarTender. Check if any warning/error message is being displayed, If yes, please let us know the message number.
2. Verify that you are using the appropriate Detection Method. When your task is setup to detect a File trigger, there are two types of detection methods you can select from: Polling and Immediate. The Detection Method is selected on the Trigger tab of the Task Options dialog.
Immediate can be used to detect any files that are located on a Windows drive, either local or network. When using Immediate detection method, Commander will respond immediately when a new file is detected in the specified folder.
Polling can be used to detect files located on all drives, including non-Windows shared drives. With this detection method, Commander will check for new trigger files only at the specified intervals.Note that if you are monitoring a non-Windows drive, you must use Polling as the detection method.3. Verify that you are using the appropriate Detection Response. Once a file trigger is detected, you have two choices on what to do with it: delete the file or rename it. The Detection Response is selected on the Trigger tab of the Task Options dialog.When you are using data contained inside the trigger file, you want to rename the file. If you delete it, then the data will also be deleted, and your labels may not print as expected. To delete the file after the data has been used to print your labels, use the /DD command line parameter (when using Commander Scripts), or select Delete File When Done on the Text File tab of the BarTender Command Options dialog (when using BarTender Commands).4. If you are running Commander as a service, run Commander as an application.5. If you are using Commander Script, ensure that you are using the correct syntax.0 -
Any chance you could attach your Commander task list file (.tl), the BarTender document and trigger file which fail to print? Use the "More Reply Option" button to include these files.
As a quick test, switch Commander to run as an application rather than as a service (do this via the "Administer > Service Setup" dialog). Start Detection in Commander, and before sending the trigger file, choose "Detection > Show all running BarTenders". The underlying BT process should appear now. Send the trigger file and observe what occurs in BarTender. Does the BT document open, does any error message appears?
Thank you for the prompt response. I followed all of your above instructions and I did in fact encounter two errors within Bartender. One was an Invalid printer. The other said the database file ItemLabel.txt could not be found. I will work through the two errors to see if I resolving them fixes the issue. Thanks again for your help and support.
0 -
Hello,
About your issue, please try this steps:
1. Open and print the label directly from BarTender. Check if any warning/error message is being displayed, If yes, please let us know the message number.
2. Verify that you are using the appropriate Detection Method. When your task is setup to detect a File trigger, there are two types of detection methods you can select from: Polling and Immediate. The Detection Method is selected on the Trigger tab of the Task Options dialog.
Immediate can be used to detect any files that are located on a Windows drive, either local or network. When using Immediate detection method, Commander will respond immediately when a new file is detected in the specified folder.
Polling can be used to detect files located on all drives, including non-Windows shared drives. With this detection method, Commander will check for new trigger files only at the specified intervals.Note that if you are monitoring a non-Windows drive, you must use Polling as the detection method.3. Verify that you are using the appropriate Detection Response. Once a file trigger is detected, you have two choices on what to do with it: delete the file or rename it. The Detection Response is selected on the Trigger tab of the Task Options dialog.When you are using data contained inside the trigger file, you want to rename the file. If you delete it, then the data will also be deleted, and your labels may not print as expected. To delete the file after the data has been used to print your labels, use the /DD command line parameter (when using Commander Scripts), or select Delete File When Done on the Text File tab of the BarTender Command Options dialog (when using BarTender Commands).4. If you are running Commander as a service, run Commander as an application.5. If you are using Commander Script, ensure that you are using the correct syntax.I've bolded important text to increase readability.
1. When I open the label file (.btw) directly, I am able to print normally.
2. I currently have the detection method set to Polling at the default interval of 1000 milliseconds. I choose this method because I read on another forum thread that this could increase print speed. I used to have both tasks set to Immediate but I noticed a long pause when the job was sent to the print spool. The spool would remain empty for a long period of time and then show the job and instantly clear. Changing the detection method to Polling and 1000 milliseconds, I noticed faster results. However, thank you for the additional information regarding the two detection methods.
3. We are currently renaming the database file to .old so we can get an idea on the usage of each label, We planned on doing this until we could get to know the other software suites that can do the same thing. However, I feel it's a good idea to leave this as is.
4. We host Bartender on our utility server and at times it may need a reboot. Would putting the Commander task list file .tl in the Windows Startup folder open Commander as an application?
5. We currently do not use Commander Scripts, other than the one that is automatically generated within the task creation process.
Thank you for the quick and insightful reply!
0 -
Any chance you could attach your Commander task list file (.tl), the BarTender document and trigger file which fail to print? Use the "More Reply Option" button to include these files.
As a quick test, switch Commander to run as an application rather than as a service (do this via the "Administer > Service Setup" dialog). Start Detection in Commander, and before sending the trigger file, choose "Detection > Show all running BarTenders". The underlying BT process should appear now. Send the trigger file and observe what occurs in BarTender. Does the BT document open, does any error message appears?
Thank you for the prompt response. I followed all of your above instructions and I did in fact encounter two errors within Bartender. One was an Invalid printer. The other said the database file ItemLabel.txt could not be found. I will work through the two errors to see if I resolving them fixes the issue. Thanks again for your help and support.
I resolved the first of the two errors by selecting the correct printer. The task list printer was selected as a (redirected) printer. When I remote into the server, an option to have my local printers appear on the remote machine makes the same label printer appear. I selected the remote server's instance of the printer and I did not receive the printer related error message.
However, I am still receiving the database file message. It says it is unable to find the ItemLabel.txt file. The task does rename this file to .old but it's strange because the first task (Shipping Label) behaves the same way and does not produce an error.
I've attached my .tl file.
0 -
Please open the properties for your "ItemLabel_STA" task and select the "Commands" tab and now click the "..." button. Choose the "Text File" tab and remove what you've written there:
"\\CC-SLTM1\OutputFiles\labels\CCP_STA_APP\ItemLabel.txt"
Instead, please write Commander's default value for this, which is "%Trigger File Name%"
At print time, the %Trigger File Name% variable will get replaced with the real renamed trigger file.
Let us know if this solves the issue.
0 -
Please open the properties for your "ItemLabel_STA" task and select the "Commands" tab and now click the "..." button. Choose the "Text File" tab and remove what you've written there:
"\\CC-SLTM1\OutputFiles\labels\CCP_STA_APP\ItemLabel.txt"
Instead, please write Commander's default value for this, which is "%Trigger File Name%"
At print time, the %Trigger File Name% variable will get replaced with the real renamed trigger file.
Let us know if this solves the issue.
That worked! Thank you so much for your help and support.
0
Iniciar sesión para dejar un comentario.
Comentarios
7 comentarios