Known Issues for Sybase Control Center

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

Issue #	Description
RTC-432	Server connection password displays as cleartext in deployment unit When deploying an MBO package using the Deployment Wizard, if you update the server connection password, it will be stored in cleartext in the deployment unit file. Workaround: Do one of the following: When deploying the MBO package, do not update the server connection password. After deploying, update the password for the connection using Domains > <`domainName`> > Connections. Choose an existing server connection when deploying the MBO package.
RTC-221	Redeploying a package to Unwired Server after changing a Cache Group policy from "Scheduled" to "On Demand" may result in Sybase Control Center displaying an invalid cache interval. Workaround: Update the cache interval in Sybase Control Center.
RTC-225	Redundant properties displayed for application templates and connection settings Several push notification properties in the application connection settings are no longer applicable. Blackberry Push Notifications: BES Notification Name Delivery Threshold (Minutes) Apple Push Notitifcations Delivery Threshold (Minutes) Workaround: Ignore these properties.
CR-708155	"DOECNoAuth" security configuration assigned automatically when deploying for the first time in the domain, even if you select 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	Sybase 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 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: Before taking any action in Sybase 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 Sybase 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 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 from the Sybase Control Center Configuration tab. If this does not resolve the issue, try decreasing the time range set in the domain log in Sybase Control Center.
CR-695792	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 that you first use 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: Select 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 Control Center Service shortcut to stop the Sybase Control Center3.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 process, right-click and select End Process Tree. This option also kills the Sybase Control Center database repository server process dbsrv11.exe.
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.
RTC-396	Modification of JVM properties in SCC does not take effect if server is restarted using Windows Services Workaround: Restart server from SCC, use restart-unwired-server.bat, or click the stop/start Unwired Server services icons.