Description

This article lists common Pageflex errors and their corresponding causes.

• Error when deploying a project file

  If you see the following error after hitting deploy:

  folder failed validation:
  Object reference not set to an instance of an object.

  Make sure that all three of your jobs start with a capital P (Preview, Proof and Production).

• Error finding an image

  Document 1 - Evaluation failed for variable: ImageRule. File not found: FreeCat.jpg

  If you see an error similar to this, it means that it cannot find the image file. In this case, it is looking for FreeCat.jpg. Make sure the image is where it is suppose to be, and also make sure the spelling of the file matches your rule or data source.

• Error finding a file

  Document 1 - Evaluation failed for variable: ImageSelection. File not found: Cat

  If you see an error similar to this, it usually means that you have the As File box checked for your Plain Text / Constant variable (ImageSelection). You will need to uncheck this box, as it should only be checked for your image rule.

• Error finding an .xdt file

  Failure reading job template file: Template1.xdt

  This type of error means that your job (Preview, Proof or Production) is connected to an .xdt file that does not exist in your folder. Open up each job to make sure the correct .xdt file is referenced in the Template dropdown, and then hit OK.

• Font style error

  Document 1 - The font 'Broadway' is not available in the requested style (bold upright). (critical error)
  

  This type of error means that the style for this font does not exist. It could mean that bold is not available for this specific font, or it could mean that the font file for this style is not in the Project Fonts folder.

• Zip Code appears as floating-point decimal number

  If you are using an Excel data source, and your zip code is appearing as 55403.0 instead of 55403, then there is an issue with the formatting of that cell. You will need to make sure your zip column is properly formatted to Text. Follow these steps:

  1. Copy zip column and paste into notepad.
  2. Delete zip column.
  3. Create new zip column and format column to text.
  4. Copy data from notepad and paste back into your new zip column.
• Job yields no records

  Error: Job yields no records.

  This error occurs when the Pageflex project and jobs are connected to a data source, but the selected specification value does not exist in the spreadsheet.

  Make sure that the value in the data source exactly matches the corresponding specification value. Also verify that the specification name inside << >> exactly matches the specification name in Storefront. Once corrected, save the entire project and redeploy it.

• Mpower job timed out

  Error: System.Exception: Mpower job timed out.

  This error can occur when an image in the Pageflex project points to a file on a local computer or network location that the Pageflex server cannot access.

  Move the image into the project’s Images folder. Update the image source in the template to reference the file in that folder, save the project, and redeploy it.

• Preview job times out

  Error: System.Exception: Mpower job timed out.

  If the Proof job works but the Preview job times out, check the Bitmap properties of the Preview job. A high output percentage may prevent the Preview from rendering.

  Lower the Bitmap percentage and test again. If the percentage cannot be edited, create a new Preview job and set the percentage before changing the DPI. For an 8.5-by-11-inch document, 50 percent or lower can be used as a starting point.

• Incorrect Preview job format

  If the Preview job does not render correctly, open the Preview job and check its output format.

  The Preview job must be set to Bitmap, not Convert PostScript to PDF. Save the project and redeploy it after correcting the job.

• Duplicate font conflict

  A font may render incorrectly, such as appearing italic instead of regular, even though it looks correct in Pageflex Studio. This can happen when the Project Fonts folder contains another version of a font that already exists on the Pageflex server.

  Remove the fonts from the Project Fonts folder and upload the project again. Pageflex will add the server fonts referenced by the project. Test the project, and then add back only fonts that are still reported as missing.

• Font variant does not render correctly

  If one font style does not work but the other styles in the same font family work correctly, the affected font file may be invalid or incompatible.

  Remove the affected font file and replace it with another valid version. If the replacement continues to fail, use a similar font for the affected text.

• Unsupported Type 1 font

  Error: J0005000: A failure occurred in a custom renderer.

  If the job log references a Type 1 font, remove the unsupported font from the project and replace it with a suitable TrueType or OpenType font that supports printing and embedding.

  If the error continues after removing the font files, check the project's .xdt files for references to the old font. Remove or replace those references, save the project, and redeploy it.

• Special character does not appear correctly

  If a special character appears incorrectly in the Preview or output file, the selected font may not include that character.

  Review the font's character map and change the affected text to a font that supports the required character. Changing the Pageflex variable type will not resolve the issue if the character is not included in the font.

• Number is out of range

  Error: Number is out of range.

  This error can occur when a PDF file is used as an image in the Pageflex project.

  Open and resave the PDF, replace the existing file in the project, and test again. Also open the Proof and Production job properties and ensure that Fast Web View is not selected.

• Invalid use of null pointer

  Error: [Microsoft][ODBC Excel Driver] Invalid use of null pointer.

  This error is related to the Excel data source connected to the project.

  Delete the existing data source from the Pageflex project and add it again. Save the project and redeploy it.

• Copyfit rule does not work

  If a Copyfit rule does not work, check that the rule name configured in the job exactly matches the rule name in the .xdt template.

  Correct any spelling, spacing, or capitalization differences, save the project, and redeploy it.

• Fillable PDF values do not appear

  If a user completes fields in a fillable PDF but the entered values do not appear in Pageflex, flatten the PDF before adding it to the project. One option is to complete the PDF and use Print to PDF to create a flattened copy.

  If users need to enter information through Storefront, use the PDF as the background artwork and create the input fields as Pageflex variables instead of using the PDF's interactive fields.

• Plain Text variable is treated as a file

  Error: Evaluation failed for variable: VariableName. File not found: Entered Value.

  This error usually means that As File is selected for a Plain Text or Constant variable.

  Open the variable and clear the As File option. This option should only be selected when the variable is intended to reference a file.

• Formatted Paragraph variable cannot find a file

  Error: Evaluation failed for variable: VariableName. File not found: Entered Value.

  If a user-entered value is configured as a Formatted Paragraph, Pageflex may try to locate an exported paragraph file with that name.

  Use Formatted Paragraph only when the variable is connected to exported paragraph files. If users need to enter multiple lines of text, change the variable to Formatted Text instead.

 

Reason for Change: The current article does not include several common Pageflex errors documented in previous cases and internal troubleshooting notes. Adding these items would provide customers with more self-service troubleshooting options.

Approved By: Vince Fenton, Manager, OrderCloud Support