Client Application Hangs Waiting for Authentication

Problem: The client application hangs on the login screen, while waiting for authentication from Unwired Server. The application eventually times out and returns an authentication error: Failed to obtain ${licenseNumber}license(s) for SUP_BASECLIENT feature from License Server ${server_id}.

Explanation 1: This message is from SySam and indicates your site is using more client licences than your purchased SySam license allows.

Solution:
  1. Check the Unwired Server log, and look for a checking out licenses error, for example: Failed to obtain 20 license(s) for SUP_BASECLIENT feature from License Server <server_id>.

  2. Check your license file and find the license type. This file sample shows that only 10 licenses are allowed (CP=10):
    INCREMENT SUP_BASECLIENT SYBASE 2011.03312 31-mar-2011 uncounted \
    VENDOR_STRING=PE=EE;LT=CP HOSTID=00-1A-A0-36-D4-3F ISSUER="CO=Sybase, \
    Inc.;V=1.5;AS=A;MP=365;CP=10;" ISSUED=20-jan-2010 NOTICE="For \
    Sybase Inc. Internal Testing Use Only" SN=12727 TS_OK \
    SIGN2="177C E3EA A4AF 4D7F F470 D299 E7B2 215F 8EBB 76A3 0717 \
    FC2F ED9B A795 BE18 05FB 1871 6352 46D8 1FB7 EAE4 EDB1 CF70 \
    CF6E 970A 6F51 2121 8044 57D9 B87F"

    This example indicates there is a mismatch between the number of client licenses (20) and the number of Unwired Server licenses allowed (10), so Unwired Server does not authenticate.

  3. Reconfigure the license by using license.bat, for example: license.bat EE CP 10
  4. Contact Sybase to correct the license problem.

Explanation 2: This could occur when more device clients are activated and used, than the number of client licenses available.

Solution:
  1. Check the Unwired Server log, and look for a checking out licenses error, for example: The number of registered devices has reached the maximum limit for your license..

  2. Contact Sybase to purchase more licenses. Once purchased, run the license.bat file again.

Explanation 3: This could occur if you have not generated server or client licenses correctly.

Solution:
  1. Check your sup.properties file to see your license configuration:
       license.product.edition=EE
       license.type=CP
       client.licenses=0

    In this example, 0 indicates there are no client licenses.

  2. Check the Sybase Unwired Platform Installation Guide for information about generating and downloading license files. See the section starting with: http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc00838.0152/doc/html/eka1250809241052.html.
  3. Contact Sybase to correct persistent licensing problems.

Explanation x: This message is from SySam and indicates your site is using more client licences than your purchased SySam license allows.

Solution:
  1. Check your sup.properties file to see your license configuration:
       license.product.edition=EE
       license.type=CP
       client.licenses=-1

    The client.licenses parameter refers to the number of licensed devices. A value of -1 indicates there is no limit to the number of devices.

  2. Check the Unwired Server log, and look for a checking out licenses error, for example: Failed to obtain 2147483647 license(s) for SUP_BASECLIENT feature from License Server 27001@mmdfwmapp299.mm.local.

    This example indicates there is a mismatch between the number of client licenses and the number of Unwired Server licenses, so Unwired Server does not authenticate.

  3. Check the license folder and find the license type. For example, you might find the type is ED (and not EE). This means the license configuration must be reset in order for Unwired Server to check out the right client licenses.
  4. Contact Sybase to correct the license problem.
Related concepts
Troubleshooting Host Name Problems
Listeners or Services Could Not be Started Errors
Related tasks
Handling Intrusion Detection/Prevention Software
Cannot Access Device Tab and Web Service Error
Cannot Access sampledb
Related reference
Sybase Unwired Server Service Fails to Restart After Credential Change
System Environment Path is Too Long
Performance Issues if Unwired Server Not Installed on a 64-bit Machine
Unwired Server or RSOE Startup Problems
.NET Environment Problems Affect Unwired Server