Jobs staying in queue after printing

[JH]

Hello - I just installed a networked HP Laserjet 4600 for a group of people.
Everyone uses
fully patched versions of Windows 2K. For two of the users, the print queue
doesn't clear
after printing the jobs and whenever they reboot the jobs print again. The
other users with nearly identical systems don't have a problem. For the
problem users the printer status window
says the job printed and I can remove the job manually w/o a problem. I
installed the latest print
driver from HP. These users have access to other HP printers on the network
as well (not 4600's)
and there's no problem with the jobs being removed from the queue with
those. I checked the
event logs and don't see any relevant information.

Anyone have any ideas? Is there a way to trace what's happening in the print
spooler and driver
software

Thanks in advance for any help!

Jeff H.
(e-mail address removed) (please remove dashes to send email)

 

[Mark Brown[MSFT]]

Hello - I just installed a networked HP Laserjet 4600 for a group of people.
Everyone uses
fully patched versions of Windows 2K. For two of the users, the print queue
doesn't clear
after printing the jobs and whenever they reboot the jobs print again. The
other users with nearly identical systems don't have a problem. For the
problem users the printer status window
says the job printed and I can remove the job manually w/o a problem. I
installed the latest print
driver from HP. These users have access to other HP printers on the network
as well (not 4600's)
and there's no problem with the jobs being removed from the queue with
those. I checked the
event logs and don't see any relevant information.

Anyone have any ideas? Is there a way to trace what's happening in the print
spooler and driver
software

Thanks in advance for any help!

Jeff H.
(e-mail address removed) (please remove dashes to send email)




Hi Jeff,
From what I gather there are print jobs remaining in the Queues for some
users.

Failed print jobs can be caused by a bad driver version, Heap corruption,
profiles not releasing a handle.
We can get more detailed clues as to why this maybe happening.

Actions
******
1. goto "C:\winnt\system32\spool\printers" on the print server. This should
be completely empty.

2. run "winmsd" at the "run line" to pull up the system info MMC. During a
failed print job, look in "Software environment"
then in "Jobs" and "Print". This will reviel a lot of information on the
job and purhaps why it is failing.

3. If you are using roaming profiles, this tool called UPHclean will assist
in clearing this problem up.
http://support.microsoft.com/default.aspx?scid=kb;en-us;837115





~~ Mark Brown ~~
~ Performance Support Specialist,
~ Microsoft Enterprise Platforms Support
~ This posting is provided "AS IS" with no warranties, and confers no
rights.
~ Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
~ Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

 

[Mark Brown[MSFT]]

Hello - I just installed a networked HP Laserjet 4600 for a group of people.
Everyone uses
fully patched versions of Windows 2K. For two of the users, the print queue
doesn't clear
after printing the jobs and whenever they reboot the jobs print again. The
other users with nearly identical systems don't have a problem. For the
problem users the printer status window
says the job printed and I can remove the job manually w/o a problem. I
installed the latest print
driver from HP. These users have access to other HP printers on the network
as well (not 4600's)
and there's no problem with the jobs being removed from the queue with
those. I checked the
event logs and don't see any relevant information.

Anyone have any ideas? Is there a way to trace what's happening in the print
spooler and driver
software

Thanks in advance for any help!

Jeff H.
(e-mail address removed) (please remove dashes to send email)




Jeff,

Please let me know what you have found....



~~ Mark Brown ~~
~ Performance Support Specialist,
~ Microsoft Enterprise Platforms Support
~ This posting is provided "AS IS" with no warranties, and confers no
rights.
~ Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
~ Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

 

[JH]

Mark,

Thanks for your help with this problem.

The printer spool file in C:\winnt\system32\spool\printers is NOT empty.
There are two files in there and I've noticed that for every job I send to
the
printer I'll get two more files in this folder. If I bring up the HP 4600
window
and tell it to Cancel All Jobs, the entries will disappear from the printer
queue window and the spool folder. For the other destination printers, the
spooler works ok and empties after the jobs print.

I did "winmsd" and saw the same info that double clicking on the printer
icon
gives me. It shows the job as printed but still in the queue. There are no
errors
or unusual entries posted. And we're not using Roaming Profiles.

This is a tough one and I"m not sure where else to look. I compared the
size and date of the spooler file with the one on other machines that are
working and it's the same. Of 10 or so users only two have this problem.

Best Regards,

Jeff


-- _______________________________Jeff HowardSoftware EngineerOffice of the
University RegistrarUniversity of North Carolina - Chapel
(e-mail address removed)

Hello - I just installed a networked HP Laserjet 4600 for a group of people.
Everyone uses
fully patched versions of Windows 2K. For two of the users, the print queue
doesn't clear
after printing the jobs and whenever they reboot the jobs print again. The
other users with nearly identical systems don't have a problem. For the
problem users the printer status window
says the job printed and I can remove the job manually w/o a problem. I
installed the latest print
driver from HP. These users have access to other HP printers on the network
as well (not 4600's)
and there's no problem with the jobs being removed from the queue with
those. I checked the
event logs and don't see any relevant information.

Anyone have any ideas? Is there a way to trace what's happening in the print
spooler and driver
software

Thanks in advance for any help!

Jeff H.
(e-mail address removed) (please remove dashes to send email)




Hi Jeff,
From what I gather there are print jobs remaining in the Queues for some
users.

Failed print jobs can be caused by a bad driver version, Heap corruption,
profiles not releasing a handle.
We can get more detailed clues as to why this maybe happening.

Actions
******
1. goto "C:\winnt\system32\spool\printers" on the print server. This should
be completely empty.

2. run "winmsd" at the "run line" to pull up the system info MMC. During a
failed print job, look in "Software environment"
then in "Jobs" and "Print". This will reviel a lot of information on the
job and purhaps why it is failing.

3. If you are using roaming profiles, this tool called UPHclean will assist
in clearing this problem up.
http://support.microsoft.com/default.aspx?scid=kb;en-us;837115





~~ Mark Brown ~~
~ Performance Support Specialist,
~ Microsoft Enterprise Platforms Support
~ This posting is provided "AS IS" with no warranties, and confers no
rights.
~ Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
~ Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

 

[Jim Hanke [MSFT]]

In the properties of the printer on the USERS machine, go to the Advanced
tab.

Do they have the box "Keep printed documents" checked?

 

[JH]

Jim,

Checked that pretty early on. Box is unchecked. Out of lack of anything else
to try I'm deleting all of her screen savers and unused applications and
then
will run Adaware to clean up. Thanks very much for your suggestion.

Jeff H.