Print jobs not deleting -- then printing again when computer started

  • Thread starter Thread starter Frank
  • Start date Start date
F

Frank

I have a Windows 2000 SP4 workstation that quit deleting it's print
jobs yesterday. They stay in the queue with a "Printed" status. Then
they print again when the first user logs in after a restart. Just
logging out and back in doesn't reprint it; the computer has to be
restarted for them to reprint.

The computer is a Win2000 SP4 machine printing to an HP1200 on an HP
JetDirect using TCP/IP. It also prints to an HP4000 network printer
with TCP/IP, and those jobs delete fine. Only the HP1200 gives me
problems.

I've installed the latest driver, deleted and reinstalled the printer,
and made sure the "Keep printed documents" is not checked in
properties. I've checked the box and unchecked it to try to reset
things.

No luck. Any other ideas would be appreciated.
 
Try Manually deleting the files from the spool folder.
And re-print after that. Also, since it prints and purges
jobs fine on the network printer, permissions should not
be a problem.

Spool folder is usually under c:\winnt\system32
\spool\PRINTERS unless u have changed the defaults.
 
KQ said:
Try Manually deleting the files from the spool folder.
And re-print after that. Also, since it prints and purges
jobs fine on the network printer, permissions should not
be a problem.

Spool folder is usually under c:\winnt\system32
\spool\PRINTERS unless u have changed the defaults.
Click to expand...

Thanks for the suggestion. I went over for a while this morning and
did erase the files from the folder, but it doesn't stop new print
jobs from staying. I marked the "Keep printed documents" checkbox,
and of course it kept them, but they don't print on reboot. I then
unmarked it again, and it didn't reset. For now, I've got it checked
so they don't print at startup and put a shortcut to the printer on
her desktop so she can more easily delete the jobs.
 
Go figure. Grasping at straws, I turned off "Enable Bidirectional
Communication." The problem went away. Thanks for the suggestions.
 
Back
Top