Unserved License Deployment Models

Resolve problems with unserved licenses.

Possible Causes Solutions
The license for the product or feature you are using is not in the local licenses directory. The local license directory is product-specific, and the license must be deployed to the correct location for the product. Typically, this directory is $SYBASE/SYSAM-2_0/licenses. Generate the required unserved licenses from SPDC or SMP and deploy them.
Your product’s license may have been activated with the incorrect host ID for the machine on which you are running the product.
  1. Check the license back in to SPDC or SMP.
  2. Regenerate the license at SPDC or SMP with the correct host ID.
  3. Install the license to the local machine where you are running your instance of the SySAM 2-enabled Sybase product.
The available licenses are for a different operating system or architecture than the machine on which you are running your product feature.
Obtain a license for the correct platform from SPDC.
  1. Check the license back in to SPDC.
  2. Generate a license for the correct platform, or install the product on the correct platform.
  3. Deploy a license to the local machine where you are running your instance of the Sybase product.
Note: Licenses generated from SMP are platform-independent.
You are running your SySAM 2-enabled program in a terminal services (TS) environment with an unserved Standalone Seat (SS) license.
Set up served licenses for a terminal server environment:

  1. Log in to SPDC or SMP and check in your old license.

  2. Generate served licenses and deploy them to a license server.

  3. Configure the product to obtain licenses from the license server.

If the output from running sysam diag feature_name states that a license for your product or feature is available for checkout, you still may be unable to check out the license because your product has been configured as a specific edition or with a specific license type. For example, the product is configured to look for an Adaptive Server® Enterprise, Enterprise Edition license, but only an Adaptive Server Enterprise, Developer Edition license is available; or, the product is configured to use a Server License (SR) license type, but only a CPU License (CP) is available.

Another incompatibility may occur if your product has several editions, and you are trying to run a separately licensed feature from one edition with the base product of a different edition. You can run an Enterprise Edition base product only with an Enterprise Edition separately-licensed feature; you cannot run a Developer Edition feature with an Enterprise Edition base product.

 If the problem is incompatible editions or license types, reconfigure your product, or go to SPDC or SMP and check in the incorrect license and regenerate a license for the correct edition or license type.
Parent topic: SySAM Problems and Solutions