Known Issues for SAP Mobile Server

The support agreement between Oracle and SAP is no longer in effect as of December 31, 2013.

Workaround: See SAP Note 1949332 for workaround and additional instructions.

Could Not Find [...] smp_server.lock

Workaround: You can safely ignore this error since it has no negative impact.

SAP Mobile Server fails to notify device after a DCN update.

If there is an unactivated manually registered application connection, the auto registered application connection with the same user name may not work because an internal SAP Mobile Server table (mms_application_connection_info) is not updated correctly, resulting in the above symptom.

Workaround: Re-register the application connection after deleting the manually registered one.

(Applies only to Agentry) In a cluster environment, starting the primary/secondary Application Service Node takes a long time. The Windows Services status keeps starting, and server logs show RuntimeException errors. The primary server finally starts successfully.

Earlier versions of SAP Mobile Platform allowed primary key attributes with NULL values, however, the use of NULL primary key attributes within the SAP Mobile Platform Runtime is not supported. Beginning with SAP Mobile Platform version 2.3, constraints prevent NULL primary key attributes from being inserted into the cache.

Workaround: If the EIS is currently generating NULL values for MBO primary key attributes, the EIS must provide a different mechanism to establish uniqueness.

Applications migrated from earlier versions of SAP Mobile Platform may need MBO primary key attribute analysis. In particular, analyse MBOs that have no primary keys defined (by default SAP Mobile Platform generates a primary key that contains all MBO attributes), or MBOs that have composite primary keys, to ensure that the EIS is not providing NULL values for these attributes.

For a composite operation, if the name of a child MBO in the composite relationship begins with lower case, deployment would fail. 

Workaround: Change the first character of the child MBO's name to upper case using Unwired WorkSpace.

After enabling XML recording in the registry, logs will show that XML recordings are successfully saved to C:\UnwiredServer\logs, which is the incorrect SAP Mobile Platform logging directory.

Workaround: Manually add a String Value to the key HKEY_LOCAL_MACHINE\SOFTWARE\Sybase\Sybase Messaging Server\Server (HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sybase\Sybase Messaging Server\Server on 64 bit) with a path relative to the MessagingServer directory (that is, ..\UnwiredServer\logs).

When stopping the Windows service for SAP Mobile Server, very infrequently the process hangs. This problem is independent of the means used to stop the service.

Workaround: See Process of Stopping SAP Mobile Server Service Hangs.

While the MBO developer can modify the MBO attribute default value for a deployed package, and redeploy the package to SAP Mobile Server in Update mode without an error or warning, the new default value does not take effect.

Workaround: Use Replace mode to update the MBO default setting.

You can still upload BTX to the configured Solution Manager server, even if you have not enabled end-to-end tracing for an application connection.

Workaround: None.

Due to an issue with SySAM licensing 64-bit operating systems running in a zh_CN locale result in characters appearing incorrectly.

Workaround: None.

Workaround: Either:

Workaround: None. Look for deployment errors in the domain log.

If a Create operation succeeds at the enterprise information system (EIS), but its corresponding Entity Read operation fails, the EIS is updated but the cache database (CDB) is not. Error information may be reported in the SAP Mobile Server log, but the error is not propagated to the device client. LogRecord shows 0 (zero), but findAll does not show the new record on the device.

Workaround: None. The change appears in the CDB and the device when the CDB is refreshed (for example, when the cache interval expires).

LDAP role/authentication search base cannot support special characters.

The following characters have special meaning when they appear in a name in LDAP: , (comma), = (equal sign), + (plus sign), < (less than), > (greater than), # (number sign), ; (semicolon), \ (backslash), and " (quotation mark).

LDAP providers do not currently handle these special characters in any names or DNs, including user name, DefaultSearchBase, AuthenticationSearchBase, RoleSearchBase, AuthenticationFilter, and RoleFilter.

Workaround: None.

Workaround: After deployment, adjust the "onDemand" coherence window from SAP Control Center.

A 32-bit SAP Mobile Server is not supported when you are developing messaging applications that process large messages. 32-bit servers run into memory issues and can potentially further result in incorrect data synchronizing with the SAP Mobile Server cache.

Workaround: Install SAP Mobile Platform runtime components on 64-bit hosts.

SAP Mobile Platform no longer allows composite orphans, that is MBO child entities within a composite relationship that have no parent entity. Depending on the system configuration, the upgrade may physically delete the orphans, or may only logically delete them, then physically delete them during a subsequent cache purge process. Either way, applications that use MBOs with composite orphans may not behave as expected after migration.

Additional Information on Composite Orphans

An example of a scenario in which parentless child entities can occur is a two MBO parent-child model integrated with JDBC for sales orders and line items. If the data model specifies that line items are inserted first, the application attempts to load child line items for a sales order that does not yet exist. Those line items disappear from the cache before the application can load the parent sales order.

When performing a listview object query with very large data sets, the client returns an error code 571 or 1053, and the server becomes temporarily unavailable, or tries to restart.

Workaround: Modify the maximum Java heap size to handle very large amounts of data in an object query. See Configuring SAP Mobile Server Performance Properties in System Administration.

A connectivity issue may occur between the device and SAP Mobile Server. The current client libraries use a protocol that support only HTTP chunked transfer-encoding. 3G/4G traffic might, in some cases, be subject to content filtering and convert the messages from chunked transfer-encoding to fixed content-length if communication is via standard HTTP ports, which most commonly are 80 and 8080. Since the client application can support only chunked transfer-encoding, the communication cannot be established. In effect, a response cannot be returned to the server indicating that the device is online.

Workaround: Use a nonstandard HTTP port (any port other than 80 or 8080) or an HTTPS port, that is, 443 for SAP Mobile Server client communication from devices to the Relay Server or external load balancer, whichever one is used, in the DMZ.

Workaround: Carefully evaluate whether the compression trade-off is appropriate in the deployment environment, and carefully size the server capacity to support it. If appropriate in a particular environment, follow the SAP Mobile Platform Developer Guides to enable compression.

Workaround: None.

Workaround: To disable any outbound activity to a client, lock the application connection associated with that client.

Workaround: To support the full range of valid values for an unsigned int attribute in the EIS, set the datatype for the corresponding MBO attribute as long.