Known Issues with Installing, Uninstalling, and Upgrading

WARN MMS main [com.sybase.sup.server.mbs.SUPPackageUtil] [] [] 
No scope named [d1_onlineproject.1_0] exists at location 
[C:\S-_.123456781\MobilePlatform012345678901\Servers\UnwiredServer\bin\..\deploy\sup].
java.lang.RuntimeException: No scope named [d1_onlineproject.1_0] exists at location 
[C:\S-_.123456781\MobilePlatform012345678901\Servers\UnwiredServer\bin\..\deploy\sup].

Workaround: The “No scope named [d1_onlineproject.1_0] exists..” error occurs when new packages are deployed to the secondary node while the secondary node is starting but has not yet synchronized. Restart the secondary node to synchronize the packages.

Cannot upgrade Sybase Unwired Platform version 2.1 with DOE-C installed to SAP Mobile Platform version 2.3 SP04.

HEKY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sybase\UnwiredPlatform\2.1; 
HEKY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sybase\UnwiredPlatform\2.2;

remove32BitCDB.err  
remove32BitCLDB.err  
remove32BitMonDB.err  
removeCDB.err  
removeCLDB.err 

Workaround: These errors can be ignored.

HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\monitordb 
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\SCC-3_2 
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\SQL Anywhere 16 
HKEY_LOCAL_MACHINE\SOFTWARE\Sybase\SQL Anywhere\16.0 

Workaround: These registry keys can be ignored. You can remove these keys manually, but it is not necessary.

SAP Mobile Platform on Windows 8 and 2012 fails to run a silent uninstallation, start or stop SAP Mobile Server, or run the upgrade script by double clicking the corresponding desktop icon.

Workaround: Start the command by navigating to the appropriate folder, right-clicking the file of interest (for example, SilentUninstall_Win.bat and selecting Run as administrator.

When installing SAP Mobile Platform Runtime version 2.3, it is version 2.3 SP04. When upgrading from version 2.3 (any SP), you can install version 2.3 SP04 directly, and do not need to upgrade incrementally.

The installer can directly upgrade your Sybase Unwired Platform 2.2.x or SAP Mobile Platform version 2.3.x installation to SAP Mobile Platform version 2.3. SP04. If you have a version of Sybase Unwired Platform earlier than 2.2.x, additional steps are required to upgrade to SAP Mobile Platform Runtime version 2.3. SP04

2013-09-17 23:07:18.694 INFO MMS main [com.sybase.sup.cache.impl.CacheService] [] [] 
Members of distributed cache: [/10.172.157.69, /10.172.157.72, /10.172.180.46] 
2013-09-17 23:07:18.694 INFO MMS main [com.sybase.sup.cache.impl.CacheService] [] [] 
Expected members: [10.172.180.46, 10.172.180.47, 10.172.157.69, 10.172.157.72]

Workaround: Restart the problematic node.

After upgrading from SAP Mobile Platform version 2.3 to 2.3 SP03, if you find the following errors in the server log, perform one of the workarounds.

2013-09-10 11:20:02.100 INFO DOEC sup.mbs.3 [com.sybase.vader.djc.jms.DSMessageListener] [] [] (sup.mbs.3) com.sybase.vader.djc.jms.DSMessageListener.onMessage:104 - Invoking DataServices with package name: d2_sap_crm.1_0 
2013-09-10 11:20:02.842 ERROR MMS Thread-156 [com.sybase.sup.admin.server.DOEServerStatusUpdateTask] [] [] Error retrieving packages while resynchronizing. 
com.sybase.sup.doec.admin.DOECAdminException 
  at com.sybase.sup.doec.admin.impl.DOECAdminImpl.sendDOECMessage(DOECAdminImpl.java:779) 
  at com.sybase.sup.doec.admin.impl.DOECAdminImpl.resyncPackage(DOECAdminImpl.java:372) 
  at com.sybase.sup.admin.server.DOEServerStatusUpdateTask.resyncPackages(DOEServerStatusUpdateTask.java:74) 
  at com.sybase.sup.admin.server.DOEServerStatusUpdateTask.run(DOEServerStatusUpdateTask.java:28) 
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) 
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
  at java.lang.reflect.Method.invoke(Method.java:601) 
  at com.sybase.djc.server.ServiceComponent.runService(ServiceComponent.java:469) 
  at com.sybase.djc.server.ServiceComponent_DJC.runService(ServiceComponent_DJC.java:203) 

Workaround 1: Manually modify the Servers\UnwiredServer\Repository\Package\d{domainId}\sup\components\d{domainId}_{packageName}\{packageVersion}.properties file to input the techuser-password property value as plain text, and restart the server. 

ERROR: return value: 3010

ERROR: VC Runtime 2005 failed.

Workaround: You can safely ignore these errors. Return code from running vcredist indicates that the installation was successful and requires a system restart.

The service has not been started. 
Error stopping service "SAPMobilePlatformConsolidatedDatabase". 
The service has not been started. 
Error stopping service "SAPMobilePlatformClusterDatabase". 
The service has not been started. 
Error stopping service "SAPMobilePlatformMonitorDatabase".

Workaround: You can safely ignore these errors.

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. 

2013-01-27 18:38:34,815 [ INFO] [main] (SCCRepositoryPwdUpdater.java:29) - Begin database password update.
2013-01-27 18:39:48,245 [ERROR] [main] (SCCRepositoryPwdUpdater.java:45) - ASAEngine: The "scc_repository" dataserver Engine could not be started
java.lang.Exception: ASAEngine: The "scc_repository" dataserver Engine could not be started
	at com.sybase.sup.sysadmin.asa.ASAEngine.startEngine(ASAEngine.java:145)
	at com.sybase.sup.sysadmin.sccconfig.SCCRepositoryASAInstance.startEngine(SCCRepositoryASAInstance.java:36)
	at com.sybase.sup.sysadmin.sccconfig.SCCRepositoryASAInstance.open(SCCRepositoryASAInstance.java:29)
	at com.sybase.sup.sysadmin.sccconfig.apps.repoPwdUpdate.SCCRepositoryPwdUpdater.update(SCCRepositoryPwdUpdater.java:32)
	at com.sybase.sup.sysadmin.sccconfig.apps.SCCRepositoryPwdUpdate.main(SCCRepositoryPwdUpdate.java:28)

Workaround: Ignore the error message. This error does not have any functional impact.

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.

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

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.