Known Issues with Installing, Uninstalling, and Upgrading

Learn about known Runtime installation, uninstallation and upgrade issues and workarounds.

See the Sybase Unwired Platform Installation Guide for Runtime for upgrade and migration information.

Issue Number	Description
CR 697231	Recommendation for upgrading Unwired Platform in a cluster. When upgrading Unwired Platform in a Microsoft cluster, this is the recommended upgrade order: Data tier First server node Second server node After upgrading the data tier, check the data tier status to make sure the data tier connection is stable before you proceed to upgrading the first server node. If the data tier connection is not stable, and you upgrade the first server, the upgrade fails with this error: Error running "configure.bat upgrade-sup". Workaround: To correct the data tier connection problem, restart the data tier before upgrading the first server.
CR 696536	Cluster upgrade successful from 2.0.1 to 2.1.1, but device client synchronization fails. After successfully upgrading from 2.0.1 to 2.1.1 in a cluster, device client synchronization fails. This is due to a host name change that was introduced in Sybase Unwired Platform 2.1 for the data tier host; the serverName property for the messagingdb file is set to the host name of the first server node, and not to the data tier host. This is not an issue for single-node installations. Workaround: Navigate to `UnwiredPlatform_InstallDir`\UnwiredPlatform\Servers\UnwiredServer\Repository\Instance\com\sybase\djc\sql\DataSource. Use a text editor to open messagingdb.properties. Fix the serverName value to use the fully qualified host name or network name (name.domain) from the UNC path to the file system that houses the data tier database files, and not to the primary Unwired Server name. For example, if \\name.domain.com\Data was the UNC path to the file system that houses the data tier database files, update the serverName value to "name.domain.com." Save the file, and repeat the process for the second node. Restart the Unwired Platform nodes.
CR 694214	Silent installation fails on shared host Microsoft cluster. If you attempt to perform a silent installation for a shared host Microsoft cluster scenario, you can successfully install the data tier component, but when you try to install Unwired Server on the same host, the silent installation fails with: The data path must be in UNC format when installing a cluster node. Workaround: To perform a shared host Microsoft Cluster installation, you must run the installer in graphical mode.
CR 692712	When upgrading to Sybase Unwired Platform 2.1 ESD #2, you receive an error message: “*Error!!! Error!!!* The Messaging installer completed with the following errors. These errors will have to be addressed before the services become functional. Please refer to documentation for recovery process. Database upgrade failed." This error happens when the Messaging server database upgrade does not complete. The most likely reason for this is that the Messaging server database had some lingering connections to a table while the upgrade was running. You can get more detailed information from the trace file located in `UnwiredPlatform_InstallDir`\UnwiredPlatform\UnwiredServer\Logs\DBUpgrader. Workaround: Stop all Unwired Server services in all the application nodes. Restart the database services in the data tier node. This is to make sure the Messaging Database has no open connections. From the primary application nodes, open a Windows command window and navigate to `UnwiredPlatform_InstallDir`\UnwiredPlatform\Servers\Messaging\Bin folder. Run the command dbupgrader –v current and make sure no error messages are displayed. Then run the command tracemigrator –i and make sure no error messages are displayed. If the message says no action is taken because the migration is already done, it is okay. Start the Unwired Server service in the application node and verify it can start.
CR 689287	2.0 or 2.0.1 MBS clients and Hybrid Web Container clients may not be able to connect to 2.1.2 server. If 2.0 or 2.0.1 clients have not connected through an activated registration, and the server is upgraded to 2.1.2, those clients may not be able to connect to the 2.1.2 server. Workaround: Implement a server registration that uses an empty application ID, and use manual registration to make the MBS and Hybrid Web Container 2.0 and 2.0.1 clients connect to the 2.1.2 server.
CR 686034	Incorrect error message appears when the Sybase Unwired Platform 2.1 installer does not match the system bit version. If you attempt to run the 32-bit installer on a 64-bit system, you see: Your system requires the 32-bit installer of Sybase Unwired Platform. If you attempt to run the 64-bit installer on a 32-bit system, you see: Your system requires the 64-bit installer of Sybase Unwired Platform. Workaround: None. Use the installer that matches your system bit version.
CR 683668	Upgrade a cluster and add an Unwired Server. If you plan to upgrade a cluster environment from Sybase Unwired Platform 2.0 to 2.1 as part of the upgrade to 2.1 ESD #2, as well as add a new Unwired Server node to the cluster, follow these steps. Workaround: Before you add the new server node using the Sybase Unwired Platform 2.1 installer, stop all existing server nodes. Install the new server node. Stop the newly added server node, Modify the sup.properties file: Navigate to `UnwiredPlatform_InstallDir`\UnwiredPlatform\Servers\UnwiredServer\Repository\Instance\com\sybase\sup\server\SUPServer\sup.properties . Change "sup.admin.protocol=iiops" to "sup.admin.protocol=iiop". Copy the csi.properties and roles-map.xml files to: `UnwiredPlatform_InstallDir`\SCC-3_2\conf from the second node (or primary node) to replace the corresponding files on the newly added server node. Start all the server nodes in turn. To connect to Sybase Control Center for the newly added server node, change the connection profile in Sybase Control Center. Change the port number to `2000`, and change the value of Use secure connection to No.
CR 679421	Communication port number conflicts may occur when installing Sybase Unwired Platform 2.1 if you indicate consecutive port numbers for the Server Administration, Data Change Notification, and Replication ports. The Unwired Platform Runtime installer automatically creates secure port numbers by incrementing the unsecured port numbers (indicated during installation) by one. Workaround: Do not use consecutive port numbers for the unsecured communication ports to avoid port number conflicts.