print spooler - keeps crashing - how to resolve - event id 7034 (And others)
Hi,
A client has had an issue wtih the print spooler crashing and taking out the ability to print. It never happened that often but over the last few weeks its been increasing where as today it has happened about 20 times.
Resolution is just to start it again, but I need to work out why it is happening.
Actually there are a error messages in the system event log but on example of todays is the following:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7034
Date: 26/05/2010
Time: 15:25:16
User: N/A
Computer: SERVER-1
Description:
The Print Spooler service terminated unexpectedly. It has done this 5 time(s).
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Th user action for this is to:For information that can help you identify possible causes for this error, view the WIN32_EXIT_CODE error that SCM encountered. To view the error, at the command prompt, type
sc query service name
however I do not know the actual proper service name for the print sooler (i tried print spooler and it said not recognised).
This investigaiton also borught to my attemion the numerous entries in the Application event log of 8214 Windows SharePoint Services 3. - about 30 times a day. Not sure if related but thouught I would mention it.
I really need some help on this. so any pointers welcome.
Note server is: Windows Server 2003 with Windows XP clients.
A client has had an issue wtih the print spooler crashing and taking out the ability to print. It never happened that often but over the last few weeks its been increasing where as today it has happened about 20 times.
Resolution is just to start it again, but I need to work out why it is happening.
Actually there are a error messages in the system event log but on example of todays is the following:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7034
Date: 26/05/2010
Time: 15:25:16
User: N/A
Computer: SERVER-1
Description:
The Print Spooler service terminated unexpectedly. It has done this 5 time(s).
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Th user action for this is to:For information that can help you identify possible causes for this error, view the WIN32_EXIT_CODE error that SCM encountered. To view the error, at the command prompt, type
sc query service name
however I do not know the actual proper service name for the print sooler (i tried print spooler and it said not recognised).
This investigaiton also borught to my attemion the numerous entries in the Application event log of 8214 Windows SharePoint Services 3. - about 30 times a day. Not sure if related but thouught I would mention it.
I really need some help on this. so any pointers welcome.
Note server is: Windows Server 2003 with Windows XP clients.
Hello. It is usually from a bad printer driver. Reinstall or update the printer drivers in the PC.
What is the OS of the server, and the OS of the client machine? Are they 64 or 32 bit?
ASKER
OK. Well the sc query did not reveal much as I guess at time of runing the comman the service is running OK
SERVICE_NAME: Spooler
TYPE : 110 WIN32_OWN_PROCESS (interactive)
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
So I assume that is normal.
As for other comments, re-installing the driver is no t an easy feat. I have 70 workstations and about 20 network printers. I have no idea at this point which of the PC's on the network or which printer is causing the problem. All I do know is that when it does happen, everyone cries out and when it happens 20 tmes in a day people get frustrated.
The OS is Windows Serer 2003 - 32 bit and Windows XP clients also 32 bit.
SERVICE_NAME: Spooler
TYPE : 110 WIN32_OWN_PROCESS (interactive)
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
So I assume that is normal.
As for other comments, re-installing the driver is no t an easy feat. I have 70 workstations and about 20 network printers. I have no idea at this point which of the PC's on the network or which printer is causing the problem. All I do know is that when it does happen, everyone cries out and when it happens 20 tmes in a day people get frustrated.
The OS is Windows Serer 2003 - 32 bit and Windows XP clients also 32 bit.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi Coalnine,
I did notice this option and aIso noticed it was set to first fail - restart, second fail - restart and the subsequent failures -do not restart.
I was a bit scared to change this as I was worried it would go into some loop that would drain thesystem resoucres and cause more faillures, but do you reckon it's OK to go ahead?
I did notice this option and aIso noticed it was set to first fail - restart, second fail - restart and the subsequent failures -do not restart.
I was a bit scared to change this as I was worried it would go into some loop that would drain thesystem resoucres and cause more faillures, but do you reckon it's OK to go ahead?
I usually do this on most systems that are having constant spooler failures until I track down the cause to appease the users. Printing for them may seem a bit slow at times, but it won't stop.
ASKER
This error is still present. I have got around it by putting the auto start for the printer spooler but I will carry on investigation in due course.
The next thing I would recommend is removing (by deleting the printer then going to file --> server properties--> drivers tab and deleting the drivers then restart the server).
Then, reboot the server and reinstall the drivers. Errors like this are usually a faulty driver or port. You can also try deleting the port (same way as driver except the port tab instead) at the same time as the driver to kill two birds with one stone.
Then, reboot the server and reinstall the drivers. Errors like this are usually a faulty driver or port. You can also try deleting the port (same way as driver except the port tab instead) at the same time as the driver to kill two birds with one stone.
ASKER
OK I will make time to investigate this matter further hopefully sooner. The auto restart really helps, but the issue is still apparent. I'm working through reinstalling the drivers.
sc query
to get a list of all services.
Then you can see that the printspooler is called "Spooler"
so
sc query Spooler
does the trick.