Posted on 11-01-2018 06:52 AM
We are suddenly seeing an issue with Papercut where a user will print to a queue, and then walk over to a printer they have always used (let's call it printer A), login and see the job they want to release, select it, and tell it to 'print'...
Then nothing comes out.
Later that day someone will notice it came out on another printer two buildings away (now known as printer B). When we go into Papercut and look at the job, it does in fact show that it was released at the printer two buildings away where it came out (B), and not where the person actually released it (A).
This does not seem to follow any sort pattern of users or machines, all of which seems to work fine in other locations, at other times.
Solved! Go to Solution.
Posted on 11-06-2018 10:13 AM
Thanks for replying. We figure out yesterday that a couple of the printers did not hold the redirect info
Posted on 11-01-2018 07:56 AM
Sounds like the queues in the Papercut console has changed.
Posted on 11-06-2018 05:57 AM
Call your support company for Papercut (ACDI in my case). What's the mechanism you're using for release? We presently use quick release devices for our prox cards that are external to our copiers/printers.
Posted on 11-06-2018 10:13 AM
Thanks for replying. We figure out yesterday that a couple of the printers did not hold the redirect info