Discussion Locked

Printer subsystem out of whack.

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Windows2000 Pro. Upon startup I get: Error: SPOOLSV.exe has generated errors and creating and an log.(or something like that) THen when I try to add a printer, I get: Out of Resources: Due to lack of resources, this operation cannot continue. Printer subsystem unavailable. Any help on this would be great. I spent nearly 2 hours on 2 different tech support sources, neither of which could solve the problem. WHen I go to Services and start the print spooler service, it then immediatly reverts backwith the spoolsv.exe error. Very frustrating. I have also tried updating Windows and disabling items in the system tray. Thanks in advance!!

7 replies

by erikbutler

have you installed and hp printer by chance and if so you will need to uninstall the hp software and then reboot the machine and it should work

by k_pestrue

I have a similar problem with a Dell Dimension 8100 and an HP 1200 USB printer. I do not get the Spoolsv errors, my symptom is the computer running slow. The OS is W2k patched to SP-2. I have noticed that approximately 30 seconds after W2k finisheslogging in and loading services, CPU utilization on Spoolsv.exe goes to 30-50 % and memory usage incrementaly starts climbing. The printer folder will not open and the computer runs slow. I can temporarily fix the problem by stopping the print spooler service and restarting; however, after the next reboot the same thing happens. After applying the temp fix and before the next reboot the computer runs normally. I have un-installed the HP printer drivers and rebooted with the same results. Ihave pulled everything out of the startup folders and registry under the "Run" key and rebooted with the same results. I have tried to reinstall SP-2 but don't think it worked as it ran very quickly. I haven't found any references to this issue on Microsoft or Dell sites and only one here. Anybody have any suggestions? My next move is to reinstall the OS.

by k_pestrue

Thanks for the input, the fix that worked was the beta patch from Novell, 253829.exe. I never thought to look to the Novell client as causing the problem. Thanks to cordlapp@home.com for the pointer to Novell.

by laiky

i had the spoolsv.exe problem outlined in this discussion it began after a microsoft windows update patch for an NVidia 32 meg video card was installed. The spools service would hover at about 30-50% cpu utilization. if i stopped and restarted the service all was fine until the next reboot. After installing the novell beta patch 253829.exe the problem was cured. This was an especially frustrating problem because it caused several back to back rebuilds of the Vice President of out IT departmentscomputer. Once the update was installed it seems that there was no way to reverse the damadge done, uninstalling the video card, vga mode, safe mode, last known good all failed. I suspect that this is some of microsofts finest work yet!

by bprats

Windowss 2000 Pro, SP2
Linksys ppsx-1 printer server with HP DeskJet 960C. July 2001 Installation CD.
Dell 8100 laptop
LAN server Windows 2000 server SP2
Other PCs: Windows 98

I'm experiencing solid spoolsv.exe errors on the Dell 8100/Win2000 sp2 when I print to the HP960 on the remote server. When cabled locally, I don't get errors. The condition is described in Microsoft docs q260142 q258507.

This same laptop prints fine to other p-servers/printers and likewise, other pcs print fine to the linksys/HPDJ960.

Did you find anything to fix your problem?

by bprats

Only the Document Q260142 addresses Win2000 printer errors. The other doc was for a router redial problem.

by timmitchell

When you receive this type of error, you've got a print job stuck in the spooler. Go to c:\Winnt\System32\Spool\Printers. There should be one (or more) items in that folder; delete them all. Go to Services (Control Panel / Administrative Tools / Services) and restart the print spooler service. This should resolve your problem.

This discussion is closed to new replies.