vourneenward
asked on
2003 Server Print spooler crashed
The print spooler has crashed on my 2003 Server Service Pack 1, Anyone any ideas what caused this? How I can prevent it?
There are approx 60 printers on the server.
Spool directory is on d:\ with about 1.14 GB of free space.
Details:
event ID 1000
source Application
Windows 2003 Server Service Pack 1
Faulting application spoolsv.exe version 5.2.3790.1830 faulting module msvcrt.dll, version 7.0.3790.1830, fault address 0x0001c4ba
There are approx 60 printers on the server.
Spool directory is on d:\ with about 1.14 GB of free space.
Details:
event ID 1000
source Application
Windows 2003 Server Service Pack 1
Faulting application spoolsv.exe version 5.2.3790.1830 faulting module msvcrt.dll, version 7.0.3790.1830, fault address 0x0001c4ba
Are you using Terminal Services on that server? You could have a 3rd party prtiner that is crashing it.
You can also try Cleanspl.exe from http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&DisplayLang=en
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I realize this is not an answer to your question... however, in the mean time you may want to consider modifying the behavior of that service.
start -> run ->services.msc
double click the spooler service
recovery tab
first failure (and maybe second as well) set to restart.
start -> run ->services.msc
double click the spooler service
recovery tab
first failure (and maybe second as well) set to restart.
Left field...any particular reason you are still on SP1? There are a heap of updates including to spooler that have been released since then. I would recommend SP2 unless there is something in particular holding you back.
Print spooler crashes are usually caused by driver issues...has a new pritner been installed not long before this started occuring, or a new driver?
Print spooler crashes are usually caused by driver issues...has a new pritner been installed not long before this started occuring, or a new driver?