Known Installation Issues

Installation issues for this version of Event Stream Processor.

Known Installation Issues
CR#	Description
668057	If you install Event Stream Processor using InstallAnywhere in the same directory as older Sybase products that also use InstallShield, uninstalling one of the products may make other products unusable because some shared components are removed by the uninstaller. On a UNIX system, install Event Stream Processor in a separate directory. If you install Event Stream Processor in the same directory as older Sybase products, do not uninstall.
675054	The SySAM files are missing the writable permission if RepAgent 15.2 has been previously installed. Manually modify the file permissions for SySAM ($SYBASE/SYSAM-2_0/bin) after RepAgent 15.2 is installed, if you plan to install Event Stream Processor 5.1 into the same directory as RepAgent 15.2.
681675	When starting the SySAM license server, you may receive an error indicating failure to connect to the license server. This version of Sybase Event Stream Processor includes both Internet Protocol Version 4 (IPv4) and Internet Protocol Version 6 (IPv6) versions of the SySAM license server software. Use the sysam configuration command to choose the version of the license server based on your environment. By default, the IPv4 version of the license server is configured. This may result in an error if you have previously enabled IPv6 on the license server host. You can run both IPv6 and IPv4 on the same host by removing the IPv6 address from the hosts file.
716148, 716109 and 716131	Settings in a response file, generated by performing a Typical installation or by running the console installer, are not recognized when performing a silent installation. To work around this issue, generate a correct response file manually or by running the GUI installer and performing a Custom installation. Refer to the sample response file in the Installation Guide.
720308	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: `<ESP_install_dir> LAX_DEBUG=true; export LAX_DEBUG>`