If the product does not install or does not function after installation, check for a solution before contacting Technical Support.
Error | Possible Causes | Solution |
---|---|---|
Installation warning: cannot find a valid license. | You may not have the required licenses installed, or the licenses may be incorrect for the product or feature you are trying to install. |
See Installing for the First Time in the SySAM Users Guide. |
Cannot install Adaptive Server, or Adaptive Server does not start in a virtual environment. |
When this occurs, Adaptive Server reports an error similar to
this:
Cannot determine the total number of processor cores on the machine from within this virtual system. The ASE_CORE ("CH") license type is restricted for use on a machine with a maximum of 2 processor chips regardless of whether the virtual system is limited to use fewer processor chips. You need to run 'sysamcap' on the physical machine (or virtual-machine/partition control domain) and set the reported environment variable prior to running Installer. Either:
|
See the SySAM Sub-capacity licensing section of the SySAM Users Guide for more information. |
Updating an existing installation. | Make sure your license authorizes you to install the update. See Installing Product Updates, EBFs, and Support Renewal in the SySAM Users Guide. If your license does not allow you to perform the update, the product may not be usable. | If you are installing an update that is authorized by the license, see the solution for Product cannot check out a license and starts in grace period, below, before you proceed with the update. |
License server executables and scripts not installed. | When you installed your product, the license server was not installed. Some product installations offer the option to install a license server; however when available, this option, by default, is not selected for installation. You may need to explicitly install a license server. See your product installation guide and release bulletin to determine if the product installer offers this option. |
Use one of the following solutions:
|
License server does not start. | See Possible Causes of a License Server Failure in the SySAM Users Guide. | Go to SAP Service Marketplace (SMP) or Sybase Product Download Center (SPDC), generate a valid served license for your product, and copy it into the licenses directory on the machine where the license server is installed. See Generating Licenses at SMP or Generating Licenses at SPDC. |
License server does not recognize the license files. |
|
|
Linux virtual machine does not appear to be part of the Microsoft Hyper-V host. | /usr/sbin/dmidecode in Linux virtual machine cannot read from /dev/mem. | Log in to Linux virtual machine as root, then execute chmod 4555 /usr/sbin/dmidecode. |
Product does not start, license checkout error. |
|
At a command prompt or in a terminal window, execute the following commands, where feature_name is the name of the feature for which SySAM failed to check out a license: sysam diag feature_name If the SySAM script is unavailable, enter: lmutil lmdiag -c license_directory_location feature_name Go to SMP or SPDC and generate required licenses for your product. To use a separately licensable optional feature, you must have a license for both the base product and the option. If the product has more than one edition, the edition of the base product and option must be the same. If you generated an invalid license, check in the license at SMP or SPDC, and regenerate the license with the correct information. |
Product cannot check out a license and starts in grace mode. |
To help you determine the possible causes when your
product cannot check out a license, execute the following command
from the SYSAM-2_0/bin
directory, at a Windows command prompt or in a UNIX system terminal
window, where feature_name is
the name of the feature license that cannot be checked out.
sysam diag feature_nameIf the command output says that no licenses are available for checkout, this may be due to an issue with with a deployment model. See Unserved License Deployment Models and Served License Deployment Models. |
See Served License Deployment Models or Unserved License Deployment Models, both in the SySAM Users Guide. |
Product continues to run in grace meriod after fixing a license problem. | The license status has not yet been updated. When the product periodically performs license checks, the license status is not immediately updated. | Wait up to 6 hours for server products, and up to 1.5 hours for tool products. |
Product cannot find licenses for optional features. | You either have not installed the license for the optional feature, or the license exists, but cannot be checked out. | See Solution for Problem: Product Cannot Find Licenses for Optional Features in the SySAM Users Guide. |
Product obtains the wrong license. |
These locations are searched, in the order
specified, until a suitable license is found. When a license
directory is specified, license files in that directory are loaded
in the directory sort order. When a product looks for a license, it
looks in:
The first license that matches the feature name, version, edition, and license type filter is used; however, this license may not be the intended license your product requested. |
|
lmgrd is not running: Cannot connect to license server system. The license server manager (lmgrd) has not been started yet, the wrong port@host or license file is being used, or the port or host name in the license file has been changed. | One or more of the required executables is not present in the expected location. |
If SySAM is running on any OS that requires IPv6
(Windows 2008 Server, for example) make these changes:
|
License checkout problems with unserved license. | See Unserved License Deployment Models in the SySAM Users Guide. | |
License checkout problems with served license. | See Served License Deployment Models in the SySAM Users Guide. | |
Running SySAM utilities such as sysamcap or cpuinfo in a non-English environment can produce an error message. | The SySAM utilities can display a message similar to the following,
in English, even if the files to which they refer are
present:Failed to open the localised message file '../locales/unicode/sylapi/zh/cn/sylapi.lcu' (il8nuni_FileOpen returned -479) |
You can safely ignore the message, or prevent it from displaying by
setting this environment variable before running the
utility:LANG=en_US |