Search
Report Types:
Products
Updates
Logs
Bugs
Files
Encounters:
Only Reports that have Encounters
Encounters must contain resolution
Home
Products
Updates
Logs
Bugs
Files
Sign In
Create an Account
Action Links
Create a Product Report
Create a Update/Patch Report
Create a Log/Event Report
Create a Bug Report
Create a File Report
Recent Search Results
No Search results are currently available to display.
Your last search results will be displayed here for the duration of your browser session.
Latest Reports
Dell Dimension 4400
Adobe Illustrator 5
HP Access Points MSM415
Microsoft Groove 2007
Dell Vostro V13
HP Photosmart R607 BMW Special series
Dell PowerEdge M1000e
Adobe Illustrator 7
Dell Precision M2400
HP Proliant DL580 G4
...
41
42
43
44
45
...
Log Report
Print
Edit This Record
Create New
Revision
1
Template
Windows Event Log
Log Name
Application
Type
Error
Source
MsiInstaller
Event ID
10005
Average Threat Rating
Average Threat Rating Help
X
Loading...
Encounters
More Info
Related Content
Alert Me
Discuss
Add Your Encounter
Hide Encounters without Resolutions
joverland
Posts: 41
1/25/2011
Revision
1
Threat Rating:
Contains Resolution:
Ran into this on our servers. Workaround #1 from HP Support Alerts resolved this and is easy to implement:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c01682861&dimid=1001553288&dicid=alr_mar09&jumpid=em_alerts/us/mar09/all/xbu/emailsubid/mrm/mcc/loc/rbu_category/alerts
Workaround #1
The current suggested workaround for customers that wish to continue to use the latest discrete PCL 6, PCL 5, or Postscript drivers from hp.com will need to perform the following:
1.Open Notepad and save the file as hpzbdi32.msi or hpzbdi64.msi. This zero-byte file will not contain any data.
2.Navigate to the C:\WINDOWS\system32\spool\drivers\w32x86 or x64\3 directory and locate the hpzbdi32.msi or hpzbdi64.msi file. Rename the file to hpzbdi32.old or hpzbdi64.old.
3.Copy and paste the newly created zero-byte file named hpzbdi32.msi or hpzbdi64.msi into the C:\WINDOWS\system32\spool\drivers\w32x86 or x64\3 directory.
4.Verify functionality.
NOTE: Depending on configuration, it may be necessary to stop the spooler, perform the steps in the workaround, and restart the spooler once the steps have been completed.
NOTE: Please note that if the customer performs this workaround and a reinstallation of the driver is performed, the zero-byte msi file will be overwritten by the original msi file in the original driver package. All steps in the workaround would need to be performed again.
Peer Reviews (0)
Peer Review Help
X
Loading...
No reviews have been post for this Encounter
Post a Peer Review:
Copyright (c) 2011
About Us
Contact Us
Privacy
Disclaimer
FAQs