Commander not processing print jobs correctly Follow

Gregory Groth

I have a Task set with a trigger for BTXML files.  I can run the files without an issue through Bartender.  When I run Commander as an application, it runs without any issues.  When I run it as a service, about half the print jobs never print.  When the print job succeeds, I get similar to the following in the Log window:

[Task Name] QVC
[Date/Time] 4/19/2017 8:15:03 AM
[BTXML Script] Command Handler: BarTender1 - C:\PROGRA~2\Seagull\BARTEN~1\BarTend.exe /XMLScript=<?xml version="1.0" encoding="UTF-8"?><XMLScript Version="2.0"><Command Name="Job2"><Print><Format>E:\QVC\Templates\QVCLabel.btw</Format><RecordSet Name="QVC" Type="btOLEDB"><UserId>ATAPP</UserId><Password>@ffyT@ppl3</Password><SQLStatement>SELECT * FROM PrintBatchView WHERE PrintBatchID = 54 ORDER BY QVCOrderNumber DESC</SQLStatement></RecordSet><PrintSetup><Printer>KONICA951-OFFICE</Printer><PaperTray>Tray4</PaperTray></PrintSetup></Print></Command></XMLScript>

When the print job fails, the log window displays similar to the following:

[Task Name] QVC
[Date/Time] 4/19/2017 8:50:32 AM
[BarTender Command] Command Handler: BarTender1 - C:\PROGRA~2\Seagull\BARTEN~1\BarTend.exe /P

I've tried bumping up the Desktop Heap to 2048 to no avail.  These are relatively small print jobs, 2-3 pages on 1-2 templates.  Any idea on why it keep trying to run the job as a BarTender command rather than BTXML? Do I need to bump up the memory further?  We're currently running BarTender 10.1, and are planning an upgrade in the near future, and it's my understanding that Commander has been replaced by a new solution, should I consider scrapping Commander and upgrading to its replacement instead?

Please sign in to leave a comment.