Print Spooler takes a large percentage of CPU time.

[Guest 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