Commander Not Printer 关注

0
Avatar
Legacy Poster

I have set up commander to use a trigger to print a file from a specified location and print labels.

 

When the file is saved it is showing in commander as being processed and is changing in the folder from a .txt to a .arc but is not printing.

 

I can print them manually through BarTender.

 

I have other processes set up on Commander which are all printing fine but do not use BarTender.

 

Please advise.

4 评论
0
Avatar
Shotaro Ito
评论操作 固定链接

I have set up commander to use a trigger to print a file from a specified location and print labels.

 

When the file is saved it is showing in commander as being processed and is changing in the folder from a .txt to a .arc but is not printing.

 

I can print them manually through BarTender.

 

I have other processes set up on Commander which are all printing fine but do not use BarTender.

 

Please advise.

 

Try running commander as application (Administer > Service setup) with BarTender shown all(Detection > BarTender Command handler setup > Visible windows).

it would show actual behavior and error.

 

When you run commander as service,

When network access is required, specify an administrators account to Login Commander Service from Service setup > Manage services.

If you use mapped network drive (Z: etc) in scan / document folder, change that to UNC path like "\\severname\folder".

 

For detail, check Commander troubleshooting .

0
Avatar
Legacy Poster
评论操作 固定链接

I have the same issue that after setting up Bartender, then run OracleXML.tl.  Put the file into the Scan location.  The commander picks up the file, processes it and renames the file but nothing prints.  I followed the above steps and did not find any error.

Thank

0
Avatar
Canguita
评论操作 固定链接
If your trigger file is being renamed but not printed:
 
1. Open and print the label directly from BarTender. If you cannot print the label in BarTender, refer to “Troubleshooting Printing Problems” in BarTender's help system to address the issue. If the label prints from BarTender, enable message logging on the Text File Log tab of the Log Setup dialog in both BarTender and Commander. Run the Commander task again. Any errors that Commander encounters will be logged to a log file. This will help you diagnose the issue. Locate the issue in the troubleshooting guide, or contact Technical Support to resolve the issue. If you are using the BarTender XML Script command, ensure that the BTXML code is correct. Commander's Logging pane will display any XML errors it encounters while processing a print job.
 
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.
If you are no longer experiencing issues while running Commander as an application, then you know that the Commander service may be experiencing problems, or that it may not be configured correctly. Check the following:
Ensure that the user account being used to run the service has adequate permissions. At a minimum, this account must have access to any printer(s) that will be used, the trigger folder, the task list, and the BarTender documents that will be printed. If the user account does not have write-access to one or more of these, your labels may not print. To resolve this issue, you can modify the permissions of the existing account, create a new user account for Commander-related activities, or assign a different user account that has the appropriate permissions.
Verify that all paths to network drives are specified using Universal Naming Convention (UNC) paths. Commander does not support the use of mapped letter drives.
 
5. Finally, l suppose that you are using BTXML, have you verified that you are using the correct syntax?
0
Avatar
Legacy Poster
评论操作 固定链接

Hi,

 

We have just deployed the use of commander to automate the printing our labels as packs of product is produce. It uses file as trigger, and was working for a couple of days - no problem, but then it will suddenly stop without any reason and the only option I got is to reset the bartender server.  Please note the file has been detected and was renamed but no label has been printed out.

 

I have followed the troubleshooting, and found that files are printed alright according to the logged but no label was printed out.  Temporarily, resetting the whole server seems to solve the issue, but we can't go on doing this as we are migrating a lot of our labels into bartender.

 

We are using Bartender Enterprise Automation Edition 10.1.

 

Any advise advise to solve the issue will be highly appreciated.

 

Thanks.

gbp

请先登录再写评论。