Printing jobs

In this section:

1. Errors when printing Cyrillic or Japanese characters on PDF banner pages
   If you try to use Cyrillic or Japanese characters on PDF banner pages with a workflow that uses the default values for the Header page configuration file and Trailer page configuration file properties, the characters do not display correctly.
2. Jobs do not print on a Ricoh PDF printer
   Configuring RICOH ProcessDirector to send jobs to a cutsheet printer using a Ricoh PDF printer device can be challenging. If you set up a Ricoh PDF printer and jobs are not printing, use these instructions to check the most common configuration issues.
3. Jump to goes to incorrect page
   If you click the Jump to control in the RICOH ProcessDirector user interface and the page where the printer resumes is not the page displayed in the viewer, check for functions that can introduce inaccurate page counts. Examples are cut sheet emulation, N_UP printing, and the Duplex and Form definition job properties.
4. Job copied to a hot folder does not print
   If you copied a job to a hot folder and it does not print, the physical printer might not be able to receive jobs. Check to see if an AFP printer device represents the same physical printer.
5. Job prints on wrong printer
   If a job received from Download for z/OS or AFP Download Plus prints on a printer other than the one you expected, you might have to change the printer properties or your configuration file so that RICOH ProcessDirector uses the value of the DEST parameter in the job's JCL to select the printer.
6. Job requires a long time to stop printing
   If you use the Stop action on a job that is printing but it takes a long time for the job to stop printing, you might need to change some settings on the printer console.
7. Job moves to error state with message AIWI0017I, return code 310
   If a job goes into an error state and you see message AIWI0017I with return code 310, there might be a problem with submitting files to RICOH ProcessDirector.
8. Job moves to error state with message AIWI6416E
   If a job goes into an error state and you see message AIWI6416E, there might be a problem with the AFP file or there might have been an error when RICOH ProcessDirector tried to connect to the printer.
9. Job moves to error state with no message
   If a job goes into an error state during the PrintJobs step and you do not see an error message on the error-message pages or in the printer log, there may be more information in /var/psf/printernameaiw1/error.log (AIX and Linux) or C:\Program Files (x86)\InfoPrint\PSF\var\psf\printernameaiw1\error.log (Windows). printername is the name of your printer.
10. AFP jobs print with incorrect colors
    If an AFP job contains multiple AFP presentation documents and they have different color management resources (CMRs), the job can print with incorrect colors.
11. Job containing multiple AFP files does not print
    The AFP architecture lets applications put multiple documents in a single file. The document boundaries are marked with Begin Document (BDT) and End Document (EDT) structured fields. Applications might use this function to cause finishing operations, such as stapling or binding, to operate on each document separately. However, some steps provided in many workflows supplied with RICOH ProcessDirector cannot process files that contain multiple documents.
12. Recovering from printer jams
    Usually RICOH ProcessDirector can resume printing from the last stacked page when a jam is cleared from the printer. However, for AFP printers only (especially continuous forms printers) follow these steps if you need to reprint some of the pages that were successfully stacked. For example, you might need to be certain that you have complete jobs for any post-processing equipment.
13. Job moves to error state with message RPDF008E
    If a job goes into an error state and you see message RPDF008E, check how your Ricoh PDF printer is configured.
14. Job prints on incorrect media using an AFP printer
    If AFP support is installed and your job was sent to an AFP printer, where it printed on the wrong paper (for example green instead of blue paper), you might need to update some job or printer properties.
15. Job prints on incorrect media using a Passthrough printer
    If your job was sent to a Passthrough printer and it printed on the wrong paper (for example green instead of blue paper), you might need to update some job or printer properties.
16. Job prints on incorrect media using a Ricoh PDF, Custom PDF, or Ricoh TotalFlow printer
    If your job was sent to a Ricoh PDF, Custom PDF, or Ricoh TotalFlow printer and it printed on the wrong paper (for example green instead of blue paper), you might need to update some job or printer properties.
17. Jobs do not print with electronic forms
    Several different problems can keep jobs from printing with electronic forms.
18. Data does not print correctly on electronic forms
    If data does not print correctly on electronic forms, check the size and alignment of the electronic form and the pages that contain the job data.
19. Page data is combined with the wrong electronic forms
    If page data is combined with the wrong electronic forms, make sure that the correct forms have been defined for the media objects. Also make sure that the CombinePDFWithForm or CombineAFPWithForm step has been placed correctly in the workflow.
20. Jobs with electronic forms print on the wrong paper
    Even when electronic forms are combined with page data correctly, several problems can cause jobs to print the forms and page data on the wrong paper.
21. Whole job reprints instead of selected pages
    If you select a page range when you reprint a job, but the entire job reprints, the workflow might not include required steps, or reprinting might be starting at the wrong step.
22. Job moves to No matching device state
    When a job stops in the No matching device state, check the Requested printer property and make sure that the scheduling properties for the job match the corresponding properties of the requested printer.
23. Job moves to No matching media state
    When a job stops and the value of the Current job state details column is No matching media, the media name or media properties in the JDF job ticket or overrides file for the job cannot be matched to an existing media object.
24. Job moves to Device unavailable state
25. Job in Status changed on printer state
    If a job is in the Status changed on printer state, the job was manipulated on the printer console and the status is no longer reported.
26. Printing a large PDF file causes an out of memory message or slow processing
    If you see an out of memory message or encounter slow processing when printing a large PDF file, you can set the Merge banner pages into PDF print file property to No or increase the Java Virtual Machine (JVM) memory. Merging banner pages on large PDF files takes more memory and system resources than printing banner pages as separate files. If you need to merge banner pages, increase the JVM memory.
27. Errors in jobs for WPM Web
28. Incorrect characters in document properties from PDF files
    If you have trouble with document property values that are extracted from PDF files using RICOH ProcessDirector Plug-in for Adobe Acrobat, the fonts included in the PDF file might be incomplete or contain different UNICODE mappings than you expect.