I found the issue. It is not listed in Help for Vantage 8, but is listed in a document they send out for Epicor 9. The commander steps in Vantage 8:
Create a Commander Task
The purpose of a Bartender Commander Task is to actively look for Manufacturing labels as they are created.
Open the Bartender Commander application.
Add a new task.
Enter the Task Options as follows (on the Trigger tab):
Name: Bartender
Trigger: File
Detection Method: Immediate
Folder to Scan: C:\epicor\mfgsysdata\bartender
Files to Scan for: *.bt
Detection Reponse: Rename File
New Extension: dat
Locked-File Timeout: 30 (seconds)
File Encoding: Windows System Default
Click OK.
It was missing but this is in Epicor 9 instructions:
1) Go to the Commands tab
2) Find the drop-down box under `Command Type' and select Commander Script
3) Click OK (see Task Options screen shot below)
4) On the Menu bar of the main Commander window press Administer\Service Administration
5) Confirm that Commander is set to run as a Service and the Startup Type is Automatic
The main key was step 2 above....So, for bartender, if you are getting your file for the BAM, make sure your commander task has all of these configurations setup.
Create a Commander Task
The purpose of a Bartender Commander Task is to actively look for Manufacturing labels as they are created.
Open the Bartender Commander application.
Add a new task.
Enter the Task Options as follows (on the Trigger tab):
Name: Bartender
Trigger: File
Detection Method: Immediate
Folder to Scan: C:\epicor\mfgsysdata\bartender
Files to Scan for: *.bt
Detection Reponse: Rename File
New Extension: dat
Locked-File Timeout: 30 (seconds)
File Encoding: Windows System Default
Click OK.
It was missing but this is in Epicor 9 instructions:
1) Go to the Commands tab
2) Find the drop-down box under `Command Type' and select Commander Script
3) Click OK (see Task Options screen shot below)
4) On the Menu bar of the main Commander window press Administer\Service Administration
5) Confirm that Commander is set to run as a Service and the Startup Type is Automatic
The main key was step 2 above....So, for bartender, if you are getting your file for the BAM, make sure your commander task has all of these configurations setup.
--- In vantage@yahoogroups.com, "dtatctf" <dthomas@...> wrote:
>
> Bartender uses a tool called "Commander" to print the labels. This runs continuously and monitors a network location for new bartender text files. When it sees a new file, it processes it using the data and label format specified in the text file. The printer is also specfified in that file.
>
> --- In vantage@yahoogroups.com, "Karen Schoenung" <kschoenung@> wrote:
> >
> > Hello,
> >
> > I am new to using Bartender and have just started testing the autoprint option for one form. I get the file output, but it does not actually print. System monitor reports tab shows it auto printed successfully and if I try print or print preview on the reports tab - again it says printed...However, I get nothing really printing out of my printer. This tells me the BAM is working. I can "connect" the files to the Bartender software and print from within the software...Can anyone give some troubleshooting advice?
> >
> > 1 - printer setup in Vantage - does it need to be on the application server? Can it be a path on a terminal server?
> > 2 - Are there any log files that I can check to see if there is an error that is not shown in System monitor?
> > 3 - Any other ideas?
> >
> > Thank you,
> > Karen
> >
>