Spooler service / Spoolsv.exe crashing due to hpz3r4x6.dll
The Print Spooler service constantly crashes. Base is Server 2003 R2 SP2.
There's a HP network printer which is shared off of the server. This worked fine previously, but the spoolsv.exe process is now crashing every 5 minutes.
See attached screenshot for more information. I've updated the HP drivers to the most recent version and it's still causing a problem almost daily!
spoolsv.JPG
There's a HP network printer which is shared off of the server. This worked fine previously, but the spoolsv.exe process is now crashing every 5 minutes.
See attached screenshot for more information. I've updated the HP drivers to the most recent version and it's still causing a problem almost daily!
spoolsv.JPG
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
This is due to Virus issue.. Please try scan your system completely in safe mode. Uninstall printer dribver. Reinstall in safe mode.
mostely your problem will be solved
mostely your problem will be solved
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
hdhondt: I attempted that as part of my troubleshooting process anyway, but that's a spot-on suggestion thanks!
cdsathya: I don't mean to be rude or dismiss your suggestion, but there are no viruses on the system. They're all scanned daily and have realtime protection. Appreciate your advice though :)
Spike99: I did notice on other EE posts that people suggested it, however none of them warned about the complete removal of all drivers! - I noticed this after (for a change) reading the manual.. hah!
I actually tracked this down. It's a bit complicated, but bear with me!
The server 'DC-SVR' launches a batch script when every single user logs on, called PRINTERS.bat - Which contained some printui strings to add a few printers on logon.
One of the printers was mapped from "\\dc-svr\OfficejetPro k5400" and the other was mapped to '\\staff\OfficejetPro K5400'
It turns out there is a printer in the staff room, connected via USB (Yes, USB.. not ethernet).. to a machine that stays turned on *All the time*, and effectively acts as a posh print server.
This machine had issues with the printer connected to it, and the spooler was crashing locally. This in turn was causing the server's spooler service to crash, creating a bit of a cascading effect.
Once I had use cleanspl.exe on the 'Staff' machine, and reinstalled the printer software from scratch - Everything fell back into place and all was well! I've awarded you both some points for helping out. Nice one :-)
cdsathya: I don't mean to be rude or dismiss your suggestion, but there are no viruses on the system. They're all scanned daily and have realtime protection. Appreciate your advice though :)
Spike99: I did notice on other EE posts that people suggested it, however none of them warned about the complete removal of all drivers! - I noticed this after (for a change) reading the manual.. hah!
I actually tracked this down. It's a bit complicated, but bear with me!
The server 'DC-SVR' launches a batch script when every single user logs on, called PRINTERS.bat - Which contained some printui strings to add a few printers on logon.
One of the printers was mapped from "\\dc-svr\OfficejetPro k5400" and the other was mapped to '\\staff\OfficejetPro K5400'
It turns out there is a printer in the staff room, connected via USB (Yes, USB.. not ethernet).. to a machine that stays turned on *All the time*, and effectively acts as a posh print server.
This machine had issues with the printer connected to it, and the spooler was crashing locally. This in turn was causing the server's spooler service to crash, creating a bit of a cascading effect.
Once I had use cleanspl.exe on the 'Staff' machine, and reinstalled the printer software from scratch - Everything fell back into place and all was well! I've awarded you both some points for helping out. Nice one :-)
ASKER
Also, this was on a DOMAIN controller. I wouldn't like to install drivers in safe mode on a standard workstation let alone a server - This is bad practise, as most software installation packages do not run correctly in safe mode. (Especially MSI packages..)
Thanks for the points! :)
I'm surprised no one else warned about CLEANSPL.exe: it removes literally everything that's related to printers: printers, dirvers, ports, etc. The only time we use it is to clean out a server prior to using PrintMig to import printers and drivers from another server.
Glad you resolved the issue!
I'm surprised no one else warned about CLEANSPL.exe: it removes literally everything that's related to printers: printers, dirvers, ports, etc. The only time we use it is to clean out a server prior to using PrintMig to import printers and drivers from another server.
Glad you resolved the issue!
ASKER
'cleanspl.exe' from the 2030 Server Resource Kit.
http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&DisplayLang=en