Known Issues with Installing, Uninstalling, and Upgrading

When installing SAP Mobile Platform version 2.3 you must extract the installer images prior to installation. Extracting the images with Windows Explorer marks all files as read-only, resulting in an upgrade failure.

Workaround: To ensure a successful upgrade, use an extraction utility such WinZip or WinRAR to extract the files.

This issue happens when you place the installation image on a mapped network drive. The installation requires the image to be placed on a local drive.

Workaround: Move the upgrade scripts to the local drive. Re-run the scripts. 

When you perform the upgrade sequence 2.2 - 2.2 SP04 - 2.3, the PropertiesNotFoundException error is thrown and can be found in the ASN2 server log.

Workaround: None. The errors do not impact functionality.

SCC does not manage the server after you upgrade from SUP 2.2 SP04 or later to SMP 2.3.

Workaround: Save and run a SQL script at SCC node to fix the issue. The SQL script and procedure are documented in Resolving Upgrade Issue for SCC.

A QueueNotReadyException appears in server1 log when installing SAP Mobile Platform with primary install node1 and secondary node2, but starting node2 before node1.

Workaround:Ensure node1.properties appears in the SMP_HOME/repository/Instance/com/sybase/djc/server/ApplicationServer folder, then restart node1.

The SAP Mobile Platform 2.3 installer waits unnecessarily when upgrading from Sybase Unwired Platform 2.2.X to SAP Mobile Platform 2.3 if services in the 2.2.X installation are set to manual.

Workaround 1: Workaround 1: When upgrading your 2.2.X installation to 2.3, set the startup mode for Sybase Unwired Platform services to automatic before running the SAP Mobile Platform 2.3 installer

Workaround 2: If the 2.3 installer was started without setting the Sybase Unwired Platform services startup mode to automatic, and the installer status displays Pinging server using the secure management port ... for a long time, then the upgrade has completed normally. At this point, the installer can be stopped manually using Windows Task Manger.

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.

The path to the Embedded Web Container in the SCC-3_2 folder is too long for Windows to process.

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.

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    

Rarely, during the first start of the first node of a cluster, the cluster configuration cache binds itself erroneously to an IP address that cannot be reached by secondary nodes in the cluster. When this happens, the secondary nodes appear to stop responding during installation (if the primary or secondary nodes are running), and may not initially start.

Workaround: Stop the unresponsive secondary server. Restart the primary server, and then restart the secondary server.

The Unwired Platform 2.2.x installation created a registry value for the name of the cluster, clusterdb_<clustername>. SAP Mobile Platform 2.3 limits cluster names to no more than 16 characters in length. If the upgrade installer encountered a cluster name that was longer than 16 characters, it cloned the clusterdb_<clustername> registry entry with the name clusterdb, and did not delete the original clusterdb_<clustername> registry entry. SAP Mobile Platform 2.3 does not delete that entry.

Workaround: Manually delete the clusterdb_<clustername> registry entry if you want to; however, leaving it in place will not cause any problems with future reinstallation of SAP Mobile Platform.

The upgrade process stops responding after upgrading the first server node if all nodes were not shut down before the upgrade.

Workaround: Online upgrade is not supported. Stop all the SAP Mobile Platform services, including the data tier, before running the upgrade installer.

2012-08-21 01:26:15.753 WARN MMS ScheduledTask:SynchronizeNode...

Workaround: Ignore this warning, or install the secondary SAP Mobile Server node after the primary server installation completes.

SAP® JCo 3 in Unwired WorkSpace running on Windows XP requires Microsoft Visual C++ 2005 Service Pack 1 Redistributable.

Workaround: Obtain the Microsoft Visual C++ 2005 Service Pack 1 Redistributable from:

http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=14431.

The installer is unable to run in graphical mode. Try running the installer with the 
-console or -silent flag.

Workaround: Remove the installer binary path from the HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags registry key.

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: Launch the uninstaller:

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

When you uninstall or cancel out of uninstalling SAP Mobile Platform, the Program Compatibility Assistant shows:

This program might not have uninstalled correctly.

Select This program uninstalled correctly instead of Uninstall with recommended settings.