After KB896423, three print servers stopped working

We installed all the latest updates on three different 2k/SP4 servers this
weekend (two HPs, one Dell), and all three of them stopped printing. Even
test prints sent directly from the box get one of two errors:
-Test page failed to print. Would you like to view the print trouble shooter
for assistance? Unable to create a print job.-
OR
-A StartDocPrinter call was not issued.-
(both seen here
http://support.microsoft.com/default...b;en-us;121074)

The only way we got things to work was to reinstall SP4.

Anyone else had printing issues after this update?

UlineTechs a écrit :
> Anyone else had printing issues after this update?

We have some problems too !

We have updated all the workstations this night (200 workstations) with
about 10 updates (update KB896423 was one of this) and today
workstations can not print on two printers (IBM 1222 and IBM 1332). We
have no printing ussue on other printers.

We have updated the printer drivers one the servers and have reinstalled
printers which cause issues and it was not better.

I will call the Microsoft support in fee minutes and let you know if I
have some news from them.

Regards,
Sylvain

> Anyone else had printing issues after this update?

Windows 2000 Server updated yesterday at end of day, long series of updates.
This morning, remote Terminal Services session experienced printer failure.
Test Page, same failure. In the Event Log, description is "Application Popup:
Printers Folder: There was an error found when printing the document "Test
Page" to LPT1:. Do you want to retry or cancel the job?"

The same applications running as the same user from the console print
normally. All security settings appear to be correct. Reinstalled printer
driver, no change. Downloaded and installed updated printer driver, no change.

Printer was working shortly before updates, not working after, no known
system changes other than the updates.

KB896423 was one of the installed updates. Big surprise: it's a Print
Spooler update. I don't like doing it, but I'll uninstall that update.

Same problems here too.

Windows 2000 machines cannot print to Networked Dell or Lexmark
printers after KB896423 update. We have been talking with Microsoft all
week and do not have an answer from them yet, but they are pretty
reluctant to admit that their patch is the issue. Did some testing on
my own and found that the main problem lies with the new win32spl.dll
file that the patch copies to Windows 2000 machines. Replacing this
file with the old file located in the $NtUninstallKB896423$ folder,
removing all connected printers, rebooting the machine, and then adding
the printers back fixed the problem. I didn't want to try this outside
of a test machine so on other machines having the problems we have just
uninstalled the entire patch.

I'm curious if anyone else has had better luck getting an answer from
Microsoft?

More information. Uninstalling the patch alone did not fix the problem. I see
that I might have to remove the printers and reinstall.... I'll try that.

Abd ulRahman Lomax wrote:

> More information. Uninstalling the patch alone did not fix the problem. I see
> that I might have to remove the printers and reinstall.... I'll try that.
Hi,

See if this one helps:

Users cannot print after you install a service pack or printer
hotfix on a server
http://support.microsoft.com/default...b;en-us;832219



--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx

FYI...If you have already uninstalled the patch and rebooted without
uninstalling the printers first you may need to do the following steps:
Delete Printers--Cycle Print Spooler--Reinstall Printers

What I did to get Terminal Services users printing again, after having
removed the security patch, was to delete the printer driver, reboot, and
then reinstall the driver (and I used the opportunity to download and install
the latest driver, which may or may not have had any effect). This did work.
The printer, by the way, is a Kyocera FX-1900.

But, of course, the server is now vulnerable if a Print Spooler exploit
gets through our firewall....