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.
The Mac M1 chipset has limited supported at this time. Please see the "Supported client workstations" section of these Release Notes.
Some free "Internet fonts" can cause issues
Malformed Fonts that do not follow strict specifications (typically found for free on the Internet) may cause issues on refine and or output. Proof carefully if using these types of fonts.
Using a Preflight+ check such as "List Potential Font Problems" is sometimes a good way to mitigate this risk.
Dashboard has been removed in Prinergy 9.0 and is no longer supported
With the end of support for Adobe Flash, Dashboard is no longer available in Prinergy. Dashboard functionality is migrating to the PRINERGY On Demand portal. See PartnerPlace answer ID 75256 for more information.
Setup client interface is no longer available in macOS Workshop client
The Setup client interface has been removed from the Prinergy Workshop client on macOS due to Silverlight End Of Service Life by Oct. 12, 2021. Setup continues to be available with the Windows Prinergy Workshop client.
PDF Editor Adobe Illustrator Plugin is no longer installed as of Prinergy 9.0
Tiff Direct Output fails when making on-the-fly Process Template edits - PRINERGY-52304 - Addressed by P9.0.0.3. See Available Patches.
Big Sur (11.0) support
The shortcut WorkshopInstaller does not work properly. If you double-click it, Workshop will not be installed.
Workaround
1. Connect to the WkspInstall share on the server.
2. Within the share, navigate to MacOSX>Disk1>InstData
3. Double-click the WorkshopInstaller application to begin the installation.
(PRINERGY-49418, PRINERGY-49597)
Active Directory support via Patch P9.0.0.2
Note: Limitation is applicable to Prinergy servers within an active directory domain
The following graphics cards are known to be affected:
Radeon Pro Vega 56 |
| Radeon Pro 580x |
Radeon R9 M390 |
| Radeon Pro 5300 |
| Radeon Pro 5300M/Intel UHD 630 |
| Radeon Pro 5300 XT |
| Intel Iris Plus Graphics 1536 MB |
Workaround
1. Connect to the WkspInstall share on the server.
2. Within the share, navigate to MacOSX>Disk1>InstData
3. Double-click the WorkshopInstaller application to begin the installation.
(PRINERGY-49418, PRINERGY-49597)
The current Managed Services entitlement under the Line Extension License feature may not be reflected in the number of JTPs you are licensed for on your Prinergy Primary. Version 9.0.0 is currently limited to a maximum of seven trapper JTPs and 15 Register JTPs.
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]
Commas are not supported as a decimal separator in the Job Ticket Editor. To change the number format, open the Region control panel and press the Additional Settings button. When the Customize Format window appears, select the Numbers tab and make sure that the Decimal symbol is set to a period (.).
When using Internet Explorer with Device Track, Device Track requires version 11 or later. [PRINERGY-41757]
An issue with status reporting coming from Kodak Xpo can cause the In Process queues in Prinergy’s Device Track UI and Xpo to get out of sync and display output separation in the wrong order in Device Track. [PRINERGY-47843]
After successful completion of output to EFI or Canon digital front-ends, the completed output jobs are absent from all queues in Device Track. [PRINERGY-47923] [PRINERGY-43780]
When resubmitting a separation via Device Track, the separation receives a new Job ID from the device control software (Xpo or Print Console). This is due to the separation being treated as a new output instance rather than a remake of a previous output.
Device messages prompt on Print Console 5.24 do not pop up on Prinergy 9.0.2 TRACK > Device Messages Window [PRINERGY-52855]
When using a slugline mark with the updated sluglinemark positioning settings in the process template with direct (GDAPI) and TIFF Direct connectivity to CTP devices, the slugline mark may appear in the wrong location on the plate. [PRINERGY-46463]
When using a slugline mark with the updated sluglinemark positioning settings in the process template with direct (GDAPI) and TIFF Direct connectivity to CTP devices, the slugline mark may appear in the wrong location on the plate. [PRINERGY-46463]
Due to limitations in third-party JDF implementation, some settings may not flow back to Prinergy Workflow’s Setup application 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. Please refer to Partner Place 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.3. 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.
When upgrading to Prinergy 9.0 from 7.5.x, 8.0.x, or 8.1.x Custom Checks and Fixups will not be migrated as their own entities. However, profiles referencing Custom Checks and Fixups will have been updated to incorporate the Custom Checks and Fixups; meaning, they will continue to work as they did prior to upgrading.
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 https://www.callassoftware.com/goto/tbx_ENG_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
Because each PDF report contains a full copy of the original input PDF file, using Preflight+ may result in higher demands on storage space in your job home disks.
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.
As of APPE 4.7 a maximum of 123 spots colors is supported (in addition to the four CMYK process colors, for a total of 127 colors).
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.
In keeping with PANTONE best practice guidelines, all previous PANTONE libraries have been removed as factory libraries and will no longer appear in your process templates. Previous Prinergy PANTONE libraries are provided in archive format and can be imported as user libraries, if desired, for legacy reprint jobs. For more details, see About PANTONE libraries.
Kodak Maxtone CX, Maxtone FX, and Maxtone SX screens are available for APPE RIP only. They are not available for use with CPSI RIP.
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]
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]
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.
[Prinergy-34180]
The following limitations have been identified when running Prinergy using the Windows Server 2016 and 2019 operating systems:
Not all legacy Kodak computer-to-plate (CTP) devices have controlled release software that is compatible with Windows Server 2016 and Windows Server 2019. Contact your Kodak representative to confirm if your CTP device has a compatible controlled release software available.
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).
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]
C:\Windows\System32\drivers\etc\host [PRINERGY-45428]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]
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]
Prinergy Signature Selection works in Preps 5 mode. Therefore, there are several 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.
Re-editing a Preps imposition from Workshop may not work for certain imported jobs. If the imported job contains an imposition name that is greater than 25 characters and had an imposition that was previously edited and the older version was deleted. To prevent this issue when editing existing impositions always choose the import option to "Keep existing imposition". [PRINERGY-50121]
Rules Based Automation (RBA) may not start after upgrading to Prinergy Workflow 8.1.2 or later. To address this issue, if encountered, see Partner Place answer 73601.
If a downgrade to Prinergy 8.1.2 is required after upgrading to 9.0.0, errors may be encountered with creating jobs in the downgraded 8.1.2 server.
If you encounter this problem, contact your Kodak service representative to address the issue with your Prinergy system. [PRINERGY-46987]
After downgrading from Prinergy 8.4.0 to Prinergy 8.1.2, Setup needs to be re-installed to function correctly. [PRINERGY-48872]
McAfee 10.5.3 / 10.6 cannot be installed and run on Windows 2016 if Windows Defender is installed. This is a limitation of the McAfee anti-virus software that requires Windows Defender to be uninstalled on systems you wish to install McAfee on. [PRINERGY-48947]
The first time you attempt to add an output device in Prinergy Administrator after restarting the server Prinergy is running on, Prinergy Administrator may crash. You will be able to add the device successfully after restarting the Prinergy Administrator interface.[PRINERGY-48874]
Acrobat 2017 and 2020 are one-time purchase release updates of Acrobat DC (similar to the original Acrobat 2015 release). The Prinergy Workshop installer does not detect the folder location for Acrobat 2017 or 2020. If you are using the version of Acrobat DC that is sold and labeled as Acrobat 2017 or 2020, you will need to manually install the Acrobat DC plugins in Acrobat 2017 or 2020.
See Partner Place Answer ID 74309 for plugins and manual installation instructions.
Exported jobs from Prinergy 9.x that contain Preflight+ XML reports cannot be imported into Prinergy 7.x.
Copy job does not keep page alias assigned to pageset when copying jobs on the same server or between servers. [PRINERGY-49619]
Dynamic Visible columns shift position (eg: move to the right or left). [PRINERGY-52293]