Windows Server 2008 Terminal Server - Print Spooler crashes due to HP BiDi Component DLL's
We are using latest version drivers, indicated as Server 2008 compatible from the HP website, for the following printers:
LaserJet 9050DN, PCL6
LaserJet 4250, PCL5e
Color LaserJet 9500, PS
Printers are hosted on a Windows Server 2003 R2 print server and are managed using PCOUNTER.
The HP BiDi Channel Components are causing the print spooler to suddenly terminate on ALL of our 2008 Terminal Servers (x86 and x64). This does not happen on any of our 2003 Terminal Servers.
To make the issue more complicated, crashes are intermittent. I've configured the print spooler to restart indefiniately when the service fails, however our Terminal Servers eventually must be rebooted due to memory corruption (and poor performance) due to the subsequent spooler crashes.
I've identified two HP DLL's are the culprits (there are application errors logged for these DLL's at the same time the print spooler crashes):
hpzpnp.dll
hpcpn5r1.dll
Below are the descriptions from the event log for each of the following DLL's. I've also attached snap shots of the event log.
Faulting application spoolsv.exe, version 6.0.6001.18000, time stamp 0x4791956c, faulting module hpcpn5r1.dll, version 0.3.1537.48, time stamp 0x47f649ae, exception code 0xc0000005, fault offset 0x00010a65, process id 0x1b7c, application start time 0x01c8fc055030d3fa.
Faulting application spoolsv.exe, version 6.0.6001.18000, time stamp 0x4791956c, faulting module hpzpnp.dll, version 0.3.1537.18, time stamp 0x478e03b2, exception code 0xc0000005, fault offset 0x00006026, process id 0xac8, application start time 0x01c8fc0b9bf57f0e.
There was a recent thread on experts-exchange regarding disabling SNMP & LPR byte counting (https://www.experts-exchange.com/questions/23680409/print-spooler-problems-on-Windows-2008-Terminal-Server-We-keep-lossing-ability-to-print-and-contantly-need-to-restart-the-spooler-service.html); I've ensured that neither of these options is enabled, however, the spooler crashes still occur. The printers are configured to use RAW protocol (so LPR byte count is disabled and cannot be configured).
Has anyone seen this problem before? I have been pulling my hair out over this issue for the past month.
Thanks,
Haas Computing Services
Snap0.jpg
Snap1.jpg
LaserJet 9050DN, PCL6
LaserJet 4250, PCL5e
Color LaserJet 9500, PS
Printers are hosted on a Windows Server 2003 R2 print server and are managed using PCOUNTER.
The HP BiDi Channel Components are causing the print spooler to suddenly terminate on ALL of our 2008 Terminal Servers (x86 and x64). This does not happen on any of our 2003 Terminal Servers.
To make the issue more complicated, crashes are intermittent. I've configured the print spooler to restart indefiniately when the service fails, however our Terminal Servers eventually must be rebooted due to memory corruption (and poor performance) due to the subsequent spooler crashes.
I've identified two HP DLL's are the culprits (there are application errors logged for these DLL's at the same time the print spooler crashes):
hpzpnp.dll
hpcpn5r1.dll
Below are the descriptions from the event log for each of the following DLL's. I've also attached snap shots of the event log.
Faulting application spoolsv.exe, version 6.0.6001.18000, time stamp 0x4791956c, faulting module hpcpn5r1.dll, version 0.3.1537.48, time stamp 0x47f649ae, exception code 0xc0000005, fault offset 0x00010a65, process id 0x1b7c, application start time 0x01c8fc055030d3fa.
Faulting application spoolsv.exe, version 6.0.6001.18000, time stamp 0x4791956c, faulting module hpzpnp.dll, version 0.3.1537.18, time stamp 0x478e03b2, exception code 0xc0000005, fault offset 0x00006026, process id 0xac8, application start time 0x01c8fc0b9bf57f0e.
There was a recent thread on experts-exchange regarding disabling SNMP & LPR byte counting (https://www.experts-exchange.com/questions/23680409/print-spooler-problems-on-Windows-2008-Terminal-Server-We-keep-lossing-ability-to-print-and-contantly-need-to-restart-the-spooler-service.html); I've ensured that neither of these options is enabled, however, the spooler crashes still occur. The printers are configured to use RAW protocol (so LPR byte count is disabled and cannot be configured).
Has anyone seen this problem before? I have been pulling my hair out over this issue for the past month.
Thanks,
Haas Computing Services
Snap0.jpg
Snap1.jpg
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
FYI: the spooler crashes occur when printers are being mapped upon user login. We use a VBS login script to map appropriate printers to users. The spooler crashes randomly when the script is in the middle of mapping printers. Printer mapping ultimately succeeds (as does printing), but the spooler crashes are requiring daily system reboots. Not acceptable for production environment! ;)
Ok... I got ya - you aren't using terminal printer redirection...
HP had a bunch of issues like this with some of their newer drivers... any way you can pull a driver from mid to late 2007? Folks reported those were more stable. Also - can you change the PCL6 and PS driver to PCL5e or 5c drivers? Those tend to be more stable as well.
HP had a bunch of issues like this with some of their newer drivers... any way you can pull a driver from mid to late 2007? Folks reported those were more stable. Also - can you change the PCL6 and PS driver to PCL5e or 5c drivers? Those tend to be more stable as well.
ASKER
HP doesn't post older drivers on their website...frustrating when their current drivers have so many issues. I did have an older version of the LJ 9050 drivers, DriverVer=02/13/2007,61.06
Hmmm well in the mean you could uninstall the drivers and switch them to HP Laserjet 4 or 4000 builtin drivers... since those ship w/ windows, those are about as generic as they come. The only catch is the 9500c... I think you can use one of the 4xxx series color printers - they are fairly generic. They should all be included with windows.
It isn't ideal, but it should eliminate the driver issue.
It isn't ideal, but it should eliminate the driver issue.
You may want to check out the ScrewDrivers pack from Tricerat. They solved a lot of our printing stability problems.
http://www.tricerat.com/screwdrivers
http://www.tricerat.com/screwdrivers
Object on the grounds that all Tagclts did was re-itterate my first suggestion, namely TriCerat's ScrewDrivers program.
ASKER
Apologies to the administrators for abandoning this question.
3rd party solutions such as screwdrivers and simplifyprinting were not options for us.
We have found a working solution to the problem. Please see the HP Community Forum for solution:
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1259636&admit=109447626+1227226906797+28353475
Administrators:
If it's not too late to return any points granted for this question I am requesting it, I would like to request it; I have answered my own question thru support cases with HP and Microsoft Premier (solutions published in link provided above).
Thanks,
Haas Computing Services
3rd party solutions such as screwdrivers and simplifyprinting were not options for us.
We have found a working solution to the problem. Please see the HP Community Forum for solution:
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1259636&admit=109447626+1227226906797+28353475
Administrators:
If it's not too late to return any points granted for this question I am requesting it, I would like to request it; I have answered my own question thru support cases with HP and Microsoft Premier (solutions published in link provided above).
Thanks,
Haas Computing Services
ASKER
These are network printers that are being mapped on the Terminal Server. There are no locally installed printers on any 2008 Terminal Servers. Thus, drivers are being centrally stored and delivered from the 2003 R2 Print Server. Also, as I said, the HP website states that these versions are 2008 compatible.