Ramdom Printing issues - Not printing everything thats sent

[newpersn]

Hello.

 

Anyone had issues with printing from Windows 10 to Server 2016/2019.

 

Some users are reporting they are sending jobs to the printer and only some of the jobs are getting printed and other jobs are lost.

 

There no print managed software installed (This has been reported at 2 of my sites)

 

Any ideas?

[GaryPad]

If you open up the queue Properties on the server and under Advanced tick the option for "Keep printed jobs" you should be able to see if they even arrive on the queue (turn this off after testing and delete all the kept jobs). The other useful tip is to run the event viewer (EVENTVWR.EXE) and expand Applications and Service Logs | Microsoft | Windows | PrintService, then right click on Operational, and under Properties you can Enable logging. This will add to the event log all future print activity so you can see what's going on (if anything!).

If all that activity looks good - so jobs are arriving on the queue and then being printed - then you might need to check the logs on the printer itself, normally accessible through the printer's web page or printing off a log from the front panel if you can log in as an admin. Possible reasons why the printer will fail to print include:

1. Wrong driver (which would be consistent for all users)

2. Not enough memory (vary by job, especially affects wide format and / or printing multi-layered PDFs especially printing PDFs natively within Chrome / Edge)

3. Corrupted print data (v rare these days but not unheard of!)

4. Print release enabled in the driver (some drivers support PIN printing - much like a print management tool) so the job will go to the printer and be held there

There are 2 settings on the queue properties which can have an effect as well. Under Advanced is "Enabled advanced printing features" and under Sharing is "Render print jobs on client computer". If the former is unchecked or the latter is checked then the job will be rendered to a printable version on the client. Otherwise it's done on the server. I've seen Xerox drivers in the past not like booklet jobs rendered on the client, so to fix it we had to enable advanced printing and disable rendering on the client. Worth a shot. Also try to determine which jobs are failing and where they are printed from - e.g. if PDFs in the browser then try opening them and print from Acrobat instead.

[newpersn]

I will check the event viewer. But its just started happening. No reason why. Computers are up to date on 21h2