Yet Another 'can't Print When Run As A Service' Post
Before you ask I have spent the last day or so reading through these posts and I know there are a lot of them, but nothing seems to be working for me.
When I run Commander as an application all is well, and everything works easily. However, switching to run Commander as a service seems to break the process. The trigger files get detected just fine and they get renamed as I have it set, but nothing will print, and I don't get any error messages. I can print from Bartender just fine.
I don't believe it is a permissions issue as both the bartender file and the trigger file are on a shared drive that all domain users have access to. Also the Command Handler and Service itself is setup to use a Domain Admin account.
Pretty much everywhere I am reading on here says it must be a permissions issue, but I believe I've ruled that out. The log files I am seeing just show me stating / stopping the service, and as I said I don't see any error messages. I've read through the troubleshooting commander PDF and still nothing seems to work.
Any ideas or direction would be greatly appreciated.
EDIT:
If it helps, here is the Command Line:
/AF="\\FileServer\Public\Bartender Testing\ItemLabel\NewItemLabels_Automated.btw" /PRN="ZP_BWP_004" /P
-
Forgot to mention I am running Enterprise Automation Version:10.1 SR2
Also, when I try to click ''Show All Running Bartenders" nothing happens. EDIT: Nevermind, this was due to me specifying the user account in the Command Handler. When I uncheck "Run Bartender under Specified Account" it shows up.
0 -
Turn on logging in BarTender and see what messages are coming from there. Commander logging isn't going to reflect anything other than detection being turned on or off, BarTender is actually what does the printing, so that's where you're going to look for answers. Since it works as an application and not as a service, the issue here is something related to the non-interactive user that you're using to run the Commander service. Maybe verify that the printer that you're using is installed for all users, and not just the interactive user that you're logged in as (if you installed it by going to \\servername\printername and clicking on it, all you did was install a view of the printer for that particular user). If you get a message that the BTW file isn't found that's permissions to the share, make sure your non-interactive user has read, write, and modify access to the folder and the files.
Also, you are using an older service release of BarTender, we'd highly recommend you get to SR4.
0 -
Ah, Thanks for the clarification on the log files.
I've verified that the printer is installed for everyone, and I don't see any messages about a BTW file. I have attached my label along with its log, and my commander task list if that helps. I'm pretty stuck at this point.
I will look at updating to SR4.
0 -
OK I see the problem. From the log:
2014-12-09 13:19:51 3300 Error File OK U:\Knuckles\Bartender\PPS\ItemLabel\Template.txt Cannot find the above file. Please verify that the correct path and file name are given.
In the label format, the default database that you used points at "U:\Knuckles\Bartender\PPS\ItemLabel\Template.txt ". The issue with that is that your U: drive is a network map, and network maps are only for the interactive user they're created for. Use the UNC path to make that work appropriately.
0 -
I do believe I heard angels singing when I read that last post...
It works! I knew in Commander I needed to use the \\ServerName format, but it didn't occur to me that would be a factor from inside BarTender. Thank you very much!
0
Please sign in to leave a comment.
Comments
5 comments