Results 1 to 7 of 7

Thread: How to cancel printing or to delete a print job that is stuck in the print queue in Windows XP

  1. #1
    Alan Morris [MSFT] Guest

    How to cancel printing or to delete a print job that is stuck in the print queue in Windows XP

    http://support.microsoft.com/kb/946737

    the group that wrote this is pretty proud. Most of you will just start at
    method 4 since you already performed the first 3 methods.


    I'll take a minute and explain why a job gets stuck. Uninterested parties
    just follow the link.

    Jobs get a reference count associated with them from the spooler and the
    driver components (print processors and language monitor primarily). When a
    reference gets incremented without a decrement, the job will still have a
    reference and the spooler will not delete the job until the component which
    incremented the count performs the decrement function. If the decrement
    function never arrives or takes a long time from the function, the job sits
    in the queue in a deleting state while the spooler waits for the reference
    count to reach 0.

    Yes I know, you want to just delete the dang job, you don't care that some
    process out there is supposed to manipulate the job to signal the spooler
    that it's done and ready for deletion.



    --
    Alan Morris
    Windows Printing Team
    Search the Microsoft Knowledge Base here:
    http://support.microsoft.com/search/?adv=1

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



  2. #2
    soscc Guest

    RE: How to cancel printing or to delete a print job that is stuck in t

    i followed the instructions in the kb, and the jobs are still in the queue.
    checking the folder before running the script didn't show any of the files
    referred to in the script. the printer is attached to a linux sme pc via
    samba. the print jobs don't show up on that system either.

    i can't delete the printer when there are jobs queued, so that isn't an
    option.

    when trying to delete the job from within the print queue window i get
    either an error processing command or access denied. looking up either of
    these in the support database brings up all kinds of things that aren't
    related to printing.

    any other ideas?
    --
    a few miles from nowhere...


    "Alan Morris [MSFT]" wrote:

    > http://support.microsoft.com/kb/946737
    >
    > the group that wrote this is pretty proud. Most of you will just start at
    > method 4 since you already performed the first 3 methods.
    >
    >
    > I'll take a minute and explain why a job gets stuck. Uninterested parties
    > just follow the link.
    >
    > Jobs get a reference count associated with them from the spooler and the
    > driver components (print processors and language monitor primarily). When a
    > reference gets incremented without a decrement, the job will still have a
    > reference and the spooler will not delete the job until the component which
    > incremented the count performs the decrement function. If the decrement
    > function never arrives or takes a long time from the function, the job sits
    > in the queue in a deleting state while the spooler waits for the reference
    > count to reach 0.
    >
    > Yes I know, you want to just delete the dang job, you don't care that some
    > process out there is supposed to manipulate the job to signal the spooler
    > that it's done and ready for deletion.
    >
    >
    >
    > --
    > Alan Morris
    > Windows Printing Team
    > Search the Microsoft Knowledge Base here:
    > http://support.microsoft.com/search/?adv=1
    >
    > This posting is provided "AS IS" with no warranties, and confers no rights.
    >
    >
    >


  3. #3
    Alan Morris [MSFT] Guest

    Re: How to cancel printing or to delete a print job that is stuck in t

    The instructions are for canceling jobs for a local printer. I do not know
    where linux stores the print files

    --
    Alan Morris
    Windows Printing Team
    Search the Microsoft Knowledge Base here:
    http://support.microsoft.com/search/?adv=1

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

    "soscc" <soscc@discussions.microsoft.com> wrote in message
    news:1ED6ECA6-81FB-49FD-9752-C5122C607C66@microsoft.com...
    >i followed the instructions in the kb, and the jobs are still in the queue.
    > checking the folder before running the script didn't show any of the files
    > referred to in the script. the printer is attached to a linux sme pc via
    > samba. the print jobs don't show up on that system either.
    >
    > i can't delete the printer when there are jobs queued, so that isn't an
    > option.
    >
    > when trying to delete the job from within the print queue window i get
    > either an error processing command or access denied. looking up either of
    > these in the support database brings up all kinds of things that aren't
    > related to printing.
    >
    > any other ideas?
    > --
    > a few miles from nowhere...
    >
    >
    > "Alan Morris [MSFT]" wrote:
    >
    >> http://support.microsoft.com/kb/946737
    >>
    >> the group that wrote this is pretty proud. Most of you will just start
    >> at
    >> method 4 since you already performed the first 3 methods.
    >>
    >>
    >> I'll take a minute and explain why a job gets stuck. Uninterested
    >> parties
    >> just follow the link.
    >>
    >> Jobs get a reference count associated with them from the spooler and the
    >> driver components (print processors and language monitor primarily).
    >> When a
    >> reference gets incremented without a decrement, the job will still have a
    >> reference and the spooler will not delete the job until the component
    >> which
    >> incremented the count performs the decrement function. If the decrement
    >> function never arrives or takes a long time from the function, the job
    >> sits
    >> in the queue in a deleting state while the spooler waits for the
    >> reference
    >> count to reach 0.
    >>
    >> Yes I know, you want to just delete the dang job, you don't care that
    >> some
    >> process out there is supposed to manipulate the job to signal the spooler
    >> that it's done and ready for deletion.
    >>
    >>
    >>
    >> --
    >> Alan Morris
    >> Windows Printing Team
    >> Search the Microsoft Knowledge Base here:
    >> http://support.microsoft.com/search/?adv=1
    >>
    >> This posting is provided "AS IS" with no warranties, and confers no
    >> rights.
    >>
    >>
    >>




  4. #4
    soscc Guest

    Re: How to cancel printing or to delete a print job that is stuck

    the print jobs aren't on the linux pc. i have another xp pc that uses the
    same printer and those jobs don't show up in it's queue. it seems to be on
    just this computer.

    --
    a few miles from nowhere...


    "Alan Morris [MSFT]" wrote:

    > The instructions are for canceling jobs for a local printer. I do not know
    > where linux stores the print files
    >
    > --
    > Alan Morris
    > Windows Printing Team
    > Search the Microsoft Knowledge Base here:
    > http://support.microsoft.com/search/?adv=1
    >
    > This posting is provided "AS IS" with no warranties, and confers no rights.
    >
    > "soscc" <soscc@discussions.microsoft.com> wrote in message
    > news:1ED6ECA6-81FB-49FD-9752-C5122C607C66@microsoft.com...
    > >i followed the instructions in the kb, and the jobs are still in the queue.
    > > checking the folder before running the script didn't show any of the files
    > > referred to in the script. the printer is attached to a linux sme pc via
    > > samba. the print jobs don't show up on that system either.
    > >
    > > i can't delete the printer when there are jobs queued, so that isn't an
    > > option.
    > >
    > > when trying to delete the job from within the print queue window i get
    > > either an error processing command or access denied. looking up either of
    > > these in the support database brings up all kinds of things that aren't
    > > related to printing.
    > >
    > > any other ideas?
    > > --
    > > a few miles from nowhere...
    > >
    > >
    > > "Alan Morris [MSFT]" wrote:
    > >
    > >> http://support.microsoft.com/kb/946737
    > >>
    > >> the group that wrote this is pretty proud. Most of you will just start
    > >> at
    > >> method 4 since you already performed the first 3 methods.
    > >>
    > >>
    > >> I'll take a minute and explain why a job gets stuck. Uninterested
    > >> parties
    > >> just follow the link.
    > >>
    > >> Jobs get a reference count associated with them from the spooler and the
    > >> driver components (print processors and language monitor primarily).
    > >> When a
    > >> reference gets incremented without a decrement, the job will still have a
    > >> reference and the spooler will not delete the job until the component
    > >> which
    > >> incremented the count performs the decrement function. If the decrement
    > >> function never arrives or takes a long time from the function, the job
    > >> sits
    > >> in the queue in a deleting state while the spooler waits for the
    > >> reference
    > >> count to reach 0.
    > >>
    > >> Yes I know, you want to just delete the dang job, you don't care that
    > >> some
    > >> process out there is supposed to manipulate the job to signal the spooler
    > >> that it's done and ready for deletion.
    > >>
    > >>
    > >>
    > >> --
    > >> Alan Morris
    > >> Windows Printing Team
    > >> Search the Microsoft Knowledge Base here:
    > >> http://support.microsoft.com/search/?adv=1
    > >>
    > >> This posting is provided "AS IS" with no warranties, and confers no
    > >> rights.
    > >>
    > >>
    > >>

    >
    >
    >


  5. #5
    soscc Guest

    Re: How to cancel printing or to delete a print job that is stuck

    any idea why the jobs just show up on 1 pc of the 2 that access the same
    printer that is on the linux system? is there another place on the pc where
    the jobs might be queue'd? a registry entry perhaps?

    --
    a few miles from nowhere...


    "soscc" wrote:

    > the print jobs aren't on the linux pc. i have another xp pc that uses the
    > same printer and those jobs don't show up in it's queue. it seems to be on
    > just this computer.
    >
    > --
    > a few miles from nowhere...
    >
    >
    > "Alan Morris [MSFT]" wrote:
    >
    > > The instructions are for canceling jobs for a local printer. I do not know
    > > where linux stores the print files
    > >
    > > --
    > > Alan Morris
    > > Windows Printing Team
    > > Search the Microsoft Knowledge Base here:
    > > http://support.microsoft.com/search/?adv=1
    > >
    > > This posting is provided "AS IS" with no warranties, and confers no rights.
    > >
    > > "soscc" <soscc@discussions.microsoft.com> wrote in message
    > > news:1ED6ECA6-81FB-49FD-9752-C5122C607C66@microsoft.com...
    > > >i followed the instructions in the kb, and the jobs are still in the queue.
    > > > checking the folder before running the script didn't show any of the files
    > > > referred to in the script. the printer is attached to a linux sme pc via
    > > > samba. the print jobs don't show up on that system either.
    > > >
    > > > i can't delete the printer when there are jobs queued, so that isn't an
    > > > option.
    > > >
    > > > when trying to delete the job from within the print queue window i get
    > > > either an error processing command or access denied. looking up either of
    > > > these in the support database brings up all kinds of things that aren't
    > > > related to printing.
    > > >
    > > > any other ideas?
    > > > --
    > > > a few miles from nowhere...
    > > >
    > > >
    > > > "Alan Morris [MSFT]" wrote:
    > > >
    > > >> http://support.microsoft.com/kb/946737
    > > >>
    > > >> the group that wrote this is pretty proud. Most of you will just start
    > > >> at
    > > >> method 4 since you already performed the first 3 methods.
    > > >>
    > > >>
    > > >> I'll take a minute and explain why a job gets stuck. Uninterested
    > > >> parties
    > > >> just follow the link.
    > > >>
    > > >> Jobs get a reference count associated with them from the spooler and the
    > > >> driver components (print processors and language monitor primarily).
    > > >> When a
    > > >> reference gets incremented without a decrement, the job will still have a
    > > >> reference and the spooler will not delete the job until the component
    > > >> which
    > > >> incremented the count performs the decrement function. If the decrement
    > > >> function never arrives or takes a long time from the function, the job
    > > >> sits
    > > >> in the queue in a deleting state while the spooler waits for the
    > > >> reference
    > > >> count to reach 0.
    > > >>
    > > >> Yes I know, you want to just delete the dang job, you don't care that
    > > >> some
    > > >> process out there is supposed to manipulate the job to signal the spooler
    > > >> that it's done and ready for deletion.
    > > >>
    > > >>
    > > >>
    > > >> --
    > > >> Alan Morris
    > > >> Windows Printing Team
    > > >> Search the Microsoft Knowledge Base here:
    > > >> http://support.microsoft.com/search/?adv=1
    > > >>
    > > >> This posting is provided "AS IS" with no warranties, and confers no
    > > >> rights.
    > > >>
    > > >>
    > > >>

    > >
    > >
    > >


  6. #6
    Shawnk Guest

    RE: How to cancel printing or to delete a print job that is stuck in t

    I need some serious help. I was printing invitations last night and I got
    all of them, however, this morning I went to print a document and it won't
    print. In the print que it's showing that it's trying to delete a job from
    last night at 8:30ish. How do I get rid of this?

    "Alan Morris [MSFT]" wrote:

    > http://support.microsoft.com/kb/946737
    >
    > the group that wrote this is pretty proud. Most of you will just start at
    > method 4 since you already performed the first 3 methods.
    >
    >
    > I'll take a minute and explain why a job gets stuck. Uninterested parties
    > just follow the link.
    >
    > Jobs get a reference count associated with them from the spooler and the
    > driver components (print processors and language monitor primarily). When a
    > reference gets incremented without a decrement, the job will still have a
    > reference and the spooler will not delete the job until the component which
    > incremented the count performs the decrement function. If the decrement
    > function never arrives or takes a long time from the function, the job sits
    > in the queue in a deleting state while the spooler waits for the reference
    > count to reach 0.
    >
    > Yes I know, you want to just delete the dang job, you don't care that some
    > process out there is supposed to manipulate the job to signal the spooler
    > that it's done and ready for deletion.
    >
    >
    >
    > --
    > Alan Morris
    > Windows Printing Team
    > Search the Microsoft Knowledge Base here:
    > http://support.microsoft.com/search/?adv=1
    >
    > This posting is provided "AS IS" with no warranties, and confers no rights.
    >
    >
    >


  7. #7
    Alan Morris [MSFT] Guest

    Re: How to cancel printing or to delete a print job that is stuck in t

    Is the job still there after deleting the files as instructed?

    --
    Alan Morris
    Windows Printing Team
    Search the Microsoft Knowledge Base here:
    http://support.microsoft.com/search/?adv=1

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

    "Shawnk" <Shawnk@discussions.microsoft.com> wrote in message
    news:9B609783-199A-404C-8098-7B1F0D2906B8@microsoft.com...
    >I need some serious help. I was printing invitations last night and I got
    > all of them, however, this morning I went to print a document and it won't
    > print. In the print que it's showing that it's trying to delete a job
    > from
    > last night at 8:30ish. How do I get rid of this?
    >
    > "Alan Morris [MSFT]" wrote:
    >
    >> http://support.microsoft.com/kb/946737
    >>
    >> the group that wrote this is pretty proud. Most of you will just start
    >> at
    >> method 4 since you already performed the first 3 methods.
    >>
    >>
    >> I'll take a minute and explain why a job gets stuck. Uninterested
    >> parties
    >> just follow the link.
    >>
    >> Jobs get a reference count associated with them from the spooler and the
    >> driver components (print processors and language monitor primarily).
    >> When a
    >> reference gets incremented without a decrement, the job will still have a
    >> reference and the spooler will not delete the job until the component
    >> which
    >> incremented the count performs the decrement function. If the decrement
    >> function never arrives or takes a long time from the function, the job
    >> sits
    >> in the queue in a deleting state while the spooler waits for the
    >> reference
    >> count to reach 0.
    >>
    >> Yes I know, you want to just delete the dang job, you don't care that
    >> some
    >> process out there is supposed to manipulate the job to signal the spooler
    >> that it's done and ready for deletion.
    >>
    >>
    >>
    >> --
    >> Alan Morris
    >> Windows Printing Team
    >> Search the Microsoft Knowledge Base here:
    >> http://support.microsoft.com/search/?adv=1
    >>
    >> This posting is provided "AS IS" with no warranties, and confers no
    >> rights.
    >>
    >>
    >>




Similar Threads

  1. Print jobs remain in the queue after printing
    By Gus in forum Windows Server Help
    Replies: 4
    Last Post: 06-06-2011, 10:42 PM
  2. Help to delete a document in print queue
    By Mario in forum Vista Help
    Replies: 5
    Last Post: 19-09-2010, 05:08 AM
  3. Replies: 5
    Last Post: 15-09-2010, 04:12 PM
  4. Replies: 4
    Last Post: 17-08-2010, 02:09 PM
  5. Print jobs getting stuck in the queue
    By Bottlenecked in forum Hardware Peripherals
    Replies: 5
    Last Post: 17-08-2010, 12:25 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •