Known Issues for the Replication Agent Installer

Learn about known issues and workarounds for the Replication Agent installer.

Replication Agent Installer Issues
CR#	Description
641256	The Replication Agent installation fails on Sun platforms when the Logical Domains Manager (LDoms) does not exist. During installation, you may see several `Failed to connect to logical domain manager: Connection refused` messages before an exception occurs. Workaround: Perform one of the following: If `/opt/SUNWldm/bin/ldm ls -l -p` does not work, remove LDM. In the SySAM properties file, set SYBASE_SAM_CPUINFO to OSCMDFORK before running the installer to change how LDoms is called. Remove SYBASE_SAM_CPUINFO after installation.
631310	The SySAM lmgrd daemon is not installed unless you provide a served license during installation. Workaround: To install a SySAM server during the installation of Replication Agent 15.6, specify a served license. To install a SySAM server without running the Replication Agent 15.6 installer, invoke the SySAM server installer directly from the archives directory of the Replication Agent 15.6 installation media: On Windows: archives\sysam_server\setup.exe LAX_VM %JAVA_HOME%\bin\java.exe On UNIX: archives/sysam_server/setup.bin LAX_VM $JAVA_HOME/bin/java Note: If you do not have access to a Java installation, run the Replication Agent 15.6 installer and a suitable JRE will be installed. You can reference this JRE through the SYBASE_JRE6 environment variable.
625227	SPDC-generated served partition-level licenses may not work. When you use a served partition-level license generated from the Sybase Product Download Center to start a SySAM server, you see a message that you are using an invalid license key, similar to: (SYBASE) Invalid license key (inconsistent authentication code) ... (SYBASE) License server system started on hpiabou (SYBASE) No features to serve, exiting (SYBASE) EXITING DUE TO SIGNAL 49 Exit reason 4 (lmgrd) SYBASE exited with status 49 (No features to serve) (lmgrd) SYBASE daemon found no features. Please correct (lmgrd) license file and re-start daemons. (lmgrd) (lmgrd) This may be due to the fact that you are using (lmgrd) a different license file from the one you expect. (lmgrd) Check to make sure that: (lmgrd) /remote/cat_fc/nli/iq152.hpia/SYSAM-2_0/licenses/18965_hpiabou_ (lmgrd) is the license file you want to use. Workaround: Use the old host IDs for the license running on the license server.
622349	Licenses directory is not always created. When you install Replication Agent using an unserved license, licenses, the default license directory, is not created. Because Replication Agent does not have access to the license file, it uses the grace license, which expires after 30 days. Workaround: Manually create the licenses directory in $SYBASE/SYSAM-2_0. Copy the unserved license to the licenses directory. Restart Replication Agent.
618407	Issues when installing using a served license. When you install Replication Agent using a served license, SySAM Utilities is installed twice, and two copies of the Java Runtime Environment (JRE) are installed. These issues do not impact the Replication Agent and can be ignored. Workaround: None.
616338	Issues when reinstalling Replication Agent on IBM AIX. Reinstalling Replication Agent on IBM AIX after you create, start, and stop a Replication Agent instance results in an error from the installation program. This error does not affect subsequent Replication Agent instances and can be ignored. Workaround: None.
615072	SySAM Server and SySAM Utilities installation information not displayed. When you install Replication Agent with a served license, the SySAM Utilities and SySAM Server Install screen should display the installation progress of the SySAM components. However, when you install in console or GUI mode on a Windows XP or Windows 2003 machine, the SySAM Utilities and SySAM Server Install screen does not display the expected information. Workaround: Wait for the Sybase Software Asset Management screen to appear and continue with your installation. The installation program has installed the SySAM components even if the progress bar had not been shown.
614944	Replication Agent is installed with a served license even if a SySAM server is already running. When installing in console mode on Windows Vista, the installation program allows you to install Replication Agent with a served license even if a SySAM server is already running. The correct behavior is for the installation program to stop the installation process with this error: Error: The license key(s) you entered requires a Sybase Software Asset Management (SySAM) license server. The installer has detected a SySAM license server running on this host. Only one SySAM server can be setup on a system. You need to deploy the served-license key(s) to the existing server. Workaround: When installing Replication Agent in console mode on Windows Vista, change the compatibility mode of the console installer to Windows XP: In Windows Explorer, right-click setupConsole.exe. Select Properties. On the Compatibility tab, select the Windows XP compatibility mode. Launch the installation program using: setupConsole.exe -i console
614742	Available License Check window does not display correct database name. When you enter an invalid license on the Sybase Software Asset Management License Panel and click Next, you will see this message in the Available License Check window: Replication Agent for `database_type`, license not found If you click Previous, change the database type, and click Next, the error message displays again if the license is still invalid. However, the message does not reflect the new database type. Workaround: Ignore the message and ensure that you enter a valid license.
609606	An extra console opens when installing Replication Agent on Windows Vista. Installing Replication Agent in console mode on Windows Vista opens an extra console. Sybase recommends that you do not use this extra console. Workaround: To suppress the extra console, deactivate User Account Control (UAC) before running the installation program: Go to Control Panel \| User Accounts \| Turn User Account Control On or Off. Uncheck "Use User Account Control (UAC) to help protect your computer." Reboot your machine
606761	Cannot view text fields properly when using Hummingbird Exceed from a Windows workstation. If you use Hummingbird Exceed from a Windows workstation to install Replication Agent on a UNIX host, you might not be able to view all of the text fields on the Sybase installer screens. Workaround: Use a native X-Windows session to run the Sybase installation program, or run the Sybase installation program in console or silent mode. See the Replication Agent Installation Guide.
595614	Installation program cannot create installation directory on Microsoft Windows 2008. On Microsoft Windows 2008, the installation program can create the Replication Agent installation directory only when you are logged in as an administrator, even if your role has permission to create directories. Workaround: Create the installation directory before running the installation program.
595582	Installer fails to launch when path to setup.bin contains “..”. On UNIX and Linux platforms, the installer fails to launch if you specify a path to setup.bin that contains “..”. Workaround: Ensure that the path to setup.bin does not contain “..”.
595573	Uninstallation process stops responding. The uninstallation program stops responding when you select Delete from the Delete User Files screen and then click Previous from the Uninstall Complete screen. Delete User Files and Uninstall Complete are the last two screens shown in the uninstallation program. Workaround: Do not return to the Delete User Files screen after you have selected Delete.
594586	Inaccurate disk space information. The installation program displays inaccurate disk space requirement. Workaround: Refer to the Replication Agent Installation Guide for the correct disk space requirement for your platform.
593410	Installation program cannot uncompress the Replication Agent archive. On UNIX and Linux platforms, if you specify the tar utility from the GNU collection before the operating system-supplied tar utility in the $PATH environment variable, the GNU tar utility is invoked when you issue a tar command, and the installer fails with this error: The included VM could not be unarchived (TAR). Please try to download the installer again and make sure that you download using 'binary' mode. Please do not attempt to install this currently downloaded copy. Workaround: In the $PATH environment variable, specify the operating system-supplied tar utility before the GNU tar utility.
579988	`./setup.bin: !: not found` message appears when installing Replication Agent on Sun Solaris. You see this error message when you install Replication Agent on Sun Solaris: Preparing to install... ./setup.bin: !: not found Extracting the installation resources from the installer archive... Configuring the installer for this system's environment... Workaround: Ignore the message and continue.