Spooler service keeps stopping

I have a virtualized terminal server whose print service keeps stopping. I get the event id 1000 Source Application Error "faulting application spoolsv.exe" error message in the application log and the event id 333 source application popup "An i/o initiated by the Registry failed unrecoverably." error message in the system log.

Since this is the terminal server, I need for the print spooler to keep running and not bomb out.
MainSail2007Asked:
Who is Participating?
 
conradjonesConnect With a Mentor Commented:
restart the spooler service with the printers folder open and see if the spooler service is crashing when accessing a particular printer.

if so then it is probably down to a bad printer driver or queue
0
 
dexITCommented:
Did you try cleaning out the spool dir or registry?
If so, have you tried using the WS2K3 CD to repair/re-install the service?
0
 
MainSail2007Author Commented:
Yes, I have tried clearing out the spool folder. Sorry I did not specify that in the original post. I tried clearing out the folder, which did have files in it and restarted the spooler. The same issue occured.

The server has service pack 2 installed and does not have any APC software installed.
0
Take Control of Web Hosting For Your Clients

As a web developer or IT admin, successfully managing multiple client accounts can be challenging. In this webinar we will look at the tools provided by Media Temple and Plesk to make managing your clients’ hosting easier.

 
MainSail2007Author Commented:
Conradjones, I went through all of the printers and even though the print spooler stopped three times it was not on any particular printer. After starting the service up again I was able to access the last printer it stopped out without it stopping again on the same printer.
0
 
conradjonesCommented:
do you have many users on the terminal server?
do you have many apps on the terminal server?

can you build a clean ts vm with nothing installed to see if the spooler server crashes on that?

we use app-v for our applications, last time i had a problem with a terminal server, it took about 30mins to rebuild because all we had to do was install windows --> add/confgure ts role--> install app-v client.
0
 
MainSail2007Author Commented:
There a about 50 users on the Terminal Server and about 35 printers installed, which would be the biggest problem installing over again.

I thought of doing that, but would like to resolve the problem if I could. User profiles are also a huge. We don't use standardized desktops.
0
 
conradjonesCommented:
i was thinking just put a test vm terminal server, and see if that one crashes the printer spooler.

at least then you will know whether it is a queue or the terminal server itself

are the queues on another server or are they directly on the terminal server?
0
 
MainSail2007Author Commented:
The queues are directly on the terminal server.
0
 
conradjonesCommented:
what service pack level are you on?

just confirming 2003 server
0
 
MainSail2007Author Commented:
Worked with Microsoft on the issue. It was a bad print driver. They were only able to find it after performing a dump and analyzing it.
0
All Courses

From novice to tech pro — start learning today.