The Print Spooler service terminated unexpectedly error

Anybody know how to fix this?

Thanks
Rockit
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7034
Date: 10/22/2004
Time: 8:56:23 PM
User: N/A
Computer: COMPUTER
Description:
The Print Spooler service terminated unexpectedly. It has done this 8 time(s).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

Delete the offending printer. Let windows redetect it. Check for any newer driver/application programme for the printer.

 

Thanks but there are no printers installed yet.

This is a fresh and complete install of Windows XP SP2.

The only thing I can come up with is to reinstall the print spooler service?

Anybody know how to do this?

Thanks
Rockit

 

Here are a couple of "Reads" that may shed some light:

http://support.microsoft.com/default.aspx?scid=kb;en-us;324757&Product=winxp

http://support.microsoft.com/default.aspx?scid=kb;en-us;324757&Product=winxp

Beyond that, it might pay to run sfc /scannow and be ready with the install CD in case it's requested.

Then you might want to try actually installing a printer in hopes that it will swamp out the error message.

Good luck.

 

Well I've tried all the suggestions so far and if I boot up with the printer turned on it starts the install process then error's out. The only error code or clue I get is the printer spooler service is not running.

If I manually start it (it's on automatic) then try and install a printer it turns itself off before I can get a printer installed.

I'll keep looking for the cure but if I don't get it soon I'll have to do a repair WinXP install

Thanks and any other idea's?

Rockit

 

Check and verify that you have the following three files and that they agree with the size, date and locations that mine are.

localspl.dll

Directory of C:\WINDOWS\ServicePackFiles\i386

08/04/2004 02:56 AM 341,504 localspl.dll
1 File(s) 341,504 bytes

Directory of C:\WINDOWS\SYSTEM32

08/04/2004 02:56 AM 341,504 localspl.dll
1 File(s) 341,504 bytes

Directory of C:\WINDOWS\SYSTEM32\dllcache

08/04/2004 02:56 AM 341,504 localspl.dll
1 File(s) 341,504 bytes

spoolss.dll

Directory of C:\WINDOWS\ServicePackFiles\i386

08/04/2004 02:56 AM 74,752 spoolss.dll
1 File(s) 74,752 bytes

Directory of C:\WINDOWS\SYSTEM32

08/04/2004 02:56 AM 74,752 spoolss.dll
1 File(s) 74,752 bytes

Directory of C:\WINDOWS\SYSTEM32\dllcache

08/04/2004 02:56 AM 74,752 spoolss.dll
1 File(s) 74,752 bytes



win32spl.dll

Directory of C:\WINDOWS\ServicePackFiles\i386

08/04/2004 02:56 AM 101,888 win32spl.dll
1 File(s) 101,888 bytes

Directory of C:\WINDOWS\SYSTEM32

08/04/2004 02:56 AM 101,888 win32spl.dll
1 File(s) 101,888 bytes

Directory of C:\WINDOWS\SYSTEM32\dllcache

08/04/2004 02:56 AM 101,888 win32spl.dll
1 File(s) 101,888 bytes

We're clutching at straws here since if you ran SFC /scannow it should have corrected any errors with these files.

 

Another straw to grab:

Check C:\WINDOWS\SYSTEM32\spool\PRINTERS and delete anything found in that folder. The theory being that a corrupt print job is in there and gumming up the works. Slim chance but possible.

Then, if the above fails, if it were me, I would empty every folder in that tree from spool on down. Can't hurt if you are facing a repair install anyway.

 

Thanks SurferDude ...
I think we got it .. It appears to be installing ok now. I did run the SFC /scannow but that didn't help?

The guilty party was spoolss.dll.

I had two files of different size on my hard drive?

I made them both the same with the size you posted and started the spooler service and clicked on add printer and it appears to be working !!

One question?

Why are some of the folders under C:\windows\system32\ blue when the rest are yellow?

Is it cause their system folders?

The one's I notice are: dllcache and conime.exe?

Hmm .. that don't look like a folder?

Is it cause they are corrupt?

At least I can print out my resume now.

Thanks Allot
Rockit

Update .. it's printing

 

They are blue because that's the way XP identifies compressed folders.

Good luck with the resume!

Edit: Now we gotta figure out what happened to fool SFC on that file. That could shake a persons confidence in how robust XP supposedly is and how it can repair itself.

 

See also this thread

Greetings,
Stray Cat