Link to home
Start Free TrialLog in
Avatar of ravenrx7
ravenrx7

asked on

2008 Print Server Crashing Spooler

Over the summer i installed a 2008 printer server with about 40 printers. Most of our employees have returned this week and all of a sudden the print server is crashing. I've found multiple event logs like the one below. how can i find out what printer is causing this?

Faulting application name: spoolsv.exe, version: 6.1.7601.17514, time stamp: 0x4ce7b4e7
Faulting module name: wsdapi.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ca31
Exception code: 0xc0000005
Fault offset: 0x000000000006ad4a
Faulting process id: 0x35c
Faulting application start time: 0x01cd7aeb3392c2c1
Faulting application path: C:\Windows\System32\spoolsv.exe
Faulting module path: C:\Windows\System32\wsdapi.dll
Report Id: 19496a63-e6e1-11e1-a2da-00155d042e08
Avatar of Shane McKeown
Shane McKeown
Flag of Ireland image

So the spooler isn't restarting I assume? You've tried to restart it yes?

Go into the following folder and check if there are contents, if so delete the contents

C:\Windows\System32\spool\printers\

Then restart the service

As for finding out what is causing it, i've seen certain documents(sometimes pdf) causing a spooler to crash, but its not that easy to find, you'd have to watch the server as documents are printed to locate the issue
Avatar of ravenrx7
ravenrx7

ASKER

It was stopped and kept stopping but I went in to the services and config to restart will stopped , its a driver issue not files
i did check C:\Windows\System32\spool\PRINTERS

and I there a tons of files in there.
Right, so those files are the spooled files from the users
If spooler service will not stay running, you need to clear those files and restart service

But locating your issue file is going to be hard, since there's no way(that I know of) to match the spooled files to the actual files printed
any way to just locate what printer it is? you're still thinking its a file issue right? not a driver issue?
In the cases I've seen on my client networks its file related yes, never been driver related...not saying it isn't driver related in your case of course...

Reason I know this is one of our clients uses a piece of software called Papercut(www.papercut.com), now on that package there is a log of every document printed...and in the cases where the spooler crashed I could backtrace to the exact document that was printed prior to the spooler crash...so it made life easy in those instances...

Not aware of the default windows print management software having that same functionality though...
Oh there is the Event log of course...

When you print a document it logs in the Application log in Event viewer - so soon as you know the spooler stops/crashes just check the app log to see last document printed...
ASKER CERTIFIED SOLUTION
Avatar of hdhondt
hdhondt
Flag of Australia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I'm in agreement with hdhon
Just to add, even if the printer supports WSD printing, it often needs to be enabled on the printer before it will work. Most of our MFDs, for example, ship with it disabled by default.