I have users reporting that if the 7845 runs out of paper during a secure print job, it will complete the job with however many pages printed and not resume when supplies are added. Is there a way to have the job resume or is this a "feature" of secure print?
Solved! Go to Solution.
It is Working as intended.
Say you do a secure print job that is about the horrible things Sandra in Accounting did to Gary in the warehouse. The printout is all the collected relevant data of the case against Sandra, who sits right by that printer.
You get page 1 printed and it runs out of Black toner.
The toner is is a locked cabinet, you don't have the key (because why would an HR rep deal with printer supplies), so you need to contact someone else to get the toner put in the machine. But that person is on lunch and won't be back for 27 minutes.
So you need to wait up to 27 minutes just to get someone to get the toner and put it in the printer, so probably 35-40 minutes total. And you are hungry.
So do you want to skip lunch and sit doing nothing because you have to wait for the job to come out, or go to lunch knowing that if someone replaces the needed toner, that job won't print?
<The Sandra and Gary in this theoretical are not real people, and if they are, I'm sure Sandra is not as evil as this investigation leads us to believe>
Hello Joe, I know this is an old subject, but will this also happen if paper is out/empty? Have a B8075 that I'm getting constant complaints that their secure jobs aren't there when they get to the copier, or they are saying they aren't showing up till hours later. Yet on the server in the status, I can see them "active jobs tab, held for secure status"
Yes it will (tray empty), if things are taking hours to get to the device, switch the port from RAW to LPR and disable both LPR Byte counting and SNMP Status.
Then disable the deletion if needed via EWS > Jobs > Policies
At that point if they can't find them it would imply more on the side of User error, but I am not real proficient on the VersaLink family, but if this was a bug I should have heard of it.