After upgrading to Suite 12.1.1 from a version lower than the Suite 12.1, Color Engine Pilot does not see all the Color Strategies.
The Automation Engine proof ticket/workflow shows the color strategy I want to proof with, but the proof task ends in error. When checking the Color Engine Pilot, the Color Strategies does not show the color strategy I selected.
Setting up the environment variable BG_SERVER does not resolve the issue. Re-installing the Color Engine Pilot after setting up the variable BG_SERVER does not help.
The post-installation procedure of Color Engine Pilot 12.1.1, where the Color Engine Pilot 12.1.1 resources are registered on the server, is not ran at installation time.
For information on setting up the BG_SERVER variable, see:
The Research and Development department of Esko is planning to implement the possibility to redirect to the central resources in the Color Engine Pilot. The aim is to get this implemented in Suite 12 Assembly 5 (Suite 12.2).
After upgrading to Suite 12.x, the Color Engine Pilot does not see the CMS data tree of the general resources but in the local system. The Automation Engine however looks at the central resource.
To resolve this issue, set up the following System Environment variable:
Variable Name - BG_DATA_CMS_V010
Value - \\hostname\bg_data_cms_v010 (where, hostname is the name of your central resources server).
The DGC curves implemented in the Color Strategies are not found. To avoid this, set up the following System Environment variable:
Variable Name - BG_DATA_DGC_V010
Value - \\hostname\bg_data_dgc_v010 (where, hostname is the name of your central resources server).