Known Issues for Sybase Control Center

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

Issue Number	Description
n/a	Domains and Packages tab Sybase Control Center for Online Data Proxy does not have a way to add a new domain to an application from the Application Properties dialog. Domains can only be associated in the Application Creation wizard.
CR 708155	"DOECNoAuth" security configuration assigned automatically when deploying for the first time in the domain When deploying for the first time in the domain, the "DOECNoAuth" security configuration is assigned, even if you selected another value. Workaround: After deployment, change the security configuration in Sybase Control Center. Navigate to Domains > `DomainName` > Packages > `PackageName` > Settings > Security Configuration Select the correct security configuration, and save the changes.
CR 707966	When deleting a domain or undeploying a DOE-C package, the server log shows a `Failed to undeploy package` error. Workaround: Ignore the error.
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	SCC does not ask user to delete packages and connections before deleting the domain. Workaround: None. Make sure package and connection deletion is not an issue before deleting the domain.
CR 704917	If an administrator takes action from Sybase 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: Ensure that the primary server shutdown is complete and another server has taken over as the new primary before taking any actions in Sybase Control Center.
CR 704913	When an iOS device goes offline, the device is still shown as being online for about 8 minutes in Sybase Control Center. Workaround: None.
CR 704758	Cannot delete replication devices in Sybase Control Center; license information incorrect. Workaround: Patch 01 fixes this issue. See the Fixed Issues in Patch 01 in the Sybase Unwired Platform 2.1 ESD #3 Patch 01 section of this release bulletin. If you cannot apply the patch, use this workaround. Upgrade the client runtime to the most current version of Unwired Platform. Starting with version 2.1, device tracking changed to application connections tracking. However, replication applications must use the 2.1.2 client runtime (or 2.1.1 for Android applications) to be compatible with current versions of Sybase Control Center and license tracking. With these clients, replication devices are "implicitly" tracked at the package level and the user is associated with the device is tracked at the package user level . The expectation is that when a package user is deleted, and if that package user no longer uses any other package from that device, the device is deleted. The license count correctly decrements by 1. A similar mechanism is in place for subscriptions.
CR 703367	Domain log messages in Data Sync and Operation Replay sub-systems are not logged. Workaround: Use this: Applies to the 'default' domain only. 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. Please contact technical support for guidance.
CR 703321	Cannot export domain log after upgrading. Exporting a domain log after upgrading to version 2.1 ESD #3 generates a `Domain log export failed` error message. Workaround: Clear the cache for the browser you are using to access Sybase Control Center.
CR 696373	When retrieving a domain log for large data, you receive an unknown error in Sybase Control Center. Workaround: Check whether the Unwired Server or Sybase Control Center agent.log reports an out of memory error. If so, increase the JVM heap size appropriately for Unwired Server. Use either the Sybase Control Center Server Configuration tab or the Sybase Control Center ...\SCC_X-X\bin\ scc.properties file). If this does not resolve the issue, try decreasing the time range set in the domain log in Sybase Control Center to a smaller value.
CR 695792	Unwired Server stops responding when suspending DOE-C package subscriptions. Suspending a large volume (100 or more) of DOE-C package subscriptions may cause Unwired 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, Sybase recommends using Verify mode deployment; if verify succeeds, proceed to Update mode deployment.
CR 690482	Using Firefox, the Sybase 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 by selecting Tools > Options > Advanced > View Certificates. Click the Servers tab, then identify existing certificates issued to the same host to which you are connecting . 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 Sybase Unwired Platform Services shortcut to stop the Sybase Control Center 3.2 service, Sybase Control Center displays `Stopping` in the Windows Control Panel yet fails to stop. Workaround: To stop the Sybase Control Center service: Launch Windows Task Manager. Locate the sccservice.exe 32 process, right-click and select End Process Tree. This option also kills the Sybase Control Center database repository server process dbsrv11.exe 32. For 32-bit machines, *32 does not appear.