On the workstation where you have the Automation Engine Pilot installed, go to …Esko\bg_prog_fastservercltnt_v121\com_win and double click the cfsedt2.bat procedure.
You will be asked for a login on the server after which the Config Editor starts up.
If Color Engine Pilot 12.1 is not registered on the server, the Config Editor resources look as shown in the screenshot below:
On the workstation where the Color Engine Pilot 12.1 is installed , open Windows Explorer and go to … Esko\bg_prog_kaleidoscope_v121\com_win
Double click the post_install.bat file.
A command prompt opens, executes something and closes again.
Go again to the Config Editor on the workstation where you have the Automation Engine Pilot installed. If you had left the Config Editor open from before, just press F5 to refresh. The resources now look as shown in the screenshot below:
Now the resources of the application Color Engine Pilot 12.1 are registered on the server.
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 14 Assembly 1 (Suite 14.0), to be released in the 2nd quarter of 2014.
Esko reserves the right to change the contents and/or release date of the software release at any time.
If the steps to resolve do not work, you can perform the following as a workaround and inform Customer Services.
Set up the following System Environment variables:
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).