We also have a College having the same issues. The user prints, it leaves the computer and makes it to the print server, the server spools the job, then we see it being held on the Xerox 5945 for 30 seconds to 1 min then the job dissappears. We have replaced the Xerox, Built a new print server, upgraded the firmware on the Xerox. Also what is strange is the user can print 10 times and then the next time we have the problem again. At randum times the job gets erased from the Xerox. I have sent the Xerox's logs to second level software support. We also turned on print logging on the client and when the print is successful the log only has 8 entrys. When the print fails there are over 300 enterys in the log. Any help with this issue would be greatly apprecated.
We're banging our head here with a strange problem affecting our Xerox printers and Windows 10. We are a higher education establishment with several hundred predominantly Windows 10 desktop clients and around 2000 users. We have four 75xx series Workcenter, two 3635 MFD, a 5225 Workcenter and nine Phaser 6180DN MFD printers that are shared using group policy from a Windows 2008R2 print server in an Active Directory domain.
Our problem is that when a user logs on to a PC for the first time (i.e. after reimaging the PC or in multi use areas such as the library) they are unable to print, the job appears in the print queue locally and after a few minutes just disappears. Subsequent attempts to print are usually sucessful, but the first job always fails. What tends to happen is the student moves to another PC to try and print rather than sending the job again, and of course if they have never logged into the next PC before then it will not print.
If the spooler service is restarted after logon then the first print job will work, so we have deployed a script that restarts the service two minutes after logon, although this is a bit of a brutal workaround. We're using the latest Global Print Driver, and even tried a Windows Server 2016 print server to see if it was an issue between Win 10 and Server 2008R2, but the results are the same.
This only affects our Xerox printers using the Global Print Driver on Windows 10 clients. Our HP and Canon printers are not affected, nor are our few remaining Windows 7 clients. We're not 100% sure when the problem first appeared, we noticed it after reimaging several classrooms with the latest Win 10 build (1607 14393.1066) and initially thought it was the new OS, but subsequent tests show all Win 10 builds are affected.
Any ideas appreciated!