Results 1 to 3 of 3

Thread: Cleanup utility and Max Number of Jobs

  1. #1
    Join Date
    Nov 2013
    Posts
    1

    Default Cleanup utility and Max Number of Jobs

    We have a Fiery EB 32 connected to a Ricoh getting the message "max number of jobs reached"
    without running the cleanup it seems as though previous jobs accumulate on some unknown to me temp spool directory. we are using a template so running the cleanup forces us to reload the template every time we "cleanup".
    A. sending to direct print
    B. Post Script Driver
    C. error will appear after varying number of statements it would seem this is dependent on how recently we ran the cleanup utility.
    D. System Software and Engine firmware are all up to date
    1. is this caused by spool size, number of jobs, pages or something else. if we run the cleanup utility we can complete our jobs up to 15k statements.
    2. can we edit the cleanup commands in a manner allowing the template to stay and still clear the the rest of the directories to allow printing larger number of statements

  2. #2
    Join Date
    Jul 2009
    Location
    Amsterdam
    Posts
    963

    Default

    So many questions.

    Firstly what is this cleanup you are running? Screenshot or details?
    Also what is this template you need to reload after cleanup? Imposition template?

    What does Command Workstation report in Device Center, general tab? Can you post a config sheet taken when the error shows? Or even when it doesn't?

    Your Fiery has a max job limit of 10,000 jobs - meaning only this number of jobs can be present in the system at any one time, including active jobs, printed queue, hold queue, archived queue.

    If you're printing to the print queue (or direct queue) then you shouldn't run into this limitation, as jobs will be cleared from the system after they are printed, and clear the printed queue. Are you storing loads of jobs in hold or archive?
    Last edited by Greta_C; 01-26-2016 at 12:48 PM.

  3. #3
    Join Date
    Jul 2009
    Location
    Amsterdam
    Posts
    963

    Default

    Whoah Nelly!

    Thanks for the fast reply Art Cain, but please don't post Fiery internal code and scripts online like that, as someone could break their Fiery using that kind of info.
    I have deleted your post, but forwarded the information to our tech support who will contact you separately about this issue.

Posting Permissions

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