Known Issues with Installing, Uninstalling, and Upgrading

When upgrading to Unwired Server 2.1.3, the installer prompts you for an admin ID and password at the end of the upgrade. If the credentials you provide are deemed invalid, the following message is displayed:

The Unwired Platform admin login information provided are not valid.  Would you like to try again?
Press Y to re-enter Unwired Platform admin login information.  Any other key to exit

If you perform a silent upgrade, you do not have the chance to re-enter different credentials if they are invalid. In this case, the message reads:

The admin credential provided was not valid so cannot verify that the server is running properly.  Manually verify that the server has started.  Exiting...

Workaround: Ignore the message. You can perform a manual package deployment if you wish to be sure that the upgraded server is function properly. See Creating new users in SQL Anywhere Server - Database Administration, available at http://infocenter.sybase.com/help/topic/com.sybase.help.sqlanywhere.12.0.0/dbadmin/umannew.html.

After upgrading a cluster to 2.1 ESD #3, an new Unwired Server node that is added fails to sync with the cluster.

Workaround 1: You can avoid this problem by setting Unwired Server services to start manually when you install the 2.1 server. See Adding an Unwired Server Node to a Cluster.

When Runtime 2.1 installer is launched on the system with Mobile SDK 2.1 ESD #3 or newer installed already, user will see “null” as the installation destination path which is not changeable.

Workaround 1: Install 2.1 runtime before Mobile SDK.

On the first Unwired Server node, upgrades to 2.1 ESD #3 may take up to an hour in a clustered environment with a Windows 2008 R2 data tier server.

Workaround: None. The upgrade will complete successfully.

After successfully upgrading from 2.0 ESD #1 to 2.1 ESD #3 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.

The data path must be in UNC format when installing a cluster node.

Workaround: Run the installer in graphical mode.

“***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 retained connections to a table while the upgrade was running. You can get more detailed information from the trace file in <UnwiredPlatform_InstallDir>\UnwiredPlatform\Servers\MessagingServer\Trace\DBUpgrader.

Workaround:

1. Stop all Sybase Unwired Server services in all application nodes.
2. Restart the database services in the data tier node to ensure 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\MessagingServer\Bin.
4. Run the command dbupgrader –v current and make sure no error messages appear.
5. Run the command tracemigrator –i and ensure no error messages appear. You can safely disregard a message that says no action is taken because the migration is already done.
6. Verify that the Sybase Unwired Server service in the application node can start.

If 2.0 or 2.0 ESD #1 clients have not connected through an activated registration, and you upgrade to 2.1 ESD #3, those clients may not be able to connect to the 2.1 ESD #3 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 ESD #1 clients connect to the 2.1 ESD #3 server.

Your system requires the 32-bit installer of Sybase Unwired Platform.

Your system requires the 64-bit installer of Sybase Unwired Platform.

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

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

Workaround: To avoid port number conflicts, do not use consecutive port numbers for the unsecured communication ports.

If you plan to use SAP JCO 3 in Unwired WorkSpace running on Windows XP, JCO 3 requires Microsoft Visual C++ 2005 Service Pack 1 Redistributable.

Workaround: Install the Microsoft Visual C++ 2005 Service Pack 1 Redistributable.

Obtain the Microsoft Visual C++ 2005 Service Pack 1 Redistributable from: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=14431.

You can install the service pack after installing the 2.1 ESD #3 upgrade if you discover you need it.