Selecting Printer Properties triggers protection fault

If this happens only when doing in IE , try repairing or reinstalling IE

Repair IE :
-----------

Start > Run rundll32 setupwbv.dll,IE6Maintenance "C:\Program Files\Internet Explorer\Setup\SETUP.EXE" /g

or

Start > Run rundll32.exe setupapi,InstallHinfSection DefaultInstall 132 C:\windows\inf\ie.inf

Reinstall IE:
-------------

Description of the Internet Explorer Repair Tool
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q194/1/77.asp&NoWebContent=1

How to Reinstall or Repair Internet Explorer and Outlook Express in Windows XP
http://support.microsoft.com/?kbid=318378

or

Repair Internet Explorer 6
http://www.theeldergeek.com/repair_ie6.htm

How to Uninstall Internet Explorer 6
http://support.microsoft.com/?kbid=293907

Sunray

Sunray:

I have tried repairing IE6 and reinstalling IE6 but the problem persists.
I can print locally but cannot open Printer Properties nor print from IE6.
Same problem on two systems. Deleting Printer and reinstalling it has
not fixed the problem either.

regards and thanks

Danjava

Reinstall your Printer Software.  It's possible that one of the .library files that display the print dialogue is corrupt or missing.

I had a similiar problem.  I'm have multiple Win2k workstations and a hp lj4050.  I get the GPF message when I view printer properties and print with IE.  I had one workstation that is working and I copied the spool directory inside system32 over to the one with the GPF.  What I found out was a DLL file was either corrupted or mismatched version.  When I was trying to determine the problem I reinstalled the drivers a couple times too, but that didn't help.  But in your case since you don't have a computer that is printing correctly, I suggest you make a copy of the spool directory in another location for backup purpose.  Restarte the computer to free any files in memory.  Then delete the contents inside the spool directory.  You can test to see if it is working.  If it isn't working, try to reinstall the printer drivers.  Let me know how it goes.

Lenney

Same issue for us, but on a Win2K print server.  Our solution was to delete the printer, delete the port, re-add the port and printer.

I had the same problem just after a major W2K-Update (SP4+crit+driver updates). My W2K workstation showed the same Protection fault in IE 6, and the properties of my networked HP-2200 showed an error in coming up. Printing from the server and my other W2K (not updated) did not show the problem.
Like Lenney97 I checked the spool directory, and jus copied the older (2002) files: hpbf322e.dll, hpbf322g.dll and hpbf322i.pmd from the working workstaion to the updated computer, and the problem seams to be over. It seems to be a DLL problem.
The only other file in my updated computer which is not on the other workstation is a hpbf322e.gid hidden file from some time ago, but I have not touched this one.

Boy

I am having the same problem on my network. I have a Small Business Server 2003 R2 and several Windows XP SP2 clients. Whenever they attempt to access the properties of one of my HP LJ1320N Printers (through a shared printer spool on my server) they get a GPF. I am using the PCl6 drivers, but I think I am going back to PCL5.

Jase

Jase

The original question here was asked way back in December 2003.  The last comment added to the question was in April 2004.  The question has been closed for a long time.

Well, I am a new user to this service and I still can't find a reasonable solution to my issue which is the same one listed here way back in Dec 2003.

To be honest, what does it matter if this problem first raised it's head back in 1969? If I am having the same problem in 2008 and the solutions presented don't work, wouldn't it be a valuable resource for others having this problem (and others are having this problem--I've discussed it on other boards) if someone knew or found out the answer?

I'm glad to see you have a lot of points and all and I think that this service is pretty cool. The problem I have with it is that folks are more interested in getting points and closing topics than providing help.

I should've opened a new question so you could get your points! But as it turns out, I think my question is going to be answered by another forum where the only reward they get is knowing that they helped someone out a fix.--no points, no social status, just help!

jase

jase

Hmmm.

>>> "I should've opened a new question so you could get your points!" <<<

No, you should have asked a new question so that the status was reflected as a "Question Awaiting An Answer", and would therefore be seen by experts.  

When a question awaiting answers is superseded by new ones, it slides further and further down the list until only cleanup volunteers or those who have been actively contributing tend to see it.  Once it is PAQ'd, it dies a death until someone finds it again while searching for solutions.

When a question is closed, it is assigned the PAQ status (Previously Answered Question).  A PAQ'd question will be found in a search of Experts-Exchange and the "View Solution" button should serve as a quick link to the information people may need in a hurry.

I am well aware that you are a new user, which is the reason why I took a moment to inform you that you would be flogging a dead horse by reopening a long-expired question to add a comment which in itself did not provide any updates of useful information.

I am sorry that you feel the need for sarcasm and subtle insults.  Neither was called for or deserved.