If any of the Esko apps do not find the Eskobackstage or need access to the shares, follow these instructions to set a Windows Environment Variable. If Curve Pilot and Packedge use only the local (C:/ …) area to save and get curves, that is a bad way to set up the system.
Esko server variable. <<pdf file
KB76719617: Automation Engine – How to set up the BG_SERVER variable
How to set up the BG_SERVER environment variable?
When the BG_SERVER environment variable is set-up, the server will know which Automation Engine Server to use. As a consequence, systems having the BG_SERVER variable will find the central resource data the Automation Engine Server is using such as:
This prevents the use of local resource files.
Automation Engine no longer needs the BG_SERVER environment variable to work correctly (from Suite 12.1.0 onwards).
During a new installation of the FlexRip/FlexProof from the DVD (if no existing BG_SERVER variable is detected), a window will pop up asking to fill the name of the Automation Engine Server. When filled in, the correct environment is set up. Otherwise, you would continue working with the local resources.
If you want to set it up later or change the server name, go to Start > Esko > FlexRipConfig 12.1 (or later) > Select Server.
Color Engine Pilot – Curve Pilot – CIPress
If you install these applications on a computer without FlexRip or FlexProof (otherwise the previous procedure can be used), you have to set up the environment variable manually. To setup, follow the steps given below:
Make sure you are logged on as a user with administrative rights.
Open the Windows Explorer.
Go to My Computer.
Right-click and select Properties.
Go to the Advanced system settings and click the Environment Variables button.
Esko server variable in the System Variables section, click the New button.
Set Variable name: BG_SERVER
Set Variable value: name of the server ( e.g. AEserver)
Your variable BG_SERVER will be set.