Troubleshooting Installation

Visual C++2008 wizard starts up 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 starts up soon after you start the Sybase Unwired Platform Runtime installer.

Silent install 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 OK the deletion before the installer continues. This aborts a silent installation.

Workaround: Run the Sybase Unwired Platform Runtime installer interactively, OK the Registry key deletion, and complete the installation. Then immediately uninstall Unwired Platform components through the Windows Control Panel. 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_26\bin:

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

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

Unwired Servers do not shut down during an uninstallation

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

1. Shut down Unwired Server and Unified Agent 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:

   <UnwiredPlatform_InstallDir>\Servers\UnwiredServer\bin\configure.bat

6. Manually edit %SYBASE%\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 Unified Agent 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 and then launch Management Console using Manage option on the resource.
13. For Unwired WorkSpace components only, launch Eclipse and modify the domain name in the connection profile for Unwired Server.

Unable to 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 is not in Windows Service list.

The root cause of this problem may be that the local .NET framework is corrupted. Check this by going to C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ and running installutil. A configuration error message indicates that the local .NET framework is corrupted. Help information indicates normal function.

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