Troubleshooting Installation

Determine the cause of installation problems and apply the recommended solution.

See the Troubleshooting guide for additional information.
Problem Resolution

Backing up the SAP Mobile Platform Runtime installation fails because the SAP Control Center path is too long.

 Before backing up the Runtime installation, you must delete the contents of the EmbeddedWebContainer folder in order to complete a clean backup of the installation.

Workaround: Before backing up the SAP Mobile Platform Runtime installation, you must delete the contents of SMP_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.

Install image validation failed. Install image may be corrupt.

Workaround: Download a new copy of the installation image. See install_drive\SUPRuntimeMissingFiles.txt (MobileSDKMissingFiles.txt for SAP Mobile SDK) for list of missing files. These files are generated only if any files listed in the installImageFileList.txt file are missing from the install image.

Install image validation failed. Install image may be corrupt.

Workaround: Download a new copy of the installation image. See install_drive\SUPRuntimeCorruptedFiles.txt (MobileSDKCorruptedFiles.txt for SAP Mobile SDK) for list of corrupt files. These files are generated only if any files listed in the zipFileList.txt file are corrupt.

The installImageFileList.txt to run install image validation may be corrupt. The installImageFileList.txt file is there, but the current size does not match initial size when the install image was created.

Workaround: Download a new copy of the installation image.

The zipFileList.txt to run install image validation may be corrupt. The zipFileList.txt file is there, but the current size does not match initial size when the install image was created.

Workaround: Download a new copy of the installation image.

Cannot find file installImageFileList.txt to run install image validation. The install image may be corrupt.

Workaround: Download a new copy of the installation image.

Cannot find file zipFileList.txt to run install image validation. The install image may be corrupt.

Workaround: Download a new copy of the installation image.

Cannot find file .installImageFileSize.txt to run install image validation. The install image may be corrupt.

Workaround: Download a new copy of the installation image.

The installImageFileList.txt to run install image validation is empty. The install image may be corrupt.

Workaround: Download a new copy of the installation image.

The zipFileList.txt to run install image validation is empty. The install image may be corrupt.

Workaround: Download a new copy of the installation image.

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

When upgrading, there is a potential problem with a Windows process holding a lock on one of the 12 Adaptive Server Anywhere (ASA) libraries (DLLs) even though all the ASA processes have shut down. This causes the upgrade to fail because the upgrade cannot overwrite the file. This is specific to a 32-bit Windows Server 2003 SP2.
Workaround:
  1. Shut down all SAP Mobile Platform processes.
  2. If services were set to automatic, set the start up for the SAP Mobile Platform services to manual.
  3. Restart the system.
  4. If step 2 was performed prior to upgrade, run the upgrade after the system has restarted.
  5. After the upgrade, set the startup for the SAP Mobile Platform services to automatic.

Visual C++2008 wizard starts when installing SAP Mobile Platform

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

Workaround: Verify that the following files have a date stamp of 11/7/2007, then move them to another location:
  • VC_RED.MSI
  • VC_RED.CAB
  • eula.1028.txt
  • eula.1031.txt
  • eula.1033.txt
  • eula.1036.txt
  • eula.1040.txt
  • eula.1041.txt
  • eula.1042.txt
  • eula.2052.txt
  • eula.3082.txt
  • globdata.ini
  • install.exe
  • install.ini
  • install.res.1028.dll
  • install.res.1031.dll
  • install.res.1033.dll
  • install.res.1036.dll
  • install.res.1040.dll
  • install.res.1041.dll
  • install.res.1042.dll
  • install.res.2052.dll
  • install.res.3082.dll
  • vcredist.bmp
Installation or upgrade cannot continue host name of system resolves to local link address

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 SAP Mobile 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.

Workaround: Execute the commands below from the command prompt, restart the server, and restart the installer.
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 add prefix ::ffff:169.254.0.0/112 10 1
netsh interface ipv6 set prefix ::ffff:169.254.0.0/112 10 1

Silent installation gives Registry error

If SAP Mobile 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 SAP Mobile Platform Runtime installer interactively, confirm the Registry key deletion, and complete the installation. Then immediately use the Windows Control Panel to uninstall SAP Mobile 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 SAP Mobile 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 SMP_HOME\Uninstallers\ MobilePlatform\uninstall.jar

When you uninstall—or cancel uninstalling—SAP Mobile 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.

SAP Mobile Servers do not shut down during an uninstallation

 Shut down all SAP products, SAP processes, and associated third-party products and processes before launching the uninstaller.

Shut down the SAP Mobile Servers before shutting down the data tier.
Cannot start an SAP Mobile Platform component Make sure that all services are started for the installed components. See System Administration > System Reference > SAP Mobile Platform Windows Services.
Cannot start SAP Mobile Server service and <host>-server.log file has "PropertiesNotFoundException" error. If you cannot start the SAP Mobile Server service by any of the means available – Windows Start menu, Desktop icon, or Windows Services control panel – check the server's log file. The log file is located in SMP_HOME \Servers\UnwiredServer\logs and is named <host>-server.log. If you find a "PropertiesNotFoundException" error in this log file, it means that the name you gave this server during installation duplicates the name of another server node in the cluster.

Workaround: Uninstall SAP Mobile Server on this node and reinstall, providing a server name that is unique within the cluster.
Cannot start SAP Control Center Make sure you have installed an appropriate version of Adobe Flash Player.

See Supported Hardware and Software.

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

 Configure SAP Mobile Server to use the valid network domain name.
  1. Shut down SAP Mobile Server and SAP Control Center services.
  2. Obtain the correct host and domain name.
  3. Open a command window and enter:

    ipconfig /all

  4. Run:

    updateProps.bat -nv "sup.host=<hostname>" -cn <clustername> -sn <servername>

  5. 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.

  6. 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.
  7. Restart SAP Control Center and SAP Mobile Server.
  8. Log in to SAP Control Center.
  9. Open Perspective Resources view.
  10. Update the host property of the registered resource for SAP Mobile Server for which the network domain name changed.
  11. Choose Authenticate, then launch Management Console using Manage option on the resource.
  12. For SAP Mobile WorkSpace components only, launch Eclipse and modify the domain name in the connection profile for SAP Mobile 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.
Parent topic: Troubleshooting