Printing Is Ignoring Trigger ? Printid 追蹤

0
Avatar
Legacy Poster

What could be wrong with a printer label .btw file, if the trigger seems to be ignored.  I am generating a command string that includes a parameter to use in the query in order to filter.  However, it seems that its being ignored.  Print preview in bartender shows correctly, that when i enter a value for this parameter, i only get one record.  So then it has to be something that commander is doing which is not pulling this filter into the command that gets fired off, or when the label gets loaded, the filter parameter isnt getting used.

 

Ideas or suggestions welcome

 

4 意見

0
Avatar
Legacy Poster
評論操作 永久連結

Ok, after spending a bit more time with this system which Im still new to, I realized the commander service was running as a  local system account.

I found the older thread

http://seagullscientific.invisionzone.com/index.php?/topic/384-problems-with-commander/

 

That helped me think though a few of the issues I was having, especially the strange behavior with labels either getting OLE DB errors or printing the incorrect content.  Our commander service was running as a local system account, instead of a domain account.  Testing one of the tasks, and changing it over to run as a domain account which had access to the printer that the task was specified to use (in the flag file), allowed the label to print correctly.  Now I am in the process of getting a domain account to run the other tasks under.

0
Avatar
Fernando Ramos Miracle
版主
評論操作 永久連結

Note that if you have the Commander service running under an account with enough user access, the BarTender command handler from all your tasks should inherit these permissions (in case you don't manually enter any specified user account for that precise command handler).

0
Avatar
Legacy Poster
評論操作 永久連結

Fernando - thank you, yes its the handler that I actually changed to test the problems.  The Commander service itself is in fact running under a specific user account that has plenty of access.  Our "live" system that is being used never had an issue, its when testing a different task, and running into trouble with labels not printing correctly, that I changed the task to run as a specific network credential.  

 

How does the handler relate to the Commander service itself?  Does the service use the handler with windows impersonation or something similar?

 

The situation as I can explain it now is like this

(A) Commander service > Database server 1 (works ok)

(B) Commander service > Test database server (strange problems, some work some dont or print incorrect data)

 

Its with the (B) case that a task that is trying to access a test database server and test printer which has problems.  When the task is run, sometimes the incorrect query prompt values are used, sometimes it doesnt even populate.  When I changed the handler for that task (not realizing it changed it for all tasks), the problems went away.

 

So again, Im curious what the relationship is between the Commander service and the handler is.  

0
Avatar
Fernando Ramos Miracle
版主
評論操作 永久連結

The BarTender command handler should certainly inherit the access rights of the user under which the service is running when the latter doesn't have any user account specified. That's been the way it works for some time now.

 

As a tip on troubleshooting Commander:

If you want to make sure your problems are due to user access rights, the first thing you should try is having Commander run as an application (from the "Administer >Service Setup..." option . If everything works as expected then 99% of the time the fault lies in user access issues. This way you have an easy and fast way of saving time and avoiding any document, task or trigger configuration (which usually are the most troublesome ones).

登入寫評論。