Known Issues for Sybase Control Center Installation

Learn about known issues and apply workarounds for installing Sybase Control Center.

Change request number	Description
588793 614392	Different installer technologies for Sybase products overwrite existing program files. Sybase products use two different installer technologies: InstallAnywhere and InstallShield MultiPlatform. InstallAnywhere and InstallShield MultiPlatform installers place files and registration mechanisms in subdirectories with identical names. If you install two Sybase products that use different installer technologies in the same directory, the later installation might overwrite or incorrectly update files from the initial installation. For example, if the initial installation is Sybase Control Center, using the InstallAnywhere technology, and additional programs are installed on the same server using InstallShield MultiPlatform (for example Replication Server 15.2 and Adaptive Server Enterprise 15.0.3), InstallAnywhere installed files may be overwritten by the InstallShield MultiPlatform installation, causing the program not to function properly. Workaround: Select a unique installation directory if you are installing multiple Sybase programs on the same server. Sybase recommends that you do not install Sybase Control Center on a machine that is being used as a production server for any other product. Sybase Control Center collects and stores performance data for every server it monitors, using CPU cycles, network resources, and disk space in significant quantities. Running two (or more) servers on the same machine can result in unacceptable performance from all products.
613897	Installing Replication Server 15.2 on the Sybase Control Center server causes Sybase Control Center not to start. Because Replication Server 15.2 and Sybase Control Center use different installation technologies, Sybase Control Center environment variables are changed during the Replication Server installation. This causes Sybase Control Center not to start. Workaround: Reset the environment variables and restart Sybase Control Center. The environment variables to reset for each platform are: HP (Itanium) SYBASE_JRE6=$SYBASE/shared/JRE-6_0_1 SYBASE_JRE6_32=$SYBASE/shared/JRE-6_0_1 SYBASE_JRE6_64=$SYBASE/shared/JRE-6_0_1 AIX (POWER Series) SYBASE_JRE6=$SYBASE/shared/JRE-6_0_SR6_64BIT SYBASE_JRE6_64=$SYBASE/shared/JRE-6_0_SR6_64BIT Linux (x86-64) SYBASE_JRE6=$SYBASE/shared/JRE-6_0_17_32BIT (on 32-bit OS) SYBASE_JRE6=$SYBASE/shared/JRE-6_0_17_64BIT (on 64-bit OS) SYBASE_JRE6_32=$SYBASE/shared/JRE-6_0_17_32BIT SYBASE_JRE6_64=$SYBASE/shared/JRE-6_0_17_64BIT Windows (x86-64) SYBASE_JRE6=%SYBASE%\Shared\JRE-6_0_17_32BIT (on 32-bit OS) SYBASE_JRE6=%SYBASE%\Shared\JRE-6_0_17_64BIT (on 64-bit OS) SYBASE_JRE6_32=%SYBASE%\Shared\JRE-6_0_17_32BIT SYBASE_JRE6_64=%SYBASE%\Shared\JRE-6_0_17_64BIT Solaris (SPARC) SYBASE_JRE6=$SYBASE/shared/JRE-6_0_17 SYBASE_JRE6_32=$SYBASE/shared/JRE-6_0_17 SYBASE_JRE6_64=$SYBASE/shared/JRE-6_0_17 Alternatively, to avoid any overlap in the installed program files if you are installing multiple Sybase programs on the same server, select a unique directory.
617603	The Windows uninstaller may fail to remove SCC-3_1, the Sybase Control Center installation directory, because the file path is too long. If you try to remove the folder manually, the error is not informative—it says that about_files could not be deleted. Workaround: To remove the installation directory: Locate this folder: <SCC-install_dir>\services\EmbeddedWebContainer\container\Jetty-6.1.22\work\Jetty_0_0_0_0_8282_help.war__help__.smpe97 Shorten the path by changing the name of Jetty_0_0_0_0_8282_help.war__help__.smpe97 to a single character, such as j. Right-click the installation directory (SCC-3_1, by default) and select Delete.

Change request number

Description

588793

614392

Different installer technologies for Sybase products overwrite existing program files.

Sybase products use two different installer technologies: InstallAnywhere and InstallShield MultiPlatform. InstallAnywhere and InstallShield MultiPlatform installers place files and registration mechanisms in subdirectories with identical names. If you install two Sybase products that use different installer technologies in the same directory, the later installation might overwrite or incorrectly update files from the initial installation.

For example, if the initial installation is Sybase Control Center, using the InstallAnywhere technology, and additional programs are installed on the same server using InstallShield MultiPlatform (for example Replication Server 15.2 and Adaptive Server Enterprise 15.0.3), InstallAnywhere installed files may be overwritten by the InstallShield MultiPlatform installation, causing the program not to function properly.

Workaround: Select a unique installation directory if you are installing multiple Sybase programs on the same server.

Sybase recommends that you do not install Sybase Control Center on a machine that is being used as a production server for any other product. Sybase Control Center collects and stores performance data for every server it monitors, using CPU cycles, network resources, and disk space in significant quantities. Running two (or more) servers on the same machine can result in unacceptable performance from all products.

613897

Installing Replication Server 15.2 on the Sybase Control Center server causes Sybase Control Center not to start.

Because Replication Server 15.2 and Sybase Control Center use different installation technologies, Sybase Control Center environment variables are changed during the Replication Server installation. This causes Sybase Control Center not to start.

Workaround: Reset the environment variables and restart Sybase Control Center. The environment variables to reset for each platform are:

HP (Itanium)

SYBASE_JRE6=$SYBASE/shared/JRE-6_0_1
SYBASE_JRE6_32=$SYBASE/shared/JRE-6_0_1
SYBASE_JRE6_64=$SYBASE/shared/JRE-6_0_1

AIX (POWER Series)

SYBASE_JRE6=$SYBASE/shared/JRE-6_0_SR6_64BIT
SYBASE_JRE6_64=$SYBASE/shared/JRE-6_0_SR6_64BIT

Linux (x86-64)

SYBASE_JRE6=$SYBASE/shared/JRE-6_0_17_32BIT (on 32-bit OS)
SYBASE_JRE6=$SYBASE/shared/JRE-6_0_17_64BIT (on 64-bit OS)
SYBASE_JRE6_32=$SYBASE/shared/JRE-6_0_17_32BIT
SYBASE_JRE6_64=$SYBASE/shared/JRE-6_0_17_64BIT

Windows (x86-64)

SYBASE_JRE6=%SYBASE%\Shared\JRE-6_0_17_32BIT (on 32-bit OS)
SYBASE_JRE6=%SYBASE%\Shared\JRE-6_0_17_64BIT (on 64-bit OS)
SYBASE_JRE6_32=%SYBASE%\Shared\JRE-6_0_17_32BIT
SYBASE_JRE6_64=%SYBASE%\Shared\JRE-6_0_17_64BIT

Solaris (SPARC)

SYBASE_JRE6=$SYBASE/shared/JRE-6_0_17
SYBASE_JRE6_32=$SYBASE/shared/JRE-6_0_17
SYBASE_JRE6_64=$SYBASE/shared/JRE-6_0_17

Alternatively, to avoid any overlap in the installed program files if you are installing multiple Sybase programs on the same server, select a unique directory.

617603

The Windows uninstaller may fail to remove SCC-3_1, the Sybase Control Center installation directory, because the file path is too long.

If you try to remove the folder manually, the error is not informative—it says that about_files could not be deleted.

Workaround: To remove the installation directory:

Locate this folder:
<SCC-install_dir>\services\EmbeddedWebContainer\container\Jetty-6.1.22\work\Jetty_0_0_0_0_8282_help.war__help__.smpe97
Shorten the path by changing the name of Jetty_0_0_0_0_8282_help.war__help__.smpe97 to a single character, such as j.
Right-click the installation directory (SCC-3_1, by default) and select Delete.