Spooler consuming high CPU - multiple erroneous \\PIPE\Spoolss
One of our servers (2003 Standard SP2, configured as DC + File/Print server for admin offices) has a print spooler consuming excessive (60-80%) cpu. Users have multiple \\pipe\spoolss sessions open which immediately reopen if I force them closed, despite no print jobs being in the queue. Pipes remain open even if the user is no longer logged onto the machine. Shutting down the remote machine is the only thing that ends the session and reduces CPU use on the spooler.
Things I've tried so far:
Rebooted the server, deleted all printers, ripped out all printer drivers, checked for updates, and then replaced with new or known good versions (that work ok on a similarly patched server). Didn't reinstall the newest printer (HP3005dn) for good measure, just in case it was the culprit. For reference, the same model printer using the same drivers shared on another server works fine - no excessive spooler cpu consumption.
After the reboot, cpu use was normal until 10am this morning when it ramped up again and is currently sat at 93%. The event logs show a lot of print jobs where pages printed = 0.
I know that document is 2 pages long at least, and I'm getting a fair few of these, so I'm assuming that the spooler is dropping jobs because of the load.
Document 104, staff telephone list 0708.xls owned by USERNAME was printed on MO-BWLaser via port IP_$IP Size in bytes: 117151; pages printed: 0
Software-wise the only changes we've made recently is updating the clients to office 2003, but it's been 3 weeks since we did this and excessive cpu consumption by the print spooler started on Friday, flagged up by Nagios.
Google reveals similar problems occuring on earlier patch versions of 2003 Server, specifically with XP clients, but the fix was part of XP SP1 (we're on SP2 + security/critical). http://support.microsoft.com/kb/835318/en-us.