PRINTING PROBLEMS AND THEIR FIXES
Open task manager, Processes, Click Show processes for all users, change the view to include Commit size memory, Threads, and Handles or track this using the performance monitor
Performance issues are caused by a memory leak on a Windows Server 2008-based print server that has many Windows Vista-based printer clients
WINDOWS SERVER MEMORY LEAK FIX
The Printer Spooler service may encounter an access violation and crash when the service handles asynchronous notifications from print clients on Windows Server 2008-based or Windows Vista Service Pack 1-based computers
ASYNCRONOUS NOTIFICATION FIX I
ASYNCRONOUS NOTIFICATION FIX II
UPDATE TO THE LATEST SERVICE PACK
WHERE DOES IT RENDER
See if the issue is due to rendering on the print server. The Windows 7 clients by default perform the rendering task. XP clients by default package up the file in EMF format and the server does the rendering. This includes font information that may not be available by default on the server.
To force rendering on each XP client, uncheck “Enable advanced printing features” on the Advanced tab of each printer properties.
You can use prncnfg.vbs in \windows\system32\printing_admin_scripts\en-us to set your printers this way.
prncnfg -t -p “Printer name” +rawonly
PRINTER SETTINGS NOT BEING SAVED
Try adjusting the settings of your windows firewall… turning off or turning on.
PRINTER SETTINGS CHANGING ON THE FLY
This can sometimes be caused by service pack updates… yep… freaked me out too…
PRINT DRIVER CORRUPTION FIX