Print Spooler takes a large percentage of CPU time.

[davidtheweb]

I have a recurring issue with a Print Spooler on a Windows 2000 Server. A
print job will get stuck and take a large amount of the CPU time.

I stop the print spooler in Services, go into Windows (or Winnt) | System32
| Spool | Printers and delete all jobs in that folder and restart the print
spooler. This fixes the issue temporarily, but several days later, the same
process occurs.

Is there a way to trace where the stuck print job is coming from, or has
anyone run into this same issue?

Thanks,
David

 

[Karel Slejhar]

I have similar problemon terminal server WIN2000, several times of working
day. After restart service is all OK and I cannot simulate problem. I think
that is problem of one of printers or printer drivers, but I cannot check it,
because in crash time printer spooler is completely stuck (I cannot open
printer window).

Help me any idea. Thanks
Karel Slejhar

 

[davidtheweb]

We found our problem. It was a print-to-file printer that would receive a
job, and then hang. We eliminated the print-to-file printer and have not had
the issue recur.