Known Issues for SAP Control Center

Learn about known issues and apply workarounds for SAP Control Center.

Issue # Description
SMPONP-9158
Unable to restart a remote SAP Mobile Server.

If a firewall blocks all UDP and TCP packets, attempts to use a local SAP Control Center to restart a remote SAP Mobile Server fail.

Workaround: Use the local SAP Control Center to restart the local SAP Mobile Server.

RTC-373
SAP Control Center shows "Unable to retrieve the child managed objects" error dialog when removing an MBO package.

Workaround: This problem is most likely caused when the SAP Control Center host machine network address has changed while the user is performing an operation in SAP Control Center. Close your browser session and relaunch the SAP Control Center URL.

RTC-309

If the user installs SAP Mobile Platform in the root directory of the file system (such as C:\), then the SLD data supplier fails to work.

Workaround: Avoid installing SAP Mobile Platform in the root directory of the file system.

RTC-221

Redeploying a package to SAP Mobile Server after changing a Cache Group policy from "Scheduled" to "On Demand" may result in SAP Control Center displaying an invalid cache interval.

Workaround: Update the cache interval in SAP Control Center.

CR-707565
Domain log purging can take a significant amount of time if too much data accumulates.

Workaround: Purge the domain log at regular intervals.

CR-705003
SAP Control Center does not ask user to delete packages and connections before deleting the domain.

Workaround: Before you delete a domain, verify package and connection deletion is not an issue.

CR-704917
If an administrator takes action from SAP Control Center while the primary server is being shut down, you may see an internal or unexpected error if the server has not completely shut down.

Workaround: Before taking any action in SAP Control Center, ensure that the primary server shutdown is complete and another server has taken over as the new primary.

CR-704913
When an iOS device goes offline, it continues to show as being online for about 8 minutes in SAP Control Center.

Workaround: None.

CR-703367
Domain log messages in Data Sync and Operation Replay subsystems are not logged to the default domain.

Workaround:

  • Create a domain log profile for the 'default' server connection (JDBC type) to enable logging of Data Sync and Operation Replay messages.
  • If you have a similar configuration, make changes as appropriate. Contact Technical Support for guidance.
CR-703321
Exporting a domain log after upgrading generates a Domain log export failed error message.

Workaround: Clear the cache for the browser you are using to access SAP Control Center.

CR-696373
When retrieving a domain log for large data, you receive an unknown error in SAP Control Center.

Workaround: Check whether the SAP Mobile Server or SAP Control Center agent.log reports an out of memory error. If so, increase the JVM heap size appropriately for SAP Mobile Server from the SAP Control Center Configuration tab.

If this does not resolve the issue, try decreasing the time range set in the domain log in SAP Control Center.

CR-695792
Suspending a large volume (100 or more) of DOE-C package subscriptions may cause SAP Mobile Server to stop responding.

Workaround: Suspend subscriptions in batches of no more than 50.

CR-691963
MBO package deployment in Update mode after adding a new load argument without default value succeeds even though deployment should fail.

Workaround: None. To avoid deploying client-incompatible changes, SAP recommends that you first use Verify mode deployment; if verify succeeds, proceed to Update mode deployment.

CR-690482
Using Firefox, the SAP Control Center main page shows Invalid Login and the agent.log shows Received fatal alert: bad_certificate error.
Workaround: The Firefox browser appears to be using an incorrect server certificate. Clean up any such previously existing certificates:
  1. in SAP Control Center, select Tools > Options > Advanced > View Certificates.
  2. Click the Servers tab, then identify existing certificates issued to the same host to which you are connecting.
  3. Click Delete to remove all such certificates. Alternatively, use Internet Explorer.
CR-683775
In some instances, when using the Windows Services tool or the Stop SAP Mobile Platform Services shortcut to stop the SAP Control Center3.2 service, SAP Control Center displays Stopping in the Windows Control Panel yet fails to stop.
Workaround: To stop the SAP Control Center service:
  1. Launch Windows Task Manager.
  2. Locate the sccservice.exe process, right-click and select End Process Tree. This option also kills the SAP Control Center database repository server process dbsrv11.exe.
Parent topic: Known Issues for SAP Mobile Platform Runtime 2.3 SP02