Trouble Having Commander Print To Adobe Pdf
I have a label setup to print data from our SQL database. When printed manually from Bartender Automation (v. 10.0 sr1), it works fine. When i try to print from Commander via a file detection, the file gets detected, but after that it seems to get stuck.
1. Here is the command i setup:
/AF="C:\Program Files\Seagull\Formats\4th class label SB IMpB-A.btw" /PRN="Adobe PDF" /P /PrintJobName="abc123"
2. i have the Adobe PDF print settings set to print to a specific folder, and to not prompt for filename.
after the file gets detected and deleted, the occurances count is incremented, but the label PDF file is not created in the output folder. can anyone see any issues with my setup?
1. Here is the command i setup:
/AF="C:\Program Files\Seagull\Formats\4th class label SB IMpB-A.btw" /PRN="Adobe PDF" /P /PrintJobName="abc123"
2. i have the Adobe PDF print settings set to print to a specific folder, and to not prompt for filename.
after the file gets detected and deleted, the occurances count is incremented, but the label PDF file is not created in the output folder. can anyone see any issues with my setup?
0
-
You should specify the Print Job Name using a Commander variable.
/PrintJobName="%Trigger File Name%"
This would typically be specified in the Commander script or in the “Additional Command Parameters” section under the general tab.
For general Commander issues, be sure to read through the trouble-shooter at the below link:
http://seagullscientific.invisionzone.com/index.php?/topic/55-commander-troubleshooting/
If you still have problems, then post more to this thread.0 -
Gene Henson
★ BarTender Hero ★
You may also be running into a security issue. If the folder that Adobe is writing to is located on a network directory, the Commander Service may not be able to write to that location. You may want to try changing the Commander service to run under a specific user that is known to have full access to the directory. 0 -
Hey ...
rb123, has this been solved?
I'm trying something similar, and have the same problems. I'm using trial bartender and commander v. 10.0 sr2
If I specify /PrintJobName="abc123", I can see the job name in the PDT print queue, but nothong happends. If I print from within bartender all is ok, i get a nice PDF file.
My trigger file i placed in c:\commander\file.dd and I want the pdf file to be placed in c:\pdf\email.pdf.
So I set /PrintJobName="email", and configures Bullzip to print pdf in c:\pdf\<docname>.pdf
As i said, it goes to the printdriver, and then wanish!!!
Has it something to do with the trial version?
What to do?
Regards
John0
請登入寫評論。
評論
3 條評論