Advertisement
Advertisement
- 1. tigermatt 7,125
- 2. dariusg 6,600
- 3. henjoh09 6,150
- 4. Chris-Dent 5,100
- 5. Mestha 4,600
- 6. TechSoEasy 4,075
- 7. limjianan 4,000
- 8. Bembi 2,000
- 8. Shift-3 2,000
- 8. kadafitcd 2,000
- 8. GTPD22 2,000
- 8. Nikola_Sh 2,000
- 8. aperesc 2,000
- 8. TomGods... 2,000
- 8. orkinoks 2,000
- 8. dandmantra 2,000
- 8. martin_b... 2,000
- 8. BSonPosh 2,000
- 8. HayesJupe 2,000
- 20. MPECSInc 1,500
- 20. TapeDude 1,500
- 20. Rajith_En... 1,500
- 20. BBRazz 1,500
- 24. brent_ca... 1,200
- 25. Coronatus 1,000
- 25. lalanclu 1,000
- 25. hodgeyohn 1,000
- 25. dfxdeimos 1,000
- 25. dstewartjr 1,000
- 25. mkbean 1,000
- 25. CarlWebs... 1,000
- 25. RobWill 1,000
- 1. tigermatt 562,367
- 2. dariusg 130,648
- 3. henjoh09 94,460
- 4. bhanukir7 59,054
- 5. KCTS 56,166
- 6. LegendZM 54,362
- 7. plimpias 48,897
- 8. Netman66 44,965
- 9. Chris-Dent 44,718
- 10. andrew_... 41,696
- 11. dfxdeimos 35,967
- 12. McKnife 30,594
- 13. leew 29,071
- 14. Rajith_En... 28,066
- 15. jkarnes12 25,275
- 16. mkbean 25,160
- 17. gupnit 20,132
- 18. brent_ca... 19,552
- 19. MPECSInc 19,100
- 20. ScooterA... 18,520
- 21. limjianan 17,750
- 22. ryansoto 17,335
- 23. LauraEHu... 15,800
- 24. itsmein 15,250
- 25. BSonPosh 14,807
| 09.02.2008 at 11:36AM PDT, ID: 23696936 |
|
[x]
Attachment Details
|
||
Windows Server 2008 Terminal Server - Print Spooler crashes due to HP BiDi Component DLL's
|
[x]
The Solution Rating System
|
||
With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.
Your Input Matters If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support. Thank you! |
||
Microsoft, Windows Server, 2008, Terminal Services
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 (http://www.experts-exchan
Has anyone seen this problem before? I have been pulling my hair out over this issue for the past month.
Thanks,
Haas Computing Services
