Problems With Commander
Hello.
I hope someone can help me. I am having many troubles to get to print with Commander and Bartender 9.4.
This is my configuration in commander:
- I have a task configured as "Commander Script" with %Trigger Contents% as command.
- It is linked to a handler with nothing in it
- The trigger parameters are to pool for a file in C:\Commander\Scan\Print*.txt with file to be renamed to *.dat
In the generated files I have following command
%BTW% /AF="P50401.btw" /PRN="CHATTPRY206" /P /R=3 /D="%Trigger File Name%" /DD
%END%
and then a header line and the data.
From Bartender I can test and print.
Commander detects the file, renames and deletes it but nothing happens in the printer.
If I change the task to "force" the printer it works (at least sometimes)
I have two big questions:
1. In what directory should the layout "P50401.btw" be?
2. What is wrong on my set up?
Many thanks for your help.
I hope someone can help me. I am having many troubles to get to print with Commander and Bartender 9.4.
This is my configuration in commander:
- I have a task configured as "Commander Script" with %Trigger Contents% as command.
- It is linked to a handler with nothing in it
- The trigger parameters are to pool for a file in C:\Commander\Scan\Print*.txt with file to be renamed to *.dat
In the generated files I have following command
%BTW% /AF="P50401.btw" /PRN="CHATTPRY206" /P /R=3 /D="%Trigger File Name%" /DD
%END%
and then a header line and the data.
From Bartender I can test and print.
Commander detects the file, renames and deletes it but nothing happens in the printer.
If I change the task to "force" the printer it works (at least sometimes)
I have two big questions:
1. In what directory should the layout "P50401.btw" be?
2. What is wrong on my set up?
Many thanks for your help.
0
-
Gene Henson
★ BarTender Hero ★
First, for your information, you can actually specify the full path to your label formats in your trigger file. Something like this:
[code]/AF=“C:\BarTenderFiles\P50401.btw”[/code]
If you decide not to send the full path, BarTender first checks its default label format location (see below to configure), if the format is not there it will check C:\WINDOWS\system32.
To change the default label format location:
[list=1]
[*]Open BarTender
[*]Go to Administer > File and Folder Location Setup
[*]Click “Label Formats”
[*]Click Select Location to change the location
[/list]
I see no other issues with your setup.0 -
[quote name='Gene H - Seagull Support' timestamp='1320871404' post='1018']
First, for your information, you can actually specify the full path to your label formats in your trigger file. Something like this:
[code]/AF=“C:\BarTenderFiles\P50401.btw”[/code]
If you decide not to send the full path, BarTender first checks its default label format location (see below to configure), if the format is not there it will check C:\WINDOWS\system32.
To change the default label format location:
[list=1]
[*]Open BarTender
[*]Go to Administer > File and Folder Location Setup
[*]Click “Label Formats”
[*]Click Select Location to change the location
[/list]
I see no other issues with your setup.
[/quote]
Thank you very much. We managed to make it work but only it we user a user in the task.
The printer is a network printer and therefore not accessible without the user name and password.
The problem we have then is that it is mandatory for us to change the password every two months.
Is there a simple way to overcome this? For sure we can have the printer as local printer but it is not our preferred solution.
Many thanks for your support.0 -
Gene Henson
★ BarTender Hero ★
You will have to specify a user with permission to access that networked printer. The local system account that Windows services use by default does not have permission to access any network resources.
There are two ways to set the user account. The first is to specify it in the command handler for your task (which only affects the BarTender processes), as you have already done. The other way to do it is to change the user for the Commander Service itself which will cascade down to the BarTender processes.
Unfortunately, I can’t think of any workaround that will keep you from having to change the password every two months. Some users create “special” BarTender accounts that do not have to be reset on a regular basis.0 -
Thanks Gene for your reply.
It still does not work.
It only woks if I have Commander as application (not as service) and without users.
Any attempt to set up as service failed.
For other users without admin rights on the computer it did not work at all.
I am really disappointed. We bought this tool because it is easy to print but we are facing the opposite.
I am going into circles and testing everything but I still do not have a clear idea of.
1. If commander is run as service, what is the set-up? (local user, another user, ...)
2. The same for the Bartender service
3. How to enter the domain values (sometimes with \, sometimes with @, ...) for the names
4. What is the need of the user in the Commander task and when makes the user in the service not needed?
All in all, no idea how to solve this "user" thing for the constellation Commander / Bartender.
Thanks for any help.0 -
Gene Henson
★ BarTender Hero ★
First, let me apologize for the difficult experience you have had setting this up. I do hope that we get everything working correctly in a timely manner.
Here are the answers to your questions:
[u][b]1. If commander is run as service, what is the set-up? (local user, another user, ...)[/b][/u]
When Commander is run as a service, there are two things that need to be considered. First, the Commander Service will need read and write access to the directory containing the trigger files, as well as local administration privileges on the PC. Second, the BarTender processes that are started by Commander will need access to the label format directories, any database files, network printers, etc.
The easiest way to make all of this happen is to use or create a single account that has access to all of these resources. You would then set the Commander Service to use that account.
[u][b]2. The same for the Bartender service[/b][/u]
The primary responsibility of the BarTender System Service is to log various print job information to the BarTender System Database. Consequently, this Service will need access to the BarTender System Database, but only if you are using the System Database. From an account management perspective, the easiest way to handle this is to use the same account that you use for Commander. Many customers make one special “BarTender” account that has all the necessary access rights.
[u][b]3. How to enter the domain values (sometimes with \, sometimes with @, ...) for the names[/b][/u]
Typically, you will enter the user name with domainname\username.
[u][b]4. What is the need of the user in the Commander task and when makes the user in the service not needed?[/b][/u]
You do not need to specify any user in the Command Handler Setup (in the Commander Task) if the Commander Service account has the necessary permissions for BarTender to access the files and printers that it needs. However, if the Service account does not have access to something like a networked printer, then you can specify an account in the Command Handler that will give BarTender the rights it needs.
You may want contact your nearest regional office for some more personalized support. You shouldn’t share your contact information here, but you can mention this post when you call in we will be able to get you setup. There is no charge for our support, and we can discuss these issues with you to make sure that you that get everything setup as quickly as possible.
Here is our contact information [url="http://www.seagullscientific.com/aspx/contact_us.aspx"]http://www.seagullscientific.com/aspx/contact_us.aspx[/url]0 -
Thanks Gene for your time and your comprehensive answer.
I think you mentioned one point it was not yet clear to me. "the Commander Service will need ... local administration privileges on the PC". Actually this may be the reason why (sometimes) it works for me and not for the "end user".
Nevertheless I am still puzzled with the fact that for the moment in only works as application and not as service.
I will check tomorrow with my colleagues with some existing admin users and eventually create a new one for Bartender.
If this does not work I will contact the regional support in Europe.0
サインインしてコメントを残してください。
コメント
6件のコメント