Print Station 2021 Sending Label Jobs Individually
Hi
We are tryiong to use Print Station to print our Bartender labels that are connected to a SQL database
When submitting a print job to print the same label 500 times, Print Station seems to be submitting the label job 500 times where up on it will eventually crashes
In Bartender Designer we can just one job of 500 labels (which is what we want). Is there a way to get Print Station behaving normally?
Thanks in advance
-
Hello Ged,
Thank you for reaching us with your query.
If I understood correctly, the issue is that Print Station 2021 eventually after an undetermined amount of copies, crashes, right? Whereas BarTender Designer doesn't have this issue.
Could you tell us what edition and service release of BarTender are you currently on? You can find this information if you open BarTender Designer, under "Help > About".
Thank you in advance.0 -
Is the printer a networked device? As it sounds like a permissions issue perhaps with the account running the Print Scheduler service having insufficient permissions to access all the driver and so sends print 1 label 500 files rather than a file with a single print 500 command. Via Designer the permissions used are those of the person logged into the computer, hence the difference (or at least that is my understanding)
0 -
Hi Peter
Yes, the printer is a networked device. Print Station / Designer is accessed via our citrix environment
Xabier, we are using Bartender 2021 SR7
Thanks
0 -
The Print Scheduler is running as a local system account and the print queue is hosted on another server (we have servers for dedicated printing) so by your theory Peter I need a service account created to run the Print Scheduler Service?
0 -
I have certainly seen these kind of issues before where adjusting the Print Scheduler service account used has fixed them (see https://support.seagullscientific.com/hc/en-us/articles/360000528268-BarTender-Services-and-Permissions) but I am not sure how running in a Citrix environment may change things, sorry.
I would suggest updating to 2021 R9 first anyway to see if that clears this (I cant see anything in the R8/R9 release notes but often best to be running the most current version in case there are some none specified bug fixes that already have been applied).
0
Iniciar sesión para dejar un comentario.
Comentarios
5 comentarios