Perform a fresh Unwired Server installation using the Unwired Platform version 2.1 installer, then upgrade using the Unwired Platform version 2.1 ESD #3 script.
If the data tier is installed in a failover cluster, enter the network name of the cluster resource that acts as a "virtual host" for the data tier services.
Click Next.
If you get an error, such as Failed to check out license, click OK, then click Back to confirm the license model (served or unserved), license product edition, and license type.
The total length of the path must be 43 characters or less.
If you set Unwired Platform services to start automatically, the new Unwired Server node may fail to sync with the cluster.
(Optional) Select Set Sybase Unwired Server name to specify a name other than the server name designated in the file system.
The UNC path must use a fully qualified host name or network name (name.domain). For example, if the data tier node is installed in C:\Sybase, the data folder is C:\Sybase\UnwiredPlatform\Data. If the machine is named SUPDT, the UNC path to the data folder is \\SUPDT.example.com\Data.
In a typical new installation, you need not change any pre-populated value, just enter "sql" as the default password for each database.
In an upgrade installation, if the password fields are filled, do not change them. If they are not filled, enter the current the password for each database.
The script runs an initial validation check on the files extracted from the upgrade package. If files are corrupted, delete the corrupted archive and download another copy of the upgrade package.
If the script detects environment issues, you see an error message and the upgrade process stops. Follow the instructions provided and restart the upgrade. If you cannot correct the issue, contact Sybase Technical Support.
The script does not detect locked files in the installation directory tree. The error message that appears when the script encounters locked files varies.
If the installer stops with an unexpected error message, look for locked files in the installation directory tree. Unlock any locked files you find and re-run the upgrade script.