Known Issues with Installing, Uninstalling, and Upgrading

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

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

CR #Description
704936
"An Unknown server error has occurred" after upgrade of SUP 2.1.
An upgrade from SUP 2.1 to SUP 2.1 ESD #1 is causing some errors in Sybase Control Center (SCC). Several tabs return the error: 
"An Unknown server error has occurred"

These errors occur on the cluster node in the Properties and Pending Changes tabs, and under Server Configuration in the General, Communication Ports, SSL Configuration, Performance Configuration, and Replication tabs.

Workaround: Download EBF #20128. Refer to the EBF README for instructions.

697579
Cannot add a new node to an existing cluster.

When you try to add an additional node to an existing SUP 2.1 ESD #1 (EBF #19762) cluster, the new node is unable to start. To add extra nodes and have them start correctly, you need to install the new nodes with the new SUP 2.1 ESD #1 (EBF #20128).

Workaround: Download and install the new SUP 2.1 ESD #1 (EBF #20128) on the new nodes.

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:
  1. Navigate to: <UnwiredPlatform_InstallDir>\UnwiredPlatform\Servers\UnwiredServer\Repository\Instance\com\sybase\djc\sql\DataSource.
  2. Open messagingdb.properties in a text editor.
  3. Fix the serverName value to use the host name (network name) from the UNC data path the user entered during the 2.0 cluster installation, and not the primary Unwired Server name. For example, if the user entered \\someHost.myDomain.com\Data as the UNC path to the shared data folder in the data tier installation, the serverName value should be updated to someHost.mydomain.com.
  4. Save the file, and repeat the process for the second node.
  5. Restart the Sybase Unwired Platform nodes.
694214
Silent Installation Fails on Shared Host Microsoft Cluster
If you attempt to perform a silent installation for a shared host MS cluster scenario, you can install the data tier component successfully, but when you try to install Unwired Server on the same host, the silent installation fails with an error message:
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.

693727
Unwired Server upgrade from version 2.1 to 2.1 ESD #1 fails

If you installed SUP 2.1 and never started Unwired Server, the upgrade fails.

Workaround: Before upgrading to SUP 2.1 ESD #1, start the SUP 2.1 Unwired Server at least once.

692712
When upgrading to Sybase Unwired Platform 2.1 ESD #1, 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:

  1. Stop all Sybase Unwired server services in all the application nodes.
  2. Restart the database services in the data tier node. This is to make sure the Messaging Database has no open connections.
  3. From the primary application nodes, open a Windows command window and navigate to <UnwiredPlatform_InstallDir>\UnwiredPlatform\Servers\Messaging\Bin folder.
  4. Run the command dbupgrader –v current and make sure no error messages are displayed.
  5. 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.
  6. Start the Sybase Unwired Server service in the application node and verify it can start.
688350
When a version 2.1 project is opened in Unwired WorkSpace, the message says it is version is 2.0.1

This is a routine message. It reflects the version number of Unwired WorkSpace that was packaged with Unwired Platform 2.1, rather than the Unwired Platform version number.

Workaround: Ignore the version number in the message and click OK on the prompt.

686034
Incorrect error message displays 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, the error message displays:
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, the error message displays:
Your system requires the 64-bit installer of Sybase Unwired Platform.

Workaround: None. Use the installer that matches your system bit version.

679421
Communication port number conflicts can occur when installing Sybase Unwired Platform 2.1 if you indicate consecutive port numbers for the Server Administation, Data Change Notification, and Replication ports.

The Sybase Unwired Platform Runtime installer automatically creates secure port numbers by incrementing the unsecure port numbers (indicated during installation) by one.

Workaround: Do not use consecutive port numbers for the unsecured communication ports to avoid port number conflicts.