3 Replies Latest reply on Apr 12, 2018 1:33 PM by tcampbell@pharos.com

    Large job lists crashing OXPd

    Mark Royko Newbie

      we're running BPE 5.2, and this doesn't happen often, however we've run into a handful applications that will create a separate jobs when printing reports.  The result is hundreds if not over a thousand print jobs in the user's secure queue.   When our user walks up to the printer and hits secure release, 2 things can happen, the printer will crash and restart (sorry, I didn't capture the Error#), or the printer will display; "45.00.cb Error "Insufficient memory" occurred while communicating with http:\\<your servers URL here>".

       

      Currently we're left with having the user open scout on their workstation and delete jobs (much faster using scout than SRHT). and re-printing a smaller range of data in their reports, or giving them a separate queue that bypasses SRH entirely.

       

      Is there a way to limit the number of jobs sent to the terminal that I haven't found yet, or is this something that may need addressed in a future update?

        • Re: Large job lists crashing OXPd
          Scott Olswold Guide

          Mark,

           

          The issue at hand is that the HTML file being generated for the HP OXPd platform is too large for the HP's operating system to handle. The initial cause (too many jobs being generated) doesn't have a control: Microsoft does not impose any restriction on the number of jobs that can be printed, they can only restrict the available times to print a job and manipulate priority.

           

           

          Since you are using Blueprint 5.2, you could also use Pharos Print Center as a way to manage the printing.

           

          -Scott

            • Re: Large job lists crashing OXPd
              Mark Royko Newbie

              Right, but I'm not looking to limit the number of jobs submitted, only the number of jobs listed at the terminal.  I'd like to limit the number of jobs the server sends to the printer to present the user to say only the 1st 150 jobs.  The user than hits 'print all' and either the entire queue is printed (all 150+ jobs) or the next 150 jobs are listed when the queue is refreshed and they hit print all again till they empty their queue.