locked
Aborting a Print Job RRS feed

  • Question

  • We have been trying to find a way to abort a print job after it has been sent.  In this case the job is spooling and starting to print.  The user suddenly sees a problem, wrong paper, etc.  We want to be able to stop printing but not delete the job from the queue.  Just reset and start printing again without needing to re-rip the job.

    By experimentation we found a procedure that works on some machines but I'm almost sure that it is not a documented or supported method.

    1) Press the ink change button on the printer (epson 1800 series). This makes it stop printing.

    2) Pause Q

    state : Paused - Printing

    3) Restart

    state : Paused - Printing - Restarting

    4) Cancel

    state : Deleting - Paused - Printing

    after some time

    state : Paused - Sent to Printer

    5) Resume

    state : Sent to Printer

    6) Hit ink change button again

    Now the printhead parks and the job is still in the queue and can be printed.

    • Moved by Amanda Zhu Tuesday, May 21, 2013 3:14 AM not VS general forum issues and not sure which appropriate forum this thread can be moved to
    Friday, May 17, 2013 10:30 PM

Answers

All replies

  • As was said, not a specific VS or MS technology related question. It seems this forum would be appropriate: http://www.rangefinderforum.com/forums/forumdisplay.php?s=464d014ecef2d3c3c6cdab7dae7b246c&f=149 Good luck!

    Kind regards,
    Margriet Bruggeman

    Lois & Clark IT Services
    web site: http://www.loisandclark.eu
    blog: http://www.sharepointdragons.com

    Tuesday, May 21, 2013 6:41 AM
    Answerer
  • Were is the question?

    Seems to me you've explained how to do what you want to do.

    Karl


    When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer



    My Blog: http://unlockpowershell.wordpress.com
    My Book: Windows PowerShell 2.0 Bible
    My E-mail: -join ("6B61726C6D69747363686B65406D742E6E6574"-split"(?<=\G.{2})",19|%{[char][int]"0x$_"})

    Thursday, May 23, 2013 8:37 PM
  • Sorry I don't know all your forums.  I was looking for one specific to printing but found it hard to navigate.  I wanted to post to microsoft because I'm hoping they have a supported way to do this.  For most common work with print queues, once you print, the horse is out of the barn and you can't get it back.  I have been over all the documents of the printqueue class and couldn't find anything for this.  The procedure we found that I disclosed is what I would consider hacking the queue methods and we have already found that it does not work on all systems.  I wish microsoft would add an "abort" method to do this, although I believe there is printer interaction required with this so the method may need to be supported by printer firmware.

    Friday, May 24, 2013 7:04 PM
  • You'd have to explain what you are printing from.

    Generally, I'd ask in the Windows forum of Microsoft Community.

    You might also read "How to ask questions in a technical forum"

    Karl

    When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer



    My Blog: http://unlockpowershell.wordpress.com
    My Book: Windows PowerShell 2.0 Bible
    My E-mail: -join ("6B61726C6D69747363686B65406D742E6E6574"-split"(?<=\G.{2})",19|%{[char][int]"0x$_"})

    Friday, May 24, 2013 9:15 PM
  • We print images.  Whether we are printing from a custom RIP or mspaint the issue is the same.  They both become a job in the queue and are handled by the PrintQueue Class methods.  The driver is EPSON Stylus Photo R1800.

    This is for a direct to substrate printing business and jobs can take a while to rip so if users need to abort printing because something was not set up right, they don't want to re-rip.  They will often keep a job in the queue and print it over and over.

    Thanks for looking at this. I'm not getting much response except for scolding for not posting right.


    mecker82

    Friday, May 31, 2013 7:16 PM
  • Please don't see it as scolding. I guess most people, such as myself, just try to help you find a better place to get the answers for your questions. Sometimes, it's just not that easy to find the correct place to ask a question, but what makes this a community is that people try to help each other instead of bashing each other on the head for (allegedly) making mistakes.

    Kind regards,
    Margriet Bruggeman

    Lois & Clark IT Services
    web site: http://www.loisandclark.eu
    blog: http://www.sharepointdragons.com

    Monday, June 17, 2013 2:06 PM
    Answerer