Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Installation requirements


AIP Core is delivered in a ZIP file. Make sure you have the required ZIP file ready and unzipped to a folder on the AIP Node (it cannot be run from a network location). 

(tick)AIP Core needs to be installed on all AIP Nodes (i.e. dedicated servers) that will be managed by AIP Console. The installation process consists of running a setup installer on the target server.

Installation paths:

  • The CAST AIP setup can only be installed to a local or mapped drive
  • Paths starting with \\ will be refused by the setup and are not permitted.

Data storage paths / global settings:

  • All paths are accepted and are never checked by the CAST AIP setup. E.g. local full path, mapped drive, remote location starting with \\ are all accepted. Please ensure that the current user has access to these data storage locations.

You need local "Administrator" privileges to install AIP Core on all Windows versions. In addition, the installer requires elevated permissions and therefore needs to be run using the "Run as Administrator" option.


In some rare circumstances, the installer may appear to have completed, but a message will also be displayed as follows:

"The system has not been modified. To install this program at a later time, run the installation again."

This message indicates that the setup has failed. This can occur even when your user login has "Administrator" privileges. In order to workaround this, you need to assign your user login a specific Windows privilege entitled Impersonate a client after authentication.


The Windows login used to run the AIP Core installer cannot contain any special characters - for example:

  • !
  • %
  • |

If the Windows login contains a special character, the installation will fail. Note that the above list of special characters is not exhaustive.


Generally speaking, the installation path must only contain ASCII characters or characters of the language (or language group) of your Windows operating system. More precisely, all characters in the installation path must be present in the system Windows code page of the AIP Node. The system Windows code page is determined by the system locale. The system locale is defined in:

  • Control Panel > Clock and Region > Region > Administrative tab > Language for non-Unicode programs.

This language defaults to the language of the Windows operating system and can be changed, if needed.

As an example, on any western European Windows installation, the system code page is Win-1252; on central European Windows installations, the code page is Win-1250, and on a Turkish Windows installation, the code page is Win-1254. The exact value of the code page is stored in the Windows registry at the following location:

No Format

The value in the key 'ACP' indicates the current system Windows code page (also called ANSI Code Page, hence 'ACP'). If your installation path contains any character not present in the system Windows code page (e.g. a cyrillic Cyrillic character on a French Windows installation), all CAST Java based executables will fail to load due to a limitation of the Java runtime environment.

(tick)If you are facing issues installing AIP Core, you may consider temporarily disabling any anti-virus running on the host server. In some situations, anti-virus can interfere with the installation process and cause it not to complete.

Interactive installation process


  • Visual C++ 64-bit Redistributable Packages for Visual Studio 2017
  • Visual C++ 64-bit Redistributable Packages for Visual Studio 2013
  • Visual C++ 32-bit Redistributable Packages for Visual Studio 2013
  • Visual C++ 64-bit Redistributable Packages for Visual Studio 2010
  • Microsoft Build Tools 2015 (BuildTools_Full.exe)
  • .NET framework (when required - if a more recent version is already present, then nothing is installed)

    • AIP 8.3.0 - AIP 8.3.13: 4.5.2 

    • AIP 8.3.14 - 8.3.28: 4.7.1
    • AIP ≥ 8.3.29: 4.7.2

When running the AIP Core setup and a previous release is already present on the target workstation, the setup will NOT install the .NET Framework even if it (or a more recent version of the framework) is not present on the target server. In this scenario, it is the responsibility of the end-user to install the required .NET Framework.