Commander Task With Shared Folder Print Nothing
Hi Team,
Bartender commander task settings for network folder is not printing. Product details are Bartender EA 10.1 (SR3) . this only happens for the network folder. it detects file and rename the file but printing does not happen. Attached the screen shot of the settings and result. Please assist. Thanks!
Regards,
Vinoth
-
What's under the "Text File" tab of the task properties?
What's the content of the trigger file?
See the below trouble shooter for help on fault finding your issue: http://forums.seagullscientific.com/index.php?/topic/55-commander-troubleshooting/
0 -
I would be willing to bet the commander service does not have access to the network folders.
0 -
Hi Lan C,
Text file trigger property can be found under the command parameters it is like /D="\\XX.X.X.XX\SHARE\TRIGGER\barcode_print_vin2.txt" /DD /Close
The text file has data with comma separated. File format as below with header. Please assist.
Buyer,PO
Abc,1234
Regards,
Vinoth
0 -
vinoth: I see what's in the log, that is not my question. I want to know what you have specifically selected under the "Text File" tab, it should be "%Trigger File Name%" and not an explicit reference to a file. In any case, have you followed the help in the trouble-shooter guide? I suggest you select the "Detection>Show All running BarTenders" menu item while running to allow you to view what's going on inside the BarTender process.
0 -
Hi Lan C,
Thanks for the info. I even tried that option of using "%Trigger File Name%". Still no effect. when i click on show all running BarTenders. It shows an empty screen as attached. No sure any other settings need to be done. But i can achieve the successfully if place the file in local pc were the commander is running. but we need to take the file from FTP server. Thanks!
Regards,
Vinoth
0 -
You see an empty BarTender application window because you include the /DD and /Close commands in your trigger file. I advise that you NEVER use the /Close command, and for testing purposes remove the /DD command while we figure out what's going wrong. The fault finding idea is to trigger a print job while watching what goes on inside the BarTender process.
Note that you should always use the "%Trigger File Name%" Commander variable for the text file setting. Trying anything else is likely to be wrong.
I assume you've not read the trouble-shooter yet? Please read it and follow its process for problem solving.
0
Iniciar sesión para dejar un comentario.
Comentarios
6 comentarios