printer problems since patch Tuesday

[Mike Koch]

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

 

[Tom Che [MSFT]]

Hi Mike,

Thanks for your posting.

From your post, my understanding of this issue is: You have been
experiencing numerous printer problems ever since the latest patches were
released and installed for Windows 2000 Professional. If this is not
correct, please feel free to let me know.

Based on your detailed description, I guess the current driver for
IBM/Lexmark printers may be not compatible with latest patches for Windows
2000 Pro.

To confirm this root cause, a test machine is a wonderful idea. I think
the first thing is that we should find out which patches are the root
cause. Could you please let me know which patches were installed as you
mentioned before this issue?

Then, we may try to uninstall the probable patches and then test this
issue. If the issue disappears just after uninstalling patches, we may
know that the patches are the root cause indeed. I can perform more
research according the detailed patches.

On the other hand, if certain patches are the root cause, it might be
better if you also contact the printer vendor. They may confirm this issue
further, and provide a newer and compatible driver for the latest patches.

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" <[email protected]>
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#[email protected]>
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

 

[Fred Yarbrough]

Printer problems here too after WSUS patch. Only our Windows 2000 Pro
machines are seeing it and it is with Dell 5100 and 5300 printers.


Fred

 

[Tom Che [MSFT]]

Hi Fred,

Thanks for your feedback.

We are researching on this issue.

Have a nice weekend!

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: "Fred Yarbrough" <[email protected]>
References: <#$bs#[email protected]>
<[email protected]>
Subject: Re: printer problems since patch Tuesday
Date: Thu, 11 Aug 2005 15:38:27 -0500
Lines: 110
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1506
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Message-ID: <[email protected]>
Newsgroups: microsoft.public.win2000.printing
NNTP-Posting-Host: 140.165.11.163
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.win2000.printing:5031
X-Tomcat-NG: microsoft.public.win2000.printing

Printer problems here too after WSUS patch. Only our Windows 2000 Pro
machines are seeing it and it is with Dell 5100 and 5300 printers.


Fred

 

[Fred Yarbrough]

Found the fix.

Simply remove the following Microsoft Update and reboot and things are good
to go.

Update Rollup 1 for Windows 2000 Service Pack 4 (KB891861)



Thanks,
Fred

 

[dmtopas-2]

We have the same problems with Lexmark Printers. No problems after
patchinstallation, but once a new network printer is connected
applications starts to crash. Workaround was uninstall of 896423 patch
and again connect a lexmark printer. Call to lexmark is still open ...

D. M.

 

[Guest]

Tom,
I am also experiencing this issue after the latest round of patches. The
error, "Function address 0x77fcb21d caused a protection fault.(exception code
0xc0000005) Some or all property pages may not be displayed." shows up when
we try to bring up the printer properties page on a Win 2k machine that is
connected to a shared printer on another machine, server or workstation. If
we try to print something from the client machine, the program crashes. I've
installed the latest drivers for my printers but have yet to contact Lexmark
to see if this is a driver issue or something gone wrong in the windows patch.

I'm hoping that Microsoft is working on a fix for this, as i don't intend on
removing the Windows 2000 Rollup patch on any of my machines.

Thanks for your assistance,

David Hetherington

 

[beagle07]

Having the same problem here. Limited to Lexmark T630, T632, and Dell
M5200 Printers. Uninstalling the 896423 patch worked for us but my
concern is the vulnerability that is left in the Print Spooler by not
having this patch. We have a call open with Microsoft, but they do not
have a fix as of yet so that we can install the patch back onto Windows
2000 Pro machines. From a test machine I found that the problem file in
the patch is the new version of the win32spl.dll file. Replacing this
file with the old version found in the $NtUninstallKB896423$ folder
will also fix the problem, but it may also undo the fix for the
vulnerability.

I would love to know if anyone has gotten an answer from Microsoft,
Lexmark, or anyone else on this issue?

 

[Tom Che [MSFT]]

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" <[email protected]>
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#[email protected]>
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

 

[Guest]

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 sheet. 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!!!!!!!

 

[beagle07]

David,
We have had a call open with MS for a week and finally today they
admitted that it did look like a bug in the patch KB896423 (MS05-043)
and they would hopefully have a fix for us tomorrow. I will keep you
updated on what I hear from MS.

Regards,
Jeff

 

[deniseba]

I'm getting mix signal here and would like to get some clarification.
Which patch is the cause of the problem, 896423 or 832219? I got th
same problem on Prof. machines when we installed the MSFT updates o
the W2K print server last night.

The W2k Prof. machines did not get the updates but they do experienc
the problem only with IBM Info printers. I'm reluctant to roll out th
SUS updates on all desktops unless MSFT has a fix for the bug. Is thi
only happening on servers with Tuesday patches? What happen if th
patch is only installed on prof. desktops but not on w2k print server?
Same issue? Are we not to load either of these two patches on w2
server and w2k prof PCs? Please advise. Thanks.

*David,
We have had a call open with MS for a week and finally today they
admitted that it did look like a bug in the patch KB89642
(MS05-043)
and they would hopefully have a fix for us tomorrow. I will keep you
updated on what I hear from MS.

Regards,
Jeff

-
deniseb

 

[Alan Morris]

this is normally caused by the driver. Does this happen when you install a
printer which uses a driver we shipped with the OS?

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

 

[Guest]

The Win 2000 Roll Up patch is the update that i'm having the problems with,
and it seems to affect the client machines, ie the patch is on a win 2k box
printing to an xp machine and things don't work, i don't know the full affect
of having a patched win 2k printt server with xp client or unpatched 2k boxes
printing to it. All i know is it is causing headaches.

 

[Guest]

There is a win 2000 Roll Up patch version 2 that has was released by
microsoft sept 13th. I'm going to try it and see if it corrects my printing
issue, i will report back.

 

[Guest]

Well version 2 still has the issue. We have found a work around though,
installing IP print servers on the printers. We don't seem to have the issue
with IP print servers connected to the printers. That is the scoop. I will
update when more info is available.

 

[Smartie]

Any other ideas to work around this problem apart from using IP addressing?
I have the same problem with installing the driver for a Lexmark E232 on LPT1 across the Win2000 based network.

 

[Smartie]

Printer problem fixed but a new one pop up!

Uninstalling the "Update Rollup 1 for Windows 2000 Service Pack 4 (KB891861)" fixed the printer problem.

However, it generated another problem. Now there is Microsoft Internet Explorer error popping up when I openned My computer, My Network Places, Control Panel,.... etc. --- essentially everywhere.

The error window says: An error has occurred in this dialog.
Error: 30
Unspecified error.
<<OK>>

Behind this window is another error window called "Internet Explorer Script Error"
The message is "An error has occurred in the script on this page". Do you wnat to continue running script?"

Any ideas to remove these error windows?

 

[Guest]

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.

 

[Guest]

If tried the version 2 of the roll up patch, there was no difference in the
result. Still receiving the error. I am starting to wonder if it is a
printer driver issue, something that doesn't want to play nice with the MS
patch.