We manage the print server of a University. The server is running Windows Server 2008 r2 x64 Enterprise with SP1 installed.
The server has over 100 MFD's and MFP's. They are almost exclusively all Fuji Xerox devices. Combining the x86, x64, PCL and PS drivers, there are over 150 different drivers on the server.
The printers, ports and drivers are managed exclusively through the Print Management mmc.
The issue we have had for the last couple of months, is that sporadically, users have not been able to print or map print queues from the server. When this happens, existing print jobs are visible in the queues, but no action is being taken with them. It also sometimes causes users MS Office programs to lock up when trying to print. Logged on to the server, the admin is able to send a print job successfully and the job prints out at the MFD.
To restore service is simple, restart the print spooler. This instantly restores service and functionality to the users. Unfortunately, I don't know what is actually causing the 'lock up' to occur.
In the PrintService event log, when there is an issue there seems to be a lot of the following message
"An administrator moved document 182, Remote Downlevel Document owned by user
to position 1 on print queue
. This changes when the document will print. No user action is required. "
They are normally grouped in lines of 10 or more. This may mean that when the issue occurs, Mac users may still be able to print, or Mac users are stopping other users from printing.
If it is a driver causing these issues, is there a way to identify, isolate and then remove it? Or is it an RPC issue that is stopping users from making the connection to the print server?