Known Installation Issues for Adaptive Server

Learn about known installer issues and workarounds. Known issues are listed in descending order of Change Request (CR) numbers.

CR #	Description
629400	Installer incorrectly copies 64-bit JRE to Windows 32-bit. If the 32-bit Windows contains registry key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node, the installer incorrectly installs the 64-bit JRE. This registry key should not exist in 32-bit Windows, and prevents Windows from running any Java applications. Workaround: Go to Control Panel > System Properties > Advanced and: Set the environment variables for 32-bit JRE: `SYBASE_JRE6=<Installed Directory>\Shared\JRE-6_0_6_32BIT` `SYBASE_JRE6_32=<Installed Directory>\Shared\JRE-6_0_6_32BIT` Delete the 64-bit JRE environmenrt variable:`SYBASE_JRE6_64`
625837	Cannot share machine-level license by different Linux PowerPC operating systems on IBM logical partitions. The machine ID for Linux PowerPCs on IBM logical partitions is the virtual machine's MAC address, which means that SySAM cannot identify a unique machine ID for Linux on IBM logical partitions. Workaround: None. You cannot share a machine license among different operating systems.
625227	SPDC-generated served partition-level licenses may not work. When you use a served partition-level license generated from the SPDC to start a SySAM server, you see a message 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 host IDs from the previous version for the license running on the license server.
624640	Installer continues to show Chinese after selecting to show in English. When you select English to appear on the splash screen while running the installer in a Chinese locale, all the messages from your WebService configuration still appear in Chinese instead of in English. Workaround: Set the locale to English before running the installer.
624167	When you install Adaptive Server 15.5 ESD#1 in a non-English environment, the default installation type is Custom rather than Typical. Workaround: Use the Custom option. If you select Typical, the Additional Language Modules component is not installed, and some messages may not be localized.
624152	SySAM utilities may generate error message in non-English environment. When running the SySAM utilities sysamcap or cpuinfo in a non-English environment, you may see an error message similar to this, in English, even though you have sylapi.lcu installed: Failed to open the localised message file '../locales/unicode/sylapi/zh_cn/sylapi.lcu' (i18nuni_FileOpen returned -479). Workaround: You can safely ignore this message. To prevent the message from displaying altogether, set this environment variable before you run sysamcap or cpuinfo: LANG=en_US On Windows, set the UTF-8 codepage before you run the SySAM utilities with the command: chcp 65001
595614	Installer cannot create installer directory on Microsoft Windows 2008. On Microsoft Windows 2008, the installer can create the Adaptive Server installation directory only when you are logged in as an administrator, even if your role has permission to create directories. Workaround: Manually create the installation directory before running the installer.
595573	Uninstallation program 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. Workaround: Do not return to the Delete User Files screen after you have selected Delete.
593389	The 32-bit installer fails on Microsoft Windows Vista and Windows 2008 on x86-64 64-bit because the installer cannot set up the environment variables. Workaround: In Windows Explorer, right-click setup.exe or setupConsole.exe, and select Properties. On the Compatibility tab, select the Windows Vista compatibility mode. Add the environment variables by typing the text, or using Ctrl+V to paste the content into the text area, as clicking on SySAM License Panel > Browse does not work.
591746	Console-mode installations in Windows cannot validate served licenses. If you install a 32-bit installer package onto a 64-bit operating system in console mode, the console mode installer cannot correctly validate served licenses entered during installation. This results in license validation errors during installation. Workaround: Use the GUI installer instead.
590282	You cannot use the tab and arrow keys to navigate the Choose Product Features pane of the installation or uninstallation program. Workaround: Use the mouse to click in the Install or Uninstall window. This sets the focus on the window and allows you to navigate using your keyboard.
588793	Installing Adaptive Server 15.5 (which uses Install Anywhere) on older directories that have been installed with InstallShield Multiplatform can lead to incompatibility issues. These issues occur while using products installed with different installer technologies: If you install products using Install Anywhere or InstallShield Multiplatform on top of a product installed using the other installer, the same files included in both installers are silently overwritten by the later installation. If you run either the Install Anywhere or InstallShield Multiplatform uninstaller, the same files installed by both installers are removed without any indicating messages. Workaround: Do not install products that use Install Anywhere and products that use InstallShield Multiplatform in the same directory.
583979	Feature names are not validated when installing in silent mode. The installer does not validate feature names specified in the response file when you install in silent mode. Workaround: Ensure that the specified feature names are correct.