Known Issues for SAP Control Center
Learn about known issues and apply workarounds for SAP Control Center.
|
Issue #
|
Description
|
|
SMPONP-18075
|
Known issues related to Auditing, which is managed in
SAP Control Center:
|
|
SMPONP-15058
|
Product information from the Installed History tab of
SAP Control Center does not display details of
older SPs or patches.
Workaround: Check details in the product_patch_info, product_patch_components, and product_component_files tables in the clusterdb database. |
|
SMPONP-14823
|
Selected properties do not show correctly when switching between tabs in
SAP Control Center.
For example:
Workaround: Select the properties you want to show by selecting it on the current page's drop-down list to invoke the add columns event. |
|
SMPONP-14818
|
Newly created Web Container properties cannot be edited and saved by clicking
the Properties button if not first saved.
If you:
Workaround: After creating a new Web Container record, click Save before editing the properties. |
|
SMPONP-14802
|
Changing OCSP (Online Certificate Status Protocol) properties from a valid
value (not empty) to NULL (empty string), requires server restart.
If you change an OCSP property to NULL from SAP Control Center, then click Save, your changes do not take effect. Workaround: Restart SAP Mobile Server for the OCSP changes to take effect. |
|
SMPONP-14405
|
The warning message "the service did not respond to the start or control
request in a timely fashion" displays when stopping
SAP Mobile Server
Occasionally when stopping the SAP Mobile Server service from the Windows service control panel, you may encounter the warning message described above. Workaround: You can safely ignore the warning message, the process eventually stops as expected. |
|
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. |
|
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-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:
|
|
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:
|

