Problems and Solutions for SAP Mobile Platform

Troubleshoot SySAM issues that are specific to SAP Mobile Platform.

Troubleshooting SySAM
Problem	Resolution
With a served license, SAP Mobile Platform Runtime installer generates a license checkout failure error and cannot complete the installation.	This is most likely due to unavailability of a port for the license server's VENDOR SYBASE daemon to use in communicating with SAP Mobile Platform. Check the entries in the sybase.log file in the SYSAM-2_0\log directory where the SySAM license server is installed. Locate the line containing "FLEXnet Licensing." Your log file may look similar to this: 11:20:27 (lmgrd) FLEXnet Licensing (v11.6.1.0 ... 11:20:27 (lmgrd) Copyright (c) 1988-2008 Acresso ... 11:20:27 (lmgrd) US Patents 5,390,297 and 5,671,412. 11:20:27 (lmgrd) World Wide Web: http://... 11:20:27 (lmgrd) lmdown/lmreread only allowed on ... 11:20:27 (lmgrd) License file(s): .../licenses/... 11:20:27 (lmgrd) lmgrd tcp-port 27000 11:20:27 (lmgrd) Starting vendor daemons ... 11:20:27 (lmgrd) Started SYBASE (internet ... About 6 lines below the "FLEXnet Licensing" line is a line containing "lmgrd tcp-port," and just below that should be a line containing "Started SYBASE." If you do not see the "Started SYBASE" line, it indicates that the license server started without successfully opening a port for the VENDOR SYBASE daemon. Contact your network security administrator and arrange for a port number to be available, then restart the license server. Check the sybase.log file again to be sure that the port was successfully opened. If you see the "Started SYBASE" line, with no error messages, it indicates that the license server successfully opened a port for the VENDOR SYBASE daemon. Edit this port number from the "lmgrd tcp-port" line into your SAP Mobile Platform license file.
SAP Mobile Platform does not start, and generates a license checkout failure error.	If SAP Mobile Platform cannot check out the required license, it determines whether the license can be issued in grace mode. If a grace period cannot be given, the license is not granted. If the base license for SAP Mobile Platform (`SUP_ENTSRVR`, for Enterprise Edition, `SUP_ENTDEV` for Enterprise Developer Edition, or `SUP_DEVELOPER` for Personal Developer Edition) was in grace mode and the issue is not fixed by the end of the grace period, SAP Mobile Platform fails to start. See SAP Mobile Platform cannot check out a license and starts with license in grace mode in this table. The troubleshooting tips for resolving licenses issued in grace mode apply to this issue as well.
SAP Mobile Platform cannot check out a license and starts with license in grace mode.	Execute the sysam diag feature_name command from the SySAM bin directory, where `feature_name` is the SySAM feature name for SAP Mobile Platform or the optional feature that is in grace mode. The feature name is printed in the SAP Mobile Platform error log and in the optional e-mail notifications. If the diag command shows that there are no licenses available to be checked out, it may be due to one of these reasons: If you are using a served model: Verify that the license server is running and reachable from the machine you are using. Use `sysam status` to verify that you can access the license server. If you cannot access the license server, make sure it is running. If the license server is running, use `sysam status -f feature_name` to determine whether the license server is serving a license for the given feature. If not, obtain the correct licenses from SPDC or SMP. All licenses on the license server may be in use. If `sysam status -f feature_name` indicates that no licenses are available, obtain additional licenses or shut down existing instances of SAP Mobile Platform. If you are using an unserved model: The license for the given feature may not be in the local licenses directory. Obtain the correct licenses from SPDC or SMP and copy them to the local licenses directory. The license may have been activated for a different machine or with an incorrect host ID. Check the license back in to SPDC or SMP and reactivate it with the correct host ID. The available licenses are for a different operating system or architecture. Obtain license for the correct platform from SPDC or SMP. If you are running in a terminal server environment, you cannot use unserved licenses. Set up served licenses. The available license may not authorize use of this version of SAP Mobile Platform. For information about date based versioning, see Installing Product Updates, EBFs, and Support Renewal in the SySAM Users Guide.
SAP Mobile Platform cannot check out a license and starts with license in grace mode (continued).	If the diag command shows that the license for the given feature is available, SAP Mobile Platform may not be able to check it out because: The product edition or license type does not match the requirement. If the product edition and license type configuration parameters are set, SAP Mobile Platform uses only the license that matches these settings. Also see “SAP Mobile Platform cannot find license for optional feature, even though the license exists” in this table.
SAP Mobile Platform shows licenses as being in grace mode even after the issue has been fixed	SAP Mobile Platform periodically performs license checks, and the license status is updated only after the next heartbeat cycle is completed. This may take a few hours.
SAP Mobile Platform cannot find license for an optional feature, even though the license exists.	Execute `"sysam diag feature_name"` to ensure that license for the optional feature exists and can be checked out from the machine on which SAP Mobile Platform is running. If the feature exists, but cannot be checked out from SAP Mobile Platform, it may be because: The optional feature is for a different edition. The active or standby flags do not match for the base server license for SAP Mobile Platform and the optional feature.
SAP Mobile Platform does not start with the expected edition or license type.	If the edition and license type configuration parameters are not set, SAP Mobile Platform uses the first available base license (`SUP_ENTSRVR`, for Enterprise Edition, `SUP_ENTDEV` for Enterprise Developer Edition, or `SUP_DEVELOPER` for Personal Developer Edition). If you have multiple base licenses with different editions and license types, the first-available license depends on many factors, such as license file directory sort order, available licenses on the license server, and so on. The product edition and license type that are granted by SySAM cannot be guaranteed. SAP recommends that you set the edition and license type configuration parameters. During installation, you set these parameters on the license details page, following acceptance of the end-user license agreement. When these parameters are set, SAP Mobile Platform starts with that configuration. If a matching license is unavailable, SAP Mobile Platform starts in grace mode (if available) to allow you to resolve the licensing issue.