| Error | Possible Reason | Solution |
|---|
| The Bridge installer stops and throws a "java heap space" error. | The Java heap space that has been allocated automatically by the system is not sufficient. | The Bridge installer needs about 1GB of Java heap space. Start the Bridge installer with option Xmx to provide more java heap space, e.g. java -Xmx1g -jar <Bridge Installer>. |
The Bridge installer cannot be started:
Error running installer.
java.lang.UnsatisfiedLinkError  | You are trying to run the installer with a 64-bit java version. | Start the Bridge installer with a 32 bit java version. |
The Bridge cannot be installed:
Error running installer.
com.ice.jni.registry.RegistryException 
| The user that is executing the installation does not have administration rights on the system. | Login with a user that has administration rights, e.g. user Administrator or root. |
| Start the Windows command processor (cmd.exe) with option Run as administrator. |
| The operating system installed is neither an English nor a German Windows distribution. | Install the Bridge on an English or a German operating system. |
| The operating system is not supported. | Make sure, that the operating system is supported (see the list of supported operating systems). |
| An older version of Bridge is already installed. | Uninstall the old Bridge first. |
| When selecting the installation directory, the error message The directory is not empty! is displayed. | A former Bridge installation has been found and cannot be updated, because it had been installed by another user. | Either uninstall the previous installation first, or login with the same user that has installed the previous installation. In the latter case, the Bridge Installer will update the Bridge installation. |
| The Windows service of the Bridge (E2E Console) is not listed in the Windows Services tool. | Bridge service E2E Console is deleted and recreated upon each Bridge update. It can happen, if you did not stop the Bridge server before applying the update and if the Bridge service took to long to stop, that deleting and recreating the service get crossed and the service is not created. | Re-apply the Bridge update. |
| The installation has failed. | Remove and re-install the Bridge. |
| The installer seems to be stalled while "Preparing filesystem". | The Bridge installer touches all files in the installation directories (Bridge_DATA and Bridge_PROG) to set the file access rights. If your Bridge installation contains many unnecessary legacy files, such as old Runtimes, trace or log files, etc., this may take a serious period of time on Windows operating systems. | Clean-up your Bridge installation. Delete the following: - old log and trace files from the Bridge_DATA directory
- old installation files from Bridge_PROG, such as Runtime, Node.js, JRE, Apache
|
| The Bridge does not start after installation or on system startup. | | On Linux systems, the Bridge system user needs a shell to start the Bridge daemon. |
| Change the Bridge system user as to have a shell. |
| Linux systems must use systemd to be able to start the Bridge after installation or on system startup. |
| Change the Linux installations as to use systemd. |