Known Issues with Installing, Uninstalling, and Upgrading

If Sybase Unwired Platform processes are running while attempting to uninstall the product, the uninstaller cannot complete the uninstallation.

Workaround: Manually stop any running Sybase Unwired Platform processes before uninstalling the product.

The following error may occur when upgrading Sybase Unwired Platform to the latest version.

Sybase Messaging Server was NOT successfully updated. Value 0x0 not found in Install Success registry entry.  

You can also find the following error in the system event log:

Database version check failed. Database version 'nnnnn' doesn't match expected version 'NNNNN'. This may be caused by an upgrade failure. Until this issue is fixed, the services will not start. 

Workaround: In most cases, the failure occurs due to issues in CDB connectivity. Re-running the messaging server installer as follows will fix the issue in most cases. 

The jca_template.properties file was not installed with Sybase Unwired Platform version 2.2.

Workaround: Copy a jca_template.properties file to SUP_HOME\Servers\UnwiredServer\Repository\Instance\com\sybase\djc\connector\ConnectionFactory, restart the server, the error disappears.

dbg, iMO: command: C:\Sybase\UnwiredPlatform\Servers\MessagingServer\UninstallMessaging.bat 
dbg, iMO: arguments: 
err, ERROR: return value: 1

Workaround: This error can be safely ignored.

When you uninstall the Unwired Platform Runtime from a Windows Server 2003 machine, by silent uninstallation or uninstallation wizard, the Uninstallers folder is not removed.

Workaround: Manually remove the remaining folder after uninstalling.

Database files and log files that are used as part of the Sybase Unwired Platform data tier can be encrypted. The databases that use this database type are the CDB, cluster database, monitoring database, and the domain log database.

Workaround: decrypt the database files, then upgrade. See CREATE DECRYPTED DATABASE statement

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.

 2013-05-23 11:31:25.606 ERROR Cluster ScheduledTask:SynchronizeNode
      [com.sybase.sup.server.cluster.ClusterUtils] [] [] Cluster Synchronization failed. Message :
      The sync data could not be found in SYNC_DATA table for domain: 2,version: 8   java.lang.RuntimeException: The sync data could not be found in SYNC_DATA table for domain:
      2,version: 8                   at
        com.sybase.sup.server.cluster.ClusterUtils.downloadSyncData(ClusterUtils.java:1239)                   at
        com.sybase.sup.server.cluster.ClusterUtils.syncNodeForDomain(ClusterUtils.java:223)                   at
        com.sybase.sup.server.cluster.ClusterUtils.syncNode(ClusterUtils.java:693)                   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)                   at
        sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)                   at
        sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)                   at java.lang.reflect.Method.invoke(Method.java:597)                   at
        com.sybase.djc.scheduler.ScheduledTask.execute(ScheduledTask.java:1155)                   at
        com.sybase.djc.scheduler.ScheduledTask_DJC.access$001(ScheduledTask_DJC.java:4)                   at
        com.sybase.djc.scheduler.ScheduledTask_DJC$1.invoke(ScheduledTask_DJC.java:29)                   at
        com.sybase.djc.transaction.TransactionManager.invokeNotSupported1(TransactionManager.java:682)                   at
        com.sybase.djc.transaction.TransactionManager.invokeNotSupported(TransactionManager.java:644)                   at
        com.sybase.djc.scheduler.ScheduledTask_DJC.execute(ScheduledTask_DJC.java:47)                   at
        com.sybase.djc.scheduler.ScheduledTask.run(ScheduledTask.java:961)  

Workaround: Ignore the error message. Cluster synchronization will complete successfully in next synchronization loop, generally, within 60 seconds.

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.

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 Sybase Unwired Platform Runtime installation, you must delete the contents of SUP_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.

When running the 2.1.3, 2.2 SP01 PL00 or 2.2 SP01 PL01 upgrade from a command prompt window with a path that has a lowercase drive letter, the update may produce an error that indicates that it was unable to undeploy GWC.war. This only affects the listed updates with the specific circumstance where the drive letter is lowercase.

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

Workaround: Online upgrade is not supported. You must stop all the Sybase Unwired Platform services, including the data tier, before running the upgrade installer.

The Runtime installer requires the supAdmin user to exist in order for an upgrade installation to complete normally. If you removed the supAdmin user, the installer cannot perform the test package deployment that verifies that the upgraded Unwired Server is functioning properly. The installer displays this message:

 The Unwired Platform admin login information
        provided were not valid. Upgrade was completed but test deploying a package to server for
        verification was skipped.   

Workaround: Ignore the message. You can perform a manual package deployment if you wish to be sure that the upgraded server is function properly. See Creating new users in SQL Anywhere Server - Database Administration, available at http://infocenter.sybase.com/help/topic/com.sybase.help.sqlanywhere.12.0.0/dbadmin/umannew.html.

Sybase Messaging Server installation completed with errors.
**Error!!! Error!!!**
The Messaging installer completed with the following errors. These errors will have to be addressed before the services become functional.
Please refer to documentation for recovery process.
Database upgrade failed

Additionally, you can see the following message in the SUP_HOME\Servers\MessagingServer\Bin\Scripts\DBUpgraderTrace_xxxxxxxx.txt file.

-- Upgrade started at 11/6/2012 4:28:31 PM
Downgrading is not supported
-- Caught unexpected exception: Downgrading is not supported
Got global error [Downgrading is not supported]

This error occurs because the installer incorrectly tries to upgrade the database when it should not.

Workaround: If you see this error when adding a new secondary node, you can ignore it, and proceed with applying the patch. By running the patch installation (for example Sybase Unwired Platform 2.2 SP02), you can complete the installation.

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

Workaround: Ignore this warning, or install the secondary Unwired 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.

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: 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 Unwired Platform, the Program Compatibility Assistant shows:

This program might not have uninstalled correctly.

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

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

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