Spooler subsystem app error

Hi... I have this application/printer server with more than 75 printers
published through th AD. Yesterday the print spooler service stop working
with this message on the log on screen "Spooler subsystem app". I can't see
or install any printers. The kb from microsoft says that I need to clean up
the spooler, so all the printers and drivers will be deleted. That is an
option I can't do. Please tell me how to resolve this problem without
uninstalling all the printers. Thanks in advice.

I forgot... everytime I start the service, it goes down in seconds.

Error Logs:

Event Type: Information
Event Source: DrWatson
Event Category: None
Event ID: 4097
Date: 10/3/2006
Time: 1:57:54 PM
User: N/A
Computer: SENAPS01
Description:
The application, C:\WINDOWS\system32\spoolsv.exe, generated an application
error The error occurred on 10/03/2006 @ 13:57:54.169 The exception generated
was c0000005 at address 7C83B07D (ntdll!RtlCopyLuid)
------------------------------------------------------------------------------
Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 10/3/2006
Time: 1:58:01 PM
User: N/A
Computer: SENAPS01
Description:
Faulting application spoolsv.exe, version 5.2.3790.1830, faulting module
ntdll.dll, version 5.2.3790.1830, fault address 0x0003b07d.
------------------------------------------------------------------------------

I've been having the exact same problem on my Windows Server 2003 system with about 70 printers connected. All solutions I find to the error refer to WinXp and Vista, nothing for Server 2003. Running cleansp.exe and deleting all my printers is not an option! Were you ever able to resolve this?

If you learned to reply correctly then we may be able to help you!
I can't find out what the original problem was as this seems to be a new
topic (even though it starts with "Re:")

As I've just posted on another thread I had the problem with the Spooler
subsytem on a clean install of Vista and tried all the solutions I could
find. In the end I finally (in fact aboiut an hour ago) tired replacing the
file 'localspl.dll' in the windows system32 folder as that seemed to be
cuasin the spoolsv.exe to crash and voila all is now working. I got the
replacment file from a machine that was working OK.

Hi!

I am having the same kind of problem with my server 2003 and would be highly grateful if you tell me the solution if you have found one.

I found it, if that can help you ...
- (Windows XP) Spooler subsystem app has encountered a problem and will be closed:
Or an error message notifies you when to print the task can not be completed.

This problem is posed by the existence of third party software installed before the driver for your new printer. Restart in Safe Mode and in Windows Explorer, delete the entire contents of these two directories:

c: \ windows \ system32 \ spool \ printers and c: \ windows \ system32 \ spool \ drivers \ w32x

then in the registry, browse:

HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Print \ Environment \ Windows NT x86

Delete all the subkeys other than these: Drivers / Print Processors. Now open:

HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Print \ Monitors

Do the same as above except the following subkeys:

BJ Language Monitor / Local / Port PJL Language Monitor / Standard TCP / IP Port USB Monitor

It only remains for you only to reboot and perform a complete reinstallation of your printer.

Hello,

Thank you for the response and solution.
In the meantime i did something that got me rid from this problem. Details as follows:
1) I made a restore from Acronis True Image which was taken back in April this year.
2)After the restore, i could see when the event viewer actually brings up this error which ofcourse would be for the first time after the restore.
3)When i encountered the error, i checked the event viewer and there it was right before the service manager error.
4)It happened to be one specific printer driver update which when deleted took this problem with it.
5)I have citrix installed on this server and this problem actually was keeping my network handicapped but this was my resolution and it worked.

I never knew about this solution which led me to pray and this is what came to my mind. No doubt a pure heavenly help. Hope this helps you in your situation as well.