Printer Spool cache won't clear

[Fran]

I have a user who is one of three users for our MICR check printer (a
HP Laserjet 2200D) On her system (ONLY) when she prints checks the
spool files are not removed by the printer driver. All the other
printers she uses clean up after themselves but NOT this one.

I have tried uninstalling and reinstalling the printer driver but that
doesn't seem to fix the problem and I made sure that the KEEP
DOCUMENTS option in the printer setup is NOT checked.

What else can I check to fix this? Right now I have to manually delete
these everytime she prints checks otherwise it reprints all the old
checks!

Thanks for any insight(s)

-Fran-

 

[Ollie]

Hmm...

Open up the printer-queue for that printer (double-click the printer), and
watch the status of the print job during the print session. It should start
as "Spooling", then "Spooling - Printing", then "Printing", then "Deleting -
Printing", and then the print job should disappear, as should the spool
file.

Do you have the PRNCNFG.VBS script on your system? Use it on the problem
system and on the computers without a problem, and compare the output., like
so:

C:> cscript c:\windows\system32\prncnfg.vbs -p "printer name" -g

There are other printer-related .VBS scripts, one of which PRNJOBS.VBS, lets
you cancel jobs from the command-line. As a workaround, if you do
check-runs only once a day, you may be able to set it up to run this script
at midnight to delete any outstanding jobs.

Other things to check: does this problem happen on this system when only
this login-account uses the printer? Or only non-administrator
login-accounts? Or all accounts, including Administrator? (compare the
Security Permissions for this user against other users, or other users on
different machines).

When logged-in as this account, can you CD to the spool directory and create
and delete files?

If the other machines have the same version of Windows, compare the actual
driver files on the problem system against the driver files on a system that
works properly. (Maybe the uninstall / reinstall is not overwriting an
existing file.)

Select "Print directly to the printer" and bypass the spooling altogether.
(This is actually a "good idea" for security purposes -- no reason to leave
important information like who gets paid how much in a spool file that can
be snooped -- what is the likelihood that someone has jiggered the system
for exactly this purpose?)

Does this problem occur only when printing checks via whatever application
is doing the printing? Or, do all print jobs never get removed from the
spooler directory? (Does the app need reinstalling, not the printer
drivers?)

 

[Ivan Takillya]

In case you did not see the message in this group dated 03/07/200 from
Grant, replied to by Alan Morris(MSFT), this same problem was and reported
fixed:

I have the EXACT same problem here. The HP2200D that we use for checks
keeps the spooled jobs on the workstation. I unchecked the
"BiDirectional support" and that fixed our problem. Thanks!

Uncheck Bidirectional in the Printer Properties, Ports tab. Pickup the
latest driver for the 5100, HP may have fixed this for this device. I
don't think they will address this issue on the 2200

,

 

[Alan Morris\(MSFT\)]

HP gave me the driver fix for this but the only one they included was the
4500 driver. There may be an update for this problem with other drivers but
the impression I got was they were only fixing this moving forward, but that
was just my impression.

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

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Fran]

I have two users that are connected to this printer and only one of
them has the persistent spooled file problem. I looked at the bi-di
settings on the one that was NOT having the problems...sure enough it
was not enabled and the printer WITH the problem WAS enabled. I turned
it off and that fixed the persistence!

FINALLY we got this fixed. Thanks everyone for your help!

-Fran-