Learn about known issues and apply workarounds for SAP Mobile Platform Runtime components.
| Issue # | Description |
|---|---|
RTC-113 | Login fails when the value of the "tm_max_no"
parameter in the SAP® EIS is less than the number of users concurrently
logged in. The value of the tm_max_no parameter in the SAP EIS limits the maximum number of active logins. If the number of concurrent users logged in is larger than this value, SAP Mobile Server shows a R3_LOGIN_FAILED error. Workaround: Increase the value of the tm_max_no parameter in the SAP EIS to a suitable value. |
CR-717585 |
When assigning a personalization key using binary datatype to an operation
argument or load argument with BigBinary type, if the data in the
personalization key exceeds 35K, the server throws exceptions during
synchronization:
[LNSupController+Finalize.m:61] Send data ExceptionSUPPersistenceException: SUPPersistenceException from synchronize: -- SUPSynchronizeException: loginFail,Sync failed: -1497 (ERROR) %1:4 %2:4000 Workaround:When a binary personalization is assigned to an operation argument or a load argument, its size cannot exceed 35K. Additionally, do not map a personalization key to big object types such as BigString or BigBinary. The length of all personalization key values combined is a maximum of 64,000 bytes. Binary values are base64 encoded, so their length must be multiplied by 1.5 to account for encoding overhead. |
CR-714679 | SAP Control Center stops responding and shows Connecting with the SCC Managed Object Server
message after login. Workaround: Instead of using the standard URL (https:// < hostname > :8283/scc), if you are accessing SAP Control Center from the same host, use https://localhost:8283/scc or https:// < host name.domain > :8283/scc. Alternatively, try accessing SAP Control Center from a remote machine. |