Known Installation Issues

If you install Event Stream Processor using InstallAnywhere in the same directory as older SAP products that also use InstallShield, uninstalling one of the products may make other products unusable because some shared components are removed by the uninstaller.

If you install Event Stream Processor in the same directory as older SAP products, do not uninstall.

When installing ASE 15.0.3 ESD#4 with ESP 5.1 already installed in the same diretory, if you execute $SYBASE\SYBASE.bat followed by isql -v, you may receive an error.

Backup SYBASE.bat before installing ASE 15.0.3 ESD #4.

When you are installing on Windows overtop of an existing Event Stream Processor 5.1 installation, and files from that installation are in use, the installer reboots the system at the end of the installation without warning.

The installer may hang or encounter issues without reporting an error condition. This is usually caused when the temporary directory has insufficient disk space.

To check the status and view messages of the installation, start a console install using the LAX_DEBUG environment variable. This is an installer debug environment variable that reports issues with the installation as they arise. To start a console install using this environment variable, use a command line to set its value to true prior to running the installer:

LAX_DEBUG=true; export LAX_DEBUG

If you disable SSL during a custom installation, the installer disables SSL at the cluster level, but not at the project level. As a result, only certain ESP client utilities, such as esp_cluster_admin and ESP Studio, are able to connect to the server until you disable SSL at the project level. To do this, comment out all of the lines containing references to either "ssl-key-file" or "ssl-key-file-encrypted" in the node1.xml cluster configuration file. Then, restart the cluster.

Note that this issue does not apply to Studio's localnode.xml file.