Re: printer problems since patch Tuesday

That's the fix for now. HP is aware of this issue. I am not sure how far
they got into resolving their driver version conflict.

They way I work around this is to set all the printers that need the driver
upgrade to a driver that is not used by any other device. I add the AGFA
driver that is first in the driver list. DO NOT delete the printers just
assign the printers the AGFA driver. Delete the old driver (I have had to
kill explorer.exe to unload the UI drivers that are loaded), then install
the new drivers. If more that one driver is using the same module you may
need to perform this for multiple driver at the same time.

Set one of the printers to the new driver and open the properties. Then the
rest.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

"George" <George@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6856B9BF-76BC-489A-8406-A595D5321F23@xxxxxxxxxxxxxxxx
> We seem to ba having the same issues with newer HP printers. According to
HP
> this is a known problem and the only way around it is to uninstall and
> reinstall the printer dirvers. However, for our print server hosting over
100
> printers this is not someting I do lightly. Has anyone heard of another
fix.
>
> "David Hetherington" wrote:
>
> > Thanks for the assistance Tom, but that is not the same issue that I am
> > experiencing. I can't even pull up the printer properties page to try
and
> > run off a test ***. It errors with the following
> > "Function address 0x77fcb21d caused a protection fault.(exception code
> > 0xc0000005) Some or all property pages may not be displayed"
> >
> > Anyone know if MS is working on a fix for this error?
> >
> > PLEASE!!!!!!!
> >
> >
> >
> > "Tom Che [MSFT]" wrote:
> >
> > > Hi all,
> > >
> > > Regarding the issues between the recent patches/updates for Windows
2000
> > > and the printers, there is a latest KB article which can be your
reference:
> > >
> > > Users cannot print after you install a service pack, update rollup, or
> > > printer hotfix on a server in Windows 2000
> > > http://support.microsoft.com/kb/832219
> > >
> > > Hope this helps!
> > >
> > > Have a nice day!
> > >
> > > Sincerely,
> > > Tom Che
> > > Microsoft Online Partner Support
> > > Get Secure! - www.microsoft.com/security
> > >
> > > =====================================================
> > > When responding to posts, please "Reply to Group" via your newsreader
so
> > > that others may learn and benefit from your issue.
> > > =====================================================
> > > This posting is provided "AS IS" with no warranties, and confers no
rights.
> > >
> > >
> > > --------------------
> > > From: "Mike Koch" <mikey@xxxxxxxxxxxxxxxxx>
> > > Subject: printer problems since patch Tuesday
> > > Date: Wed, 10 Aug 2005 16:54:46 -0400
> > > Lines: 31
> > > X-Priority: 3
> > > X-MSMail-Priority: Normal
> > > X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
> > > X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
> > > X-RFC2646: Format=Flowed; Original
> > > Message-ID: <#$bs#2enFHA.2916@xxxxxxxxxxxxxxxxxxxx>
> > > Newsgroups: microsoft.public.win2000.printing
> > > NNTP-Posting-Host: 65.202.11.7
> > > Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14.phx.gbl
> > > Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.win2000.printing:5016
> > > X-Tomcat-NG: microsoft.public.win2000.printing
> > >
> > > We've been experiencing numerous printer problems ever since the
latest
> > > Microsoft patches were released and installed. It only seems to affect
> > > Windows 2000 Professional machines (our WinXP workstations do not
exhibit
> > > the problem), and it's only certain printers - the IBM/Lexmark
printers.
> > > When any Win2KPro user attempts to print to one of those printers, a
small
> > > error dialog appears (I don't have a sample, but it wasn't helpful,
> > > referring to a hex address, didn't even necessarily look
printer-related).
> > > Same dialog appears if the user attempts to view the printer property
pages
> > > (the properties dialog never comes up).
> > >
> > > This problem is growing wider as the day progresses and more users
accept
> > > the prompt to reboot to complete the patch installations. Third party
apps
> > > crash and die when they attempt to print to one of these printers.
> > > Microsoft
> > > apps are misbehaving if one of these printers is the users' default
printer.
> > >
> > > I've tried removing the printers from the workstation completely and
> > > reinstalling from the print server. I tried removing the printer and
> > > deleting the driver files manually, to make sure the ones from the
print
> > > server actually got downloaded and installed. No change. I checked on
IBM's
> > > site for a newer driver, but it appears that we're already using the
latest
> > > driver. I'm in the process of building a test machine to do some more
> > > experiments without impacting user productivity, but I'm running out
of
> > > ideas. Yes, we'd like to upgrade them all to Windows XP, but that
takes
> > > time
> > > and I need a quicker fix for this problem.
> > >
> > > Anybody have any ideas?
> > >
> > > Thanks,
> > > Mike
> > >
> > >
> > >


.

Loading