Release Bulletin 2.3 SP09

Known Issues with Installing, Uninstalling, and Upgrading

Learn about known runtime installation, uninstallation, and upgrade issues and workarounds.

Issue #
Description
BCP # 1670145152
The server port of the default template on the Application Connection Templates tab is wrong when the default HTTP listener ports(5001/8000) are used by the system.
Workaround:
  1. Log in to SAP Control Center.
  2. Navigate to Start of the navigation path Applications Next navigation step Application Connection Templates End of the navigation path, and select the default template which name is Start of the navigation path Default Next navigation step Properties Next navigation step Connection Next navigation step Server Port End of the navigation path.
  3. Change the wrong port to the correct one, and Save it.
SMPONP-18952
if add customized ASA start options before running the SAP Mobile Platform upgrade installer, the ASA server might not successfully start after the upgrade due to these customized options.

Workaround: Remove any customized ASA start options before upgrading a DataTier node or single server installation, and add those customized ASA start options back after confirming with your SAP consultant that those customized ASA start options are supported on the target SAP Mobile Platform version.

SMPONP-18053
SAP Mobile Server fails to start if the CLASSPATH environment variable exists in User Variables or System Variables.

Workaround: When preparing for the SAP Mobile Server installation, check for the CLASSPATH environment variable in both User Variables and System Variables panes of the Environment Variables dialog. If the environment variable is set, remove it before starting the installation.

SMPONP-15390
When upgrading from 2.2 SPx to 2.3.x, if you have a Microsoft Cluster shared host installation with the data tier databases and db log files split into separate locations, some of the registry information for the separate database and log file locations are not preserved when the registry location is moved from HKLM\SOFTWARE\Wow6432Node\Sybase to HKLM\SOFTWARE\Wow6432Node\SAP, which causes problems with later upgrades.
Workaround: Immediately after upgrading, update the registry by adding these expanded string values to HKLM\SOFTWARE\Wow6432Node\SAP\MobilePlatform\2.3:
  • CDBDataFolder = %cdb location%
  • CDBLogFolder = %cdb log location%
  • CLDBDataFolder = %clusterdb location%
  • CLDBLogFolder = %clusterdb log location%
  • DDBDataFolder = %domainlogdb location%
  • DDBLogFolder = %domainlogdb log location%
  • MDBDataFolder = %monitordb location%
  • MDBLogFolder = %monitordb log location%
SMPONP-15347
Errors in secondary server node log after installing 2.3 SP04 cluster.
After performing these steps:
  1. Install the Data Tier.
  2. Install the Primary app node with autostart=true.
  3. Install the Secondary app node with autostart=false.
  4. Install a Scale-out node.
  5. Deploy packages and start the Secondary node.
An error similar to this appears in the server node log:
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.

SMPONP-15095

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

Workaround: Delete these registry entries before upgrading 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;
SMPONP-14182
Performing an uninstallation from the GUI after performing a 2.3 to 2.3 SP04 upgraded installation, generates database related errors.
These errors are related to the upgrade in SAP Mobile Platform from SQLAnywhere version 12 to SQLAnywhere version 16, for example:
remove32BitCDB.err  
remove32BitCLDB.err  
remove32BitMonDB.err  
removeCDB.err  
removeCLDB.err 

Workaround: These errors can be ignored.

SMPONP-13514
Some registry keys are not automatically removed after uninstalling SAP Mobile Platform version 2.3 SP04.
These registry keys are not deleted on 64-bit platforms after a 2.3 SP04 runtime uninstallation:
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.

SMPONP-4639
Double-clicking desktop icon fails to launch SAP Mobile Platform command on Windows 8 and Windows 2012.

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.

SMPONP-13011
SAP Mobile Platform Runtime version 2.3 SP04 is a shelf replacement of 2.3.

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

SMPONP-11220
A cluster node fails to start because other nodes were in an abnormal state.
Error messages similar to these in the bootstrap log file are an indication of this problem:
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]
In this case, the mismatch node (10.172.180.47) indicates an abnormal status, and one in which the node does not start.

Workaround: Restart the problematic node.

SMPONP-11042
Error retrieving packages while resynchronizing in the server log.

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. 

Workaround 2: Update the password in SAP Control Center:
  1. Select Start of the navigation path localhost@localhost (running) > Domains >{your domain}-> Connections End of the navigation path.
  2. Select the connection in the connections list.
  3. Click the Properties button.
  4. Update the user name and password, and save. 
SMPONP-10775
Visual C 2005 installation log error in SMPUpgrade.log when upgrading Development and Test (DT) edition of SAP Mobile Platform from version 2.3 to 2.3 SP03.
The actual error codes returned during the upgrade are:
ERROR: return value: 3010
and:
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.

SMPONP-10112
After installing a cluster, and upgrading from version 2.3 SP02 to 2.3 SP03, the error removeDataTierServices.err appears in the silent Install log.
These errors may appear in the silent install log after the upgrade:
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.

SMPONP-10094
Server node fails to upgrade to version 2.3.3 as the Messaging Server upgrade fails.

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. 

SMPONP-4059
Error message after upgrade
After upgrading a cluster installation to 2.3 SP03, the following error message appears in SMP_HOME\SCC-3_2\sccRepoPwdChange\supATUpgrade.log for each Application Node:
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.

RTC-397
QueueNotReadyException appears in <server1> log

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

RTC-393
The SAP Mobile Platform 2.3 installer waits unnecessarily long when upgrading from Sybase Unwired Platform 2.2.X to SAP Mobile Platform 2.3

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.

RTC-363
Potential locked file may cause upgrade to fail.

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.

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. Run the upgrade after the system has restarted.
  5. If step 2 was performed prior to upgrade, set the start-up for the services back to automatic.
RTC-360
Backing up the SAP Mobile Platform Runtime installation fails because the SAP Control Center path is too long.

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

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. Delete the contents of this folder from the command prompt, and not from Windows Explorer.
RTC-306
During the first start of a cluster, the secondary node cannot start because the primary node is bound to an unreachable address.

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.

RTC-299
Uninstallation leaves undeleted registry entry if upgrade of Unwired Platform 2.2.x to SAP Mobile Platform 2.3 required cluster name to be truncated.

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.

RTC-267
Upgrade process stops responding when calling start-unwired-services.bat.

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.

RTC-34
Warning messages when installing secondary SAP Mobile Server node.
When installing a secondary SAP Mobile Server node before the primary server successfully installs, you see a warning similar to this in the server log:
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.

CR-665409
The installation program cannot run in graphical mode.
If the HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags registry key contains an entry that is the path of the installer binary (for example, C:\setup.exe), you see this error, and the installation fails:
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.