googlemad Posted January 27, 2015 Posted January 27, 2015 On our Server 2012 R2 Papercut print server we have a pull print queue, which then sends jobs to the actual print queues once released. The pull print queue works fine, jobs stay in there as 'Paused' status until released by the user. However it was recently noticed on the actual print queues for the devices (Kyocera MFDs) that random jobs stay in the queues and the status is 'Sent to printer'. There was a small issue around disk space on the server which was recently resolved, so I decided to just clear out all these jobs thinking that might be related but a couple of new ones have already got stuck! We do get the odd person ringing up saying they released their job and nothing ever came out and I'm wondering if this is linked. Has anybody else come across similar? I did see this : Print job status remains as "Sent to printer" when Isolated mode is set in Windows 7 or Windows Server 2008 R2 But it only mentions Windows 7 and Server 2008 R2!
MatthewL Posted January 27, 2015 Posted January 27, 2015 What version of PaperCut are you on and also do your old jobs get deleted after x number of days/hours?
googlemad Posted January 30, 2015 Author Posted January 30, 2015 PaperCut MF Version: 14.2 (Build 28942) Old jobs are deleted from the pull queue after 24 hours Here is an example of what is happening
MatthewL Posted January 30, 2015 Posted January 30, 2015 Right click on the printer, go to advanced and is keep printed documents ticked?
googlemad Posted January 30, 2015 Author Posted January 30, 2015 Nope. It's puzzling me as it just seems to be jobs at random that decide to get 'stuck', as I know for a fact more than 1 document has been sent to that particular MFD over the last few days since I cleared the previous backlog!
MatthewL Posted January 30, 2015 Posted January 30, 2015 Have you restarted the print spooler and all PaperCut services? Suggest stopping spooler, clearing out any print jobs in the queues and restarting. Also maybe worth putting latest version of PaperCut on (14.3 Build 30615) just in case there is a bug.
Big_Ted Posted February 2, 2015 Posted February 2, 2015 are you using the papercut ports on the print queue?
TriggerHappyUK Posted February 2, 2015 Posted February 2, 2015 Hi, I had this with my old Server 2008 Printserver. You have to go into the driver section and change the driver isolation mode to 'none'. Hope this helps :-)
DJ3Dog Posted February 3, 2015 Posted February 3, 2015 This happend when I tried to redefine the security rights for users. If you delete or further restrict the CREATOR OWNER the client spooler will not have the rights to delete the job. Resulting in "Sent to priner" I struggled with this alot especially since we use Secure Release on HIGH scale. People see "Paused" and try to restart or cancle the jobs in the virtual queues. Make sure CREATOR OWNER has defualt rights
DJ3Dog Posted February 3, 2015 Posted February 3, 2015 Or as suggested above use the PC ports. They by default prevent user interference
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now