Home | Contact Us | Submit Troubleshooting Info | Search | Help


    Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS


When multi-file refine job tickets are enabled, the mechanism to fail refined files after preflight is broken


Product

  Prinergy Connect 2.0

Platform

 

Operating system

 


Error

 

Normalizer sets a "Fail Refine" flag in the job ticket when the OPI thread detects refine problems (missing image,missing font, etc). The flag is read by Optimizer and if set (true), Optimizer will fail the task after it finishes preflighting the PDF.

With the introduction of multi-file job tickets (multiple files per task which is introduced by 2.0.7.10), this mechanism is no longer appropriate and causes file failure notification problems.


Symptoms

 

There are two symptoms:

-- When any file other than the final file of a refine group within a multi-file job ticket fails with refine problems, the problem file will not be designated as failing with a red X in process info or history, even though no refined pdf file was generated for that file

-- When the final file of a refine group within a multi-file job ticket fails with refine problems, all files in the group will be designated as failing with a red X in process info and history.

All of the details about the failure will still be available in the history or process info; however, the high level summary in process info and history will not have a red X.


Cause

  There are 2 problems with the existing detection mechanism:

-- Using this mechanism, Normalizer has no way to indicate which file had a problem (there's only one flag for the whole job ticket).

-- Normalizer currently resets the flag before processing each file, so the flag is set (true) only if the last file in the job ticket happens to have refine problems.


Solution

 

If the problem file is reprocessed individually, there will be no subtask file groupings required so the file will be processed and appropriate errors indicated correctly.

If customers cannot live with this limitation, there is a registry value that can be set to disable the multiple refine pages per sub task grouping. Note however that disabling this feature may significantly impact the productivity of high volume sites for which this grouping feature was developed, so it should only be disabled if absolutely necessary. The registry value is:

"TAKS\EnableMultipleRefinePagesPerSubTask" - set the value to 0 to disable it, 1 to enable it.

Permanent fix: Prinergy 2.0


See also

 


Keywords

 

job ticket, refiner


Technical contact(s)
 

Glen Cairns

Submitted by
 

Brian Laberge

Date submitted
 

18 Dec 2001


    Copyright © 2005 Creo Inc. All rights reserved. Confidential. Back to top.