Known Issues for SAP Mobile Server
Learn about known issues and apply workarounds for SAP Mobile Server.
|
Issue #
|
Description
|
|
NA
|
SAP Mobile Server cannot properly augment the where clause of
a customized download SQL when the clause contains the "or"
keyword.
For example. The SQL
statement:
WHERE xxx OR yyy And this
augmentation is added:
aaa AND bbb The result of
the augmentation
is:
WHERE aaa AND bbb AND xxx OR yyy Which is
interpreted by the parser
as:
WHERE (aaa AND bbb AND xxx) OR yyy But the
desired interpretation
is:
WHERE aaa AND bbb AND (xxx OR yyy) Workaround:
Enclose the entire where clause in parentheses. For example,
from:
"WHERE xxx OR yyy" to:
"WHERE (xxx OR yyy)" |
|
BCP 012002523100002170812016
|
Do not perform and DCN operations against the
SAP Mobile Server while performing an upgrade to the
installation.
Performing any type of end-user work or processing any DCN requests by SAP Mobile Server during the upgrade process, can result in various error conditions. Workaround: Shut the SAP Mobile Server down before performing the upgrade. |
|
SMPONP-20000
|
Manually deleting the logs sub-folder from
aSAP Mobile Platform installation prevents
SAP Mobile Server from starting, since the 'SAP Mobile
Platform CacheDB' service requires this
sub-folder.
Workaround:Create a new logs sub-folder, then SAP Mobile Server starts successfully. |
|
N/A
|
Agentry clustering supported in Agentry version 6.0.X and earlier, is not
supported by SAP Mobile Platform version 2.3.x, which does not
support the same functionality as the Agentry configuration file
(Agentry.ini) for clustering.
Workaround: use the redesigned Agentry feature set in SAP Mobile Platform version 3.0.x that utilizes SAP Mobile Platform version 3.0.x clustering of the shared data and I/O. See this SAP note for more details: http://service.sap.com/sap/support/notes/2129430 |
|
SMPONP-18386
|
If you do not require the Introscope agent in your production environment,
you can uninstall it, but the application service server node fails to start
after uninstalling the Introscope agent.
Workaround: For application service server nodes:
|
|
SMPONP-17953
|
SAP Mobile Server hangs after querying or exporting data from
the monitor database if the amount of data is excessively large.
Workaround:Either: Workaround 1: The preferred workaround is to narrow the search interval of the query or export to about 5 to 10 minutes:
Workaround 2: Replace the monitor database and monitor log if
there is no meaningful data:
Workaround 3: Apply PATCH-10599 to purge all data. |
|
SMPONP-15180
|
Information remains in the clusterdb after uninstalling a cluster
node.
Server node still appears in SAP Control Center after uninstallation of the node. Workaround: This issue does not affect runtime behavior.
You can remove the server node completely by manually executing this SQL
script on the clusterdb database:
DELETE FROM PACKAGE_SYNC_DATA WHERE NODENAME IN (SELECT mp.VALUE1 FROM MEMBER_PROP AS mp, CLUSTER_MEMBER AS cm WHERE mp.NAME='sup.appservername' AND mp.MEMBERID = cm.MEMBERID AND cm.NAME LIKE '%###toDelete'); DELETE FROM SYNC_VERSION WHERE NODE_NAME IN (SELECT mp.VALUE1 FROM MEMBER_PROP AS mp, CLUSTER_MEMBER AS cm WHERE mp.NAME='sup.appservername' AND mp.MEMBERID = cm.MEMBERID AND cm.NAME LIKE '%###toDelete'); DELETE FROM installation_info WHERE host_name IN (SELECT mp.VALUE1 FROM MEMBER_PROP AS mp, CLUSTER_MEMBER AS cm WHERE mp.NAME='sup.host' AND mp.MEMBERID = cm.MEMBERID AND cm.NAME LIKE '%###toDelete'); DELETE FROM installation_history WHERE host_name IN (SELECT mp.VALUE1 FROM MEMBER_PROP AS mp, CLUSTER_MEMBER AS cm WHERE mp.NAME='sup.host' AND mp.MEMBERID = cm.MEMBERID AND cm.NAME LIKE '%###toDelete'); DELETE FROM MEMBER_PROP FROM MEMBER_PROP as mp, CLUSTER_MEMBER AS cm WHERE mp.MEMBERID = cm.MEMBERID AND cm.NAME LIKE '%###toDelete'; UPDATE CLUSTER_INSTALLATION SET HOSTNAME = HOSTNAME || '###toDelete' WHERE INSTALLID IN (SELECT cm.INSTALLID FROM CLUSTER_MEMBER AS cm WHERE cm.NAME LIKE '%###toDelete') DELETE FROM CLUSTER_MEMBER WHERE NAME LIKE '%###toDelete' DELETE FROM CLUSTER_INSTALLATION WHERE HOSTNAME LIKE '%###toDelete'; |
|
SMPONP-15176
|
In a shared host Microsoft cluster environment, Hazelcast selects the wrong
IP address when starting SAP Mobile Server, which prevents
the secondary server node from starting.
In these cases, a server log
message similar to this appears on the primary server
node:
2014-03-10 22:30:09.217 INFO Other main [com.hazelcast.impl.AddressPicker] [] [] Interfaces is disabled, trying to pick one address from TCP-IP config addresses: [] 2014-03-10 22:30:09.217 WARN Other main [com.hazelcast.impl.AddressPicker] [] [] Could not find a matching address to start with! Picking one of non-loopback addresses. 2014-03-10 22:30:09.504 INFO Other main [com.hazelcast.impl.AddressPicker] [] [] Picked Address [10.58.120.84] :5701 using socket ServerSocket [addr=/0:0:0:0:0:0:0:0,localport=5701] , bind any local is true 2014-03-10 22:30:10.156 INFO Other main [com.hazelcast.system] [] [] [10.58.120.84] :5701 [2.3.4_SHC_default] Hazelcast Community Edition 2.1.3 (20120723) starting at Address [10.58.120.84] :5701 Workaround: Either:
|
|
SMPONP-12328
|
jetty-web.xml was removed from
..\DCN\WEB-INF folder
Problem: DCN POST results in error message that the form is too large. Workaround: Set the maxFormContentSize property to
100 MB:
|
|
SMPONP-11956
|
Select socket timeout property
In the connection pool, select a socket timeout property from the drop-down list:
|
|
SMPONP-7973
|
Disregard "Error applying pending settings..." in logs under
..\APNSProvider and
..\BlackBerryNotifier
"Error applying pending settings, using old settings instead" messages can be found in ..\Servers\UnwiredServer\logs\APNSProvider and ..\Servers\UnwiredServer\logs\BlackBerryNotifier. Ignore these messages. |
|
CSN-2990597 2013
|
Certificate onboarding fails after upgrade
After upgrading to SAP Mobile Platform version 2.3 SP03, certificate onboarding will fail if certain obsolete properties remain configured. Workaround: Modify the security configuration in
SAP Control Center by removing the following properties:
|
|
SMPONP-10928
|
Temporary network issues affecting the cluster
During some operations, for example, deploying packages after switching a data tier in the Microsoft cluster, or failing to connect to the data tier in a simple cluster, a temporary network issue causes the following warning message to be logged in the server log: 2013-09-04 02:16:05.362 WARN MMS Thread-256 [com.sybase.sup.server.deploy.SupDeployer] [] [] System.Web.Services.Protocols.SoapException: Error sending request to server at Admin.AddTemplate(String strTemplateName, String strTemplateDescription, PropertyItem[] settings) java.lang.RuntimeException: System.Web.Services.Protocols.SoapException: Error sending request to server at Admin.AddTemplate(String strTemplateName, String strTemplateDescription, PropertyItem[] settings) at com.sybase.sup.admin.util.WebServiceUtil.createTemplate(WebServiceUtil.java:219) at com.sybase.sup.admin.util.WebServiceUtil.createTemplate(WebServiceUtil.java:209) at com.sybase.sup.server.deploy.SupDeployer.createTemplate(SupDeployer.java:797) at com.sybase.sup.server.deploy.SupDeployer.saveApplicationInfo(SupDeployer.java:776) at com.sybase.sup.server.deploy.SupDeployer.doDeploy(SupDeployer.java:734) at com.sybase.sup.server.deploy.SupDeployer.deploy(SupDeployer.java:306) at com.sybase.sup.admin.server.DomainAdminImpl.deployWithArgs(DomainAdminImpl.java:365) at com.sybase.sup.admin.server.DOECDomainAdminImpl_DJC.$invoke_0(DOECDomainAdminImpl_DJC.java:384) at com.sybase.sup.admin.server.DOECDomainAdminImpl_DJC.$invoke(DOECDomainAdminImpl_DJC.java:147) at com.sybase.djc.rmi.iiop.server.MessageHandler.processRequest(MessageHandler.java:794) at com.sybase.djc.rmi.iiop.server.MessageHandler.run(MessageHandler.java:306) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:789) Workaround: Redeploy the package after the cluster returns to normal. |
|
SMPONP-9999
|
When one SAP Mobile Server node in a cluster restarts, other
nodes may throw com.hazelcast.core.MemberLeftException.
Workaround: The cache's status recovers after a brief period of time or when the server restarts completely. The exception is temporary and can be ignored. |
|
SMPONP-8310
|
SAP Mobile Server experiences significant performance
degradation when performing DCN load operations with large DCN request
messages when Wily Introscope agents are enabled.
Workaround: If not required, remove the Introscope agents from SAP Mobile Server using this command:C:\SAP\MobilePlatform\Servers\UnwiredServer\bin\configure-introscope-agents.bat -remove |
|
SMPONP-1781
|
Server-name fails to start due to an expired certificate
The SAP Mobile Server cannot be started (the server shows started for a short time then shows stopped), and you receive the error "Stream Error: Internal error: ssl_AddTrustedCerts returned 4157" in the server log. This error occurs because a certificate expired in the client_trusted_cert.crt file. Workaround:
To resolve the issue by removing the expired certificate:
|
|
RTC-302
|
XML recordings are saved to an incorrect
directory.
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). |
|
RTC-268
|
Process of stopping SAP Mobile Server service hangs.
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. |
|
RTC-238
|
Update deployment allows definition of a new MBO attribute default, but the
new default value does not take effect.
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. |
|
RTC-42
|
Business transaction XML (BTX) uploads
when end-to-end tracing is not enabled for an application connection.
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. |
|
RTC-38
|
Server logs Chinese environments result in
garbled characters under certain conditions.
Due to an issue with SySAM licensing 64-bit operating systems running in a zh_CN locale result in characters appearing incorrectly. Workaround: None. |
|
N/A
|
Error: 584 Message: Server public key verification
failed when running the diagtool.exe tool.
Workaround: Either:
|
|
CR-709892
|
SAP Mobile Server records deployment errors in the domain log
rather than in the SAP Mobile Server logs.
Workaround: None. Look for deployment errors in the domain log. |
|
CR-708431
|
Data on the EIS, cache, and device is not
in sync.
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). |
|
CR-703515
|
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. |
|
CR-699590
|
Large messages are processed incorrectly on
32-bit runtime installations.
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. |
|
CR-699343
|
For native Object API applications, the
upgrade process silently deletes composite orphans from the server
cache.
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. Workaround:
Before upgrading, eliminate composite orphans from native Object API applications:
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. To be sure that composite orphans do
not cause problems in your migrated applications:
|
|
CR-695671
|
The mlsrv_err.log reports error: java.lang.OutOfMemoryError.
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. |
|
CRs 693116 and 692218
|
Devices on 3G/4G network cannot connect to
SAP Mobile Server.
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. |
|
CR-692374
|
Enabling compression incurs additional processing on the
device and the server side to optimize the amount of data to be
transferred over the network.
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. |
|
CR-691517
|
Adding new operations onto a mobile business object in a
deployed package using the Update
deployment method may render client applications based on the previous package
model version nonfunctional.
Workaround: None. |
|
CR-686043
|
In a disabled domain, messaging clients
continue to receive messages from server.
Workaround: To disable any outbound activity to a client, lock the application connection associated with that client. |
|
CR-576726
|
The full range of valid values is not
supported if an attribute uses the default datatype (int) for a SQL Anywhere® database column of
type unsigned int.
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. |
|
NA
|
When stopping the Windows service for SAP Mobile Server, very infrequently the process stops responding. This problem is independent of the means used to stop the service. When this happens, the process tree for the service for the SAP Mobile Server service is no longer intact, so you cannot use the Task Manager End Process Tree option to stop the service. Workaround:
|


