Troubleshooting Installation

Backing up the Sybase Unwired Platform Runtime installation fails because the Sybase Control Center path is too long.

Workaround: Before backing up the Sybase Unwired Platform Runtime installation, you must delete the contents of SUP_HOME\services\EmbeddedWebContainer\container\Jetty-7.6.2.v20120308\work. You must delete the contents of this folder from the command prompt, and not from Windows Explorer.

Potential file locked on 32-bit Windows Server 2003 SP2 system may cause upgrade to fail.

Visual C++2008 wizard starts when installing Unwired Platform

If Visual C++ 2008 runtime is installed in the root directory of the system where you are installing Unwired Platform server components, the Visual C++ wizard automatically starts after you start the Sybase Unwired Platform Runtime installer.

In a new or upgrade installation, the installer displays this error message:

The host name of the system resolves to a local link address. This suggests an incorrect binding order of network adapters. The install/upgrade cannot proceed. Once the binding order is corrected, restart the installer. Click OK to exit the installer.

The upgrade version of the message displays the "local link address" in parentheses.

Explanation: If no usable IP addresses are available on the system where you are installing Sybase Unwired Platform, Windows assigns a "local link" IP address in the range 169.254.0.0/16. The installer detects that the system's IP address is only usable locally, and stops.

netsh interface ipv6 set prefix ::1/128 50 5 
netsh interface ipv6 add  prefix ::1/128 50 5 
netsh interface ipv6 set prefix ::1/96 40 4 
netsh interface ipv6 add prefix ::1/96 40 4 
netsh interface ipv6 set prefix  ::ffff:0:0/96 30 3 
netsh interface ipv6 add prefix ::ffff:0:0/96 30 3  
netsh interface ipv6 set prefix ::/0 20 2 
netsh interface ipv6 add  prefix ::/0 20 2 
netsh interface ipv6 set prefix ::ffff:169.254.0.0/112 10 1  
netsh interface ipv6 add prefix ::ffff:169.254.0.0/112 10 1  

Silent installation gives Registry error

If Sybase Unwired Platform was previously installed on the target system, and either the installation was canceled before completion or the uninstallation was incomplete, the installer detects Windows Registry keys that must be deleted, and prompts you to confirm the deletion. This aborts a silent installation.

Workaround: Run the Sybase Unwired Platform Runtime installer interactively, confirm the Registry key deletion, and complete the installation. Then immediately use the Windows Control Panel to uninstall Unwired Platform components. The system is then ready for a silent installation.

Uninstaller might not run on Windows Vista

Sometimes, the uninstaller does not launch on Windows Vista. This may be caused by the operating system changing the launch command for the Unwired Platform uninstaller, preventing it from using its own JVM to start itself.

Workaround: Run an external 32-bit JDK version 1.6.0_26 to launch the uninstaller with the following, where <jdk_installdir> is similar to C:\jdk1.6.0_31\bin:

<jdk_installdir>\java -Dtemp.dir=%TEMP% -jar SUP_HOME\Uninstallers\ UnwiredPlatform\uninstall.jar

When you uninstall—or cancel uninstalling—Unwired Platform, the Program Compatibility Assistant reports This program might not have uninstalled correctly. At this point, you can avoid the uninstaller issue by selecting This program uninstalled correctly instead of Uninstall with recommended settings.

Unwired Servers do not shut down during an uninstallation

Shut down the Unwired Servers before shutting down the data tier.

See Supported Hardware and Software.

Network domain name is invalid on virtual machine (VM) installation or when switching to different networks after installation

1. Shut down Unwired Server and Sybase Control Center services.
2. Obtain the correct host and domain name.
3. Open a command window and enter:

   ipconfig /all

4. Run:

   configure-mms.bat <clustername>

5. To set the proper domain name in all the Unwired Server configuration files, run:

   SUP_HOME\Servers\UnwiredServer\bin\configure.bat

6. Manually edit SCC_HOME\SCC-3_2\services\RMI\service-config.xml, modifying the address property to reflect the new fully qualified host name.

   <properties>
       <set-property property="address" value="supvm.mycompany.com" />
       <set-property property="port" value="9999" />
       <set-property property="timeout" value="43200" />
     </properties>
   

   Replace supvm with your host name and mycompany.com with your domain name.

7. If the DNS server cannot resolve the fully qualified name and this server is accessed only locally, edit the c:\Windows\system32\drivers\etc\hosts file to add 127.0.0.1 to the current fully qualified name. You can add as many 127.0.0.1 entries as needed for each host and domain in which your machine works.
8. Restart Sybase Control Center and Unwired Server.
9. Log in to Sybase Control Center.
10. Open Perspective Resources view.
11. Update the host property of the registered resource for Unwired Server for which the network domain name changed.
12. Choose Authenticate, then launch Management Console using Manage option on the resource.
13. For Sybase Unwired WorkSpace components only, launch Eclipse and modify the domain name in the connection profile for Unwired Server.

Cannot install Enterprise Developer Edition on virtual machine (VM) with unserved license.

If you need to use a Developer Edition via Remote Desktop Connection (RDC), Terminal Services, or similar remote access technology, you cannot use unserved licenses.

Workaround: Generate served licenses and use a license server. Virtual machines (VMs) that are not locally hosted typically require RDC, so also require served licenses.

You may be able to install on a VM with an unserved license if you use console 0 to access the VM to perform the installation.

Unable to open Service error appears during installation and, after installation, messaging service does not appear in Windows Service list.

The local .NET framework may be corrupted. To check, go to C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ and run installutil. A configuration error message indicates whether the local .NET framework is corrupted; help information indicates normal function.

If the local .NET framework is corrupted, uninstall and reinstall .NET 2.0.