Commander Printing Wrong Template
Occasionally, even though the trigger files specifies one template and printer, Commander uses the wrong template but on the correct printer.
If the trigger file is dropped again after a wait of some time, the same trigger file processes correctly.
-
Could you post one of your trigger files for us to examine? If possible, also attach the Commander task list (.tl).
What exact Edition, Version and Build of BarTender is in use?
0 -
We are using 10.0.SR4
Build 2868
We print in pairs; an outer label and an inner label.
The two .bt files (drop files) are nearly identical except for the printer and the template
In this case, the "inner" label data printed on the inner label printer but sued the outer label template.
After about 10 hours (overnight), I dropped the two files again and they printed correctly.
Since we are a implanted medical device business, any deviation from expected results puts us in full stop until a bunch of quality people can review and sign off. So an incident like this causes us to stop production for about 24-48 hours.
0 -
As a test, open your task list in Commander, select the "Detection > BarTender Command Handler Setup" Menu entry. Select the "Document Caching" tab and disable the first checkbox. Does the same issue still occur when this setting is disabled?
Also, try running Commander as an application (via the "Administer > Service Setup" dialog) for some days and let me know if the issue still appears.
Finally, under which Windows account is "Commander Service" running?
0 -
We seem to have discovered that our program that generates input files for Commander produced them too close together in time. By putting a 10 second pause between the two file creates, the problem seems to be better. But since the problem does not occur consistently, we need to wait a few weeks to be sure.
0
Please sign in to leave a comment.
Comments
4 comments