Learn about known installer issues and workarounds. Known issues are listed in descending order of Change Request (CR) numbers.
CR # | Description |
---|---|
684722 | When you uninstall an Adaptive Server that was installed using a non-English environment, the uninstaller displays this error message while uninstalling DBISQL: The JRE_DIRECTORY KEYWORD in the INI file points to a directory that does not contain JAVA.EXE. Workaround: Ignore the message. |
684019 |
While installing the installcommit script, Adaptive Servers with 2K page size fail to respond.
The Adaptive Server error log indicates that there is insufficient space in syslogs in the master database(Error 1105). Workaround: Increase the master database size from the default 13 MB to 15 MB before executing the installcommit script, or when configuring a new Adaptive Server. |
683068 |
Configuration of Job Scheduler fails on Windows with the error: Failed
to configure new Job Scheduler.
You see this error if your host machine is configured for multiple network
connections, and one of these two conditions exists:
Workaround:
|
678698 |
When you execute isql in an installation where Replication Server 15.6 is installed on top of Adaptive Server 15.7, you get this error: Could NOT locate the point entry of cs_locator_drop in libsybcs64.dll.
Workaround: Move <installed_directory>\OCS-15_0\dll, <installed_directory)\OCS-15_0\lib3p, and %SYBASE%\OCS-15_0\lib3p64 to the front of the %PATH% environment variable value. To do this, under tab, then click Environment Variables. In "System variables," select Path and click Edit. In "Variable value," find and paste the above directory names at the beginning of the variable. |
671844 |
Cannot start Sybase Central if RMP 15.2 is installed on top of Adaptive Server 15.7.
Workaround: Change the shortcut of the Sybase Central in the start menu to point to scjview.exe under %SYBASE%\shared\Sybase Central 6.0.0\win64. Start Sybase Central and then manually register the RMP plugin. |
670146 |
With Adaptive Server 15.7 installations, the served license cannot be checked out if IPv6 is installed.
Workaround:In the SySAM License Entry Panel, select Use previously deployed license server and replace the host name with the IPv4 address of the machine. |
625227 |
SPDC or SMP generated served partition-level licenses may not work.
When you use a served partition-level license generated from the SPDC or SMP
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 earlier Adaptive Server version for the license running on the license server. |
624167 |
When you install Adaptive Server 15.5 ESD #1 or later versions 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. |
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 and later versions (which use 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:
|
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. |