Print Jobs Jamming on Server

[nimrodel]

Hi,

I am having a problem which has been ongoing for months and I just cannot sort it.

 

I am using Print Management on my server (running Server2016). When a client prints, the job is sent to the Print Server and then passed out to the printer (Konica Minolta BizHub454). Occasionally (at least 2 or 3 times a week) I will be informed that the printer is not working. On inspection, there will be a long list of jobs in the print queue with the earliest job "stuck". None of the other jobs will even get to the printer so because of one job, the printer is unusable.

 

The way i am fixing this is to stop the Print Spool service and delete the files in the Windows/system32/spool/printers folder. Then re-starting the print spooler clears the queue and all is working again. Trouble is, I work part time and so if the problem happens when I'm not here, it causes chaos.

 

Anyone any ideas what may be causing this and how to cure it?

[MatthewL]

What print management software are you using?

[nimrodel]

I'm not using any third party printer management; just the facility within Server 2016.

[chazzy2501]

is ANY event log triggered when a job gets stuck? if it is you could trigger a scheduled task to reset the spooler service. (also I think restarting the print spooler twice will automatically clear all pending prints) or a script to stop the spool, delete the spool folder contents and restart.

[sted]

im going to lay odds that

a your printer/copier requires users to enter a code when they click print

b its usually a pdf file

 

if the above is correct then its people printing from the windows 10 pdf viewer/edge/any other modern app. they dont use the full version of the print engine and as far as i can see cant deal with printer codes so just jam up the print queue instead. only "solution" ive found is to have a sdcheduled batch file to nuke the print queue every so often

[nimrodel]

Hi Sted,

Both of your assumptions are correct. I've come across the Windows 10 PDF print issue before but thought I'd got round it by installing Adobe Reader on all PCs. However, I think you are correct.

Could you suggest a script to clear the print queue that a member of staff (non-IT) could use in my absence. They are pushing for me to leave instructions on how to fix the problem when I'm not here, but I'm very reluctant to give admin rights / server access to anyone with little knowledge of what they are doing.

Thanks

Dave

[Steve21]

I don't know if this is still the case or not, but this was occurring with KM machines when you were using the universal drivers rather than the "standard" ones for "Apps".

 

There was a workaround too, again not tried it recently as drivers fixed it for us, but might be worth a shot if you get a minute:

 

Change the driver isolation on the printer server to none, and then deselect render jobs on client, close UI blahblah, reopen it and select render jobs on client again (don't change driver isolation back). (Might need to ensure the printers get remapped on clients too to pick up the new isolation modes, so manual delete one and try it etc)

 

Steve

Edited September 5, 2018 by Steve21

[sted]

Hi Sted,

Both of your assumptions are correct. I've come across the Windows 10 PDF print issue before but thought I'd got round it by installing Adobe Reader on all PCs. However, I think you are correct.

Could you suggest a script to clear the print queue that a member of staff (non-IT) could use in my absence. They are pushing for me to leave instructions on how to fix the problem when I'm not here, but I'm very reluctant to give admin rights / server access to anyone with little knowledge of what they are doing.

Thanks

Dave

 

without some level of admin rights to the print server you cant clear the queue which is why in schools where it happens frequently i just have a script run every 30 mins

 

something like

net stop spooler
del c:\windows\system32\spool\printers\*.* /q
net start spooler
rem pause

[nimrodel]

Hi Steve,

Thanks I'll give that a go! The drivers are the specific ones from KM for the printer, but I'll try the workaround.

 

Cheers

Dave

[nimrodel]

Thank you Sted, I'll give that a go! :-)

[chazzy2501]

You can grant users (I have a staff security group) the "Manage Documents" from the security tab. Then any teacher or admin staff can delete stuck jobs. (but if its a awaiting pin stuck job they'll need to reset the spooler anyhow so poo)

[MatthewL]

Have you created a second copy of the printer and see if that causes an issue?

 

Any maintenance messages of the MFD as some have some that can cause print issues. Try disabling SNMP on the printer port.

[nimrodel]

I've gone 2 days now without a problem, but I'm off at lunchtime until Monday so if it's going to happen again then it'll happen 5 minutes after I leave! I haven't enabled the script yet as I would like to try to fix it without doing that because it is possible that the script could clear the queue just as someone has sent a long job to the printer. However, that option will be put into action on Monday if there have been any blockages before then!

I've disabled SNMP too. Not sure how that will help but certainly worth a try. Thanks all for your advice.

 

- - - Updated - - -

 

Yeah, I find that I can never clear print jobs without stopping and starting the spooler!

[dapaulio]

Have you tried print direct to printer under properties rather than spool document?