Commander Task Error

Legacy Poster

• 19. März 2014 01:34

Hi,

 

We are having a problem at a site of ours using Commander \ Bartender v10.10 with 7 tasks. 

Approx 150 labels get printed here a day.

 

The tasks themselves monitor a network share for a TXT file with subfolders for each printer E.G:

 

\\servername\BartenderFiles\Printer1\       -Monitoring for StockItem.txt

\\servername\BartenderFiles\Printer2\       -Monitoring for StockItem.txt

\\servername\BartenderFiles\Printer3\       -Monitoring for StockItem.txt

\\servername\BartenderFiles\Printer4\       -Monitoring for StockItem.txt

\\servername\BartenderFiles\Printer5\       -Monitoring for StockItem.txt

\\servername\BartenderFiles\                    -Monitoring for PickCust.txt

 

The tasks then run the following command:

 

/AF="C:\Bartender_Layout\StockItemZebra.btw" /PRN="Zebra_172.18.12.161" /P /D="%Trigger File Name%" /DD

 

 

The problem we are having is every 3rd or 4th task will produce the following error:

 

[Task Name] PickCustomer

[Date/Time] 19/03/2014 11:16:27 AM

[BarTender Command] Command Handler: BarTender8 - C:\PROGRA~1\Seagull\BARTEN~1\BarTend.exe /AF="C:\Bartender_Layout\PickCust.btw" /PRN="Datamax I-4210" /P /D="\\sss-app-01\BartenderFiles\PickCust.dat" /DD

 

[Error] BarTender process <5684> is unresponsive.   The process will be restarted.

 

[Error] The following command has failed and will be attempted again:

/AF="C:\Bartender_Layout\StockItemZebra.btw" /PRN="Zebra_172.18.12.164" /P /D="\\sss-app-01\BartenderFiles\Printer4\StockItem.dat" /DD

 

[Error] BarTender process <2692> is unresponsive.   The process will be restarted.

 

[Error] The following command has failed and will be attempted again:

/AF="C:\Bartender_Layout\PickCust.btw" /PRN="Datamax I-4210" /P /D="\\sss-app-01\BartenderFiles\PickCust.dat" /DD

 

 

Eventually the job will process but while its sitting there we start to get double ups, triple ups and sometimes 4 copies of DAT files sitting waiting to be processed and deleted.

Each Task has its own handler running as a Domain admin, I've confirmed full read\ write access on the network share.

 

I need some help troubleshooting this to find out why its happening, when the error happens labels can take up to 15 minutes to print while Commander works itself out, often the floor manager will get frustrated and just restart the Commander service, this helps sometimes but when its bad enough it wont and we have to remove all .DAT files, stop the service and start it again.

 

 

0

• 

  Domingo Rodriguez

  Moderator

  ★ BarTender Hero ★

  • 19. März 2014 12:27

  For start, please send us your Commander task list (.tl), some of the trigger files and BarTender documents, a screenshot of the "Help > About" dialog from BarTender and a printer driver information file if you have installed Seagull drivers on this computer. In order to obtain this file, access the "Printers & Faxes" dialog in Windows, open the printer properties for your thermal printer and access the "About" dialog. Click on "Version > Save" and send the file which results.

   

  We might need to end up troubleshooting this issue by email / telephone as the problem involves BT processes being unresponsive, and just by looking at the files it might be difficult to find out the cause for the problem to occur.

  0
• 

  Legacy Poster

  ★ BarTender Hero ★

  • 19. März 2014 22:55

  Hi,

   

  Please find attached the information requested, I've also submitted the support request via email although I'm yet to hear back.

   

   

  Thanks for your help,

  Jaeden Cook.

  0
• 

  Domingo Rodriguez

  Moderator

  ★ BarTender Hero ★

  • 21. März 2014 17:00

  I don't see anything obvious in your configuration that would lead to this problem. In your Commander tasks, for scanning the trigger file shared folders (such as "\\sss-app-01\BartenderFiles\Printer1\"), try using Polling instead of Immediate.Try running Commander as an application for some days and let us know if the issue still occurs.

   

  Please continue troubleshooting the issue with the corresponding tech-support office and let us know the outcome.

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.