This section lists bugs and limitations that are known to exist in the software. If a future version of the software resolves a bug listed here, the bug is moved to the Fixed bugs section of the release notes accompanying that version of the software.
When using Digital Job Ticket Editor from within Workshop (Send to Digital command) or when opening Device Track from the Workshops Tools menu, the Measurement Unit defined in Workshop's Preferences is used and the Weight Unit and Thickness Unit (Caliper) are taken from Setup's Preferences.
When Device Track is opened on the web (not from within Workshop), all unit settings in Digital Job Ticket Editor are taken from Setup's Preferences. [PRINERGY-42049]
When using Internet Explorer with Device Track, Device Track requires version 11 or later. [PRINERGY-41757]
Digital output jobs may fail to output if moved from a Digital-Direct/Digital-Submit-connected device to a JDF-bi-directional-connected device. [PRINERGY-44863]
Due to limitations in third-party JDF implementation, some settings may not flow back to Setup when updated in the front end software. This can include: binding edge, maximum density, layout, and sheet size options. [PRINERGY-39050] [PRINERGY-39982] [PRINERGY-40039] [PRINERGY-40045] [PRINERGY-41511] [PRINERGY-41632] [PRINERGY-41732] [PRINERGY-41745] [PRINERGY-41836] [PRINERGY-41906]
The following limitations have been identified for using the ColorFlow software with Prinergy:
Pages added to a ColorFlow-enabled job using Prinergy's Bypass Refine will have undefined Color Setup. This is expected behavior. Refining with ColorConvert enabled is recommended with ColorFlow integration.
If you attempt to output a file with a different snapshot number from the number you defined in the refine process template, an error message appears.
The following ColorConvert problems have been identified:
Color matching certain files with transparent objects can result in significant changes in appearance. The problem is file specific and is dependent on the transparency blending modes applied, the object's color and the DeviceLink or ICC profile used to colorconvert the objects. The problem occurs because each graphic and image object used in the transparency group is color-converted separately. Blending of the objects in the destination color space changes the appearance.
Recommendation: Flatten the PDF files. If your PDF files contain RGB data, it is highly recommended to Color-Convert this data prior to flattening. Refer to Answer ID 72326 for best practices and setting up a 2-Step refine.
Note: Contone proofing cannot be used to predict this issue when colormatching is performed on final output.
ColorMatch vector overprint handling of certain files with transparency groups that also use overprint management can generate unexpected results. The new objects generated by the ColorMatcher vector overprint handling process end up ruining the appearance. Contone proofing with raster overprint handling cannot be used to predict the problem with vector overprint handling used on final output. See the Prinergy help for detailed descriptions about the processing differences between raster and vector overprint handling.
Recommendation: Flatten the PDF files. If your PDF files contain RGB data, it is highly recommended to Color-Convert this data prior to flattening. Refer to Answer ID 72326 for best practices and setting up a 2-Step refine.
RGB Transparency Blend Color Space is not supported. Blend spaces should only be defined as DeviceCMYK.
Recommendation: Change the blend space in the input file or set up a Preflight+ profile to detect and/or fix the condition.
ColorConvert is automatically selected in Vector Output process templates after you upgrade to Prinergy 8.1. This is due to a migration script bug. If you have a Basic License which doesn’t enable ColorConvert, vector output will fail. If you are licensed for advanced Color Management, Color Conversion will be applied at output and may cause incorrect output. [PRINERGY-42167]
Workaround: open any Vector Output process templates which should not have ColorConvert enabled and clear the ColorConvert checkbox.
callas process plans and profiles that create layers or contain unlicensed DeviceLinks are not supported.
Kodak does not support or provide a license of callas pdfToolbox software. However, a copy of pdfToolbox (Preflight+ Profile Manager) is provided and licensed solely for the purpose of editing and creating preflight profiles that are to be used within Prinergy. Modification of the license as well as changing or upgrading the version of callas pdfToolbox that is provided with Prinergy is not recommended and not supported by Kodak. Kodak does not provide assistance or support for editing or creating new callas profiles. For information and support with the creation and editing of profiles, go to http://www.callassoftware.com/en/support/documentation.
Note: Kodak does support issues related to the integration of callas preflight within Prinergy Workshop.
callas fix-ups are "use at own risk". Exercise extra caution and check your proofs closely when applying fix-ups.
callas Profiles and Prinergy support different variations of the Chinese character set.
Simplified = ZH_Hans (Prinergy) = South East Asia and Singapore
Higher disk space demands—each PDF report contains a copy of the original Input PDF file.
The Adobe PDF Print Engine (APPE) RIP cannot process PDF files containing embedded PostScript objects, including pages that were processed with PostScript bypass or with the OPI bypass features of Prinergy.
The APPE RIP is the preferred RIP for Prinergy.
Observe the following precautions:
Proofs and plates: In plating jobs with the APPE RIP, be careful with plates that were proofed with the previous APPE RIP. Because the RIPs are different, there is a slight chance of an interpretation difference between proof and plate. Ideally, jobs should be plated with the same version of Prinergy that was used to generate the proofs.
Note: To avoid this situation you should coordinate hub and spoke configurations when upgrading Prinergy.
Reprints: For reprints of jobs that were printed previously using an older RIP, it is recommended that you rerun proofs using the new RIP to ensure there are no unforeseen differences between the original press run and the reprint.
As of Prinergy 8.0, all factory Spot Color libraries were replaced with Pantone V3 Lab libraries. If you refine a file that contains a Spot Color that is defined in the Lab library, the Spot Colors Alternate Color Space will change to Lab. Since Lab is not allowed in PDF/x-1a, the process will fail.
To resolve this, you can remove the PANTONE V3 library or load a CMYK library, such as a legacy user or ColorBridge library (Answer ID 73041).
Note: If your incoming PDF has Spots with LAB Alternate Color space, you will want to have a CMYK Pantone library loaded, otherwise refine will also fail.
When converting Spots to Process, its recommended to use the new PANTONE V3 Library. See the About Pantone Libraries section of the Workflow Help for more information. (PRINERGY-43630)
Kodak Maxtone CX, Maxtone FX, and Maxtone SX screens are available for APPE RIP only. They are not available for use with CPSI RIP.
Workaround: Manually set the spot screen angle in the output process template [PRINERGY-40790]
When system spot color library L*a*b* 2000 is added to a refine process template, it may not appear in the spot color libraries list but it will be available to be used by refine processes created from the refine process template. [PRINERGY-44022]
When using this setting you must follow the procedure outlined in Partner Place Answer ID 69302. Failing to do so could result in serious Output problems.
If you open an LPV page in Acrobat and then re-generate it, the Register step will fail with an access violation message. This only happens when dealing with Windows 2008 servers and if the PDF has been opened on a Mac. [PRINERGY-29349]
Workaround: Unmount the Mac share.
[Prinergy-34180]
Mitered joins in text objects with very large strokes may render incorrectly in low resolution output (300 dpi). [PRINERGY-38023]
The following limitations have been identified when running Prinergy using the Windows Server 2008 R2 x64 or Windows Server 2012 R2 operating systems:
Not all legacy Kodak computer-to-plate (CTP) devices have controlled release software that is compatible with Windows 2008 R2 or 2012 R2. Contact your Kodak representative to confirm if your CTP device has a compatible controlled release software available.
Services for Apple Macintosh does not work with Windows Server 2008 R2 or 2012 R2. You must use SMB with named forks.
By default, Prinergy servers running Windows Server 2012 R2 are shipped with SMB 2 and 3 enabled. For best performance, all Prinergy servers and tertiary servers should be running Windows Server 2012 R2. If any of the Prinergy servers are running Windows Server 2008 R2 or any of the tertiary servers are not running Windows Server 2012 R2, SMB 2 and 3 need to be disabled so that SMB 1 is used. If this is not done, this can cause performance and file consistency issues. For assistance in disabling SMB 2 and 3, contact your local support representatives.
To enable activation of Workshop, perform the following steps: [PRINERGY-34821]
Click Security and Privacy.
Click the General tab.
Click the lock icon located in the lower-left corner of the Security & Privacy window.
Enter your administrator credentials to enable making changes to the settings.
Under Allow apps downloaded from, select Anywhere.
Close System Preferences.
To enable installation and/or activation of Setup, perform the following steps: [PRINERGY-41785]
Some updates of Symantec Anti-Virus interpret Prinergy’s ARAXI service as a threat. This has been addressed in newer updates to Symantec Anti-Virus. It is recommended that you update your virus definitions to avoid any problems with Symantec Anti-Virus affecting the operation of your Prinergy Workflow system. Alternatively, to exclude araxi.exe from the threat list, refer to Partner Place answer ID: 72379. [PRINERGY-39813]
Prinergy does not support The Open Group UNIX NFS (Open Group UNIX Network File System). You can access UNIX servers using an SMB/CIFS protocol installed on the server (such as SAMBA).
The fresh installer does not run on Windows 2012 R2 servers localized to Japanese. The server must be localized to English, or another supported non-Japanese localization before the fresh installer is run. Then, the server can be returned to Japanese localization. [PRINERGY-42036]
The current implementation of XMP screening tags in Prinergy 8.1 applies the full set of XMP screening settings to the output. (PRINERGY-43209)
When running Digital Submit with NexPress on Windows 10, the Job Ticket Editor in Digital Submit fails to launch. [PRINERGY-41688]
Workarounds: To launch the NexPress Job Ticket Editor:
The HP Job Ticket Editor is software available from HP which is used in Prinergy Workflow when connecting to HP digital presses. The latest version of the software available from HP is not compatible with Windows 8 and Windows 10 operating systems. HP is aware of the issue and will address it in a future product update. [PRINERGY-41575]
Perfect bound jobs with covers sent to Ricoh digital front end with PDF RIP Enhanced by Kodak type S4 may result in output with incorrect orientation. [PRINERGY-42077]
Due to limitations in JDF implementation for Ricoh digital front end with PDF RIP Enhanced by Kodak type S4, layout options are not currently supported. [PRINERGY-39050]
When sending a surface to Ricoh, the binding edge defined in the job will rotate 90 degrees clockwise due to geometry translation, but the end result of the output at the printer will be correct. If you have questions, contact your Kodak representative for assistance. [PRINERGY-42029]
Jobs printed successfully move to On Hold queue rather than Completed queue in Device Track. This is a known Ricoh bug. [PRINERGY-45100]
The status of coated or uncoated stock may not be imported or reflected correctly in Prinergy Setup for digital connections to Konica Minolta IC-602 or C1070 digital printer front end software. Job settings may need to be manually updated in the Konica Minolta software to complete output successfully. [PRINERGY-43211]
Due to a limitation in the bi-directional communication with EFI’s software, completed jobs are do not appear in Prinergy Workflow’s Device Track Completed queue and are not present in any queues upon completion. [PRINERGY-43780]
Submitting a file to Prinergy Workshop localized to Japanese via drag and drop to a process template may cause Workshop to quit unexpectedly. [PRINERGY-43660]
Workspace is an alternative job and imposition interface that was introduced in Prinergy 6.0 and supported through Prinergy 7.5. There are several elements that remain in the Prinergy Workflow user interface that are not supported with Workshop client workflows, for example:
Note: It is recommended that you avoid using unsupported actions.
Prinergy Signature Selection works in Preps 5 mode. Therefore, there are a number of limitations related to working with Preps 6 or later.
The use of Auto Select in Prinergy Signature Selection may produce different results from the use of Auto Select in Preps. Check that Auto Select produces the expected results.
If required, you can use Move Up or Move Down to adjust the signature order, or use Add or Delete to get the right signature.
To prevent the problem, edit the PrepsPrinergy.cfg and the PrepsPrinergy.cfg.template files to include the line:AUTOSELECT_MINIMUM_PAGES:1.
When editing an imposition and keeping the existing page set, when you return to Workshop from Preps, the imposition status shown in Workshop may not be updated to reflect the changes made in Preps. If this occurs, quitting and restarting Workshop should refresh the job's imposition information to show the correct state of the imposition. [PRINERGY-45308]
Regardless of the status of the enabled/disabled status of individual custom fields, all custom fields will be displayed in Dashboard. [PRINERGY-29639]
By default, Prinergy servers running Windows Server 2012 R2 are shipped with SMB 2 and 3 enabled. For best performance, all Prinergy servers and tertiary servers should be running Windows Server 2012 R2. If any of the Prinergy servers are running Windows Server 2008 R2 or any of the tertiary servers are not running Windows Server 2012 R2, SMB 2 and 3 need to be disabled so that SMB 1 is used. If this is not done, this can cause performance and file access/transfer issues. For assistance in disabling SMB 2 and 3, contact your local support representative.
In Prinergy 8.1.1 SMB 2 on Windows Server 2008 R2 will be automatically disabled.
Notes:
Rules Based Automation (RBA) may not start after upgrading to Prinergy Workflow 8.1.2. To address this issue, if encountered, see Partner Place answer 73601.
When rolling back from Prinergy Workflow 8.1.2 to a previously installed version, the Prinergy server may be unable to automatically retrieve a license for the previously installed version. In these cases, you will receive an alert from Prinergy Administrator that the current license is invalid. If you encounter this problem, please contact your service organization to address the issue. [PRINERGY-45926]