hye everybody,
i just write these few lines for ones who could encounter same issue i had while upgrading from SEPM 12RU1 to SEPM 12RU2 today.
During DB upgrade process after files installation process, the upgrade ended with such informations:
2012-12-06 14:42:16.662 THREAD 20 SEVERE: com.sygate.scm.server.util.ServerException: Erreur de serveur inattendue.
2012-12-06 14:42:16.662 THREAD 20 SEVERE: at com.sygate.scm.server.configmanager.ConfigManager.startTransaction(ConfigManager.java:279)
2012-12-06 14:42:16.662 THREAD 20 SEVERE: at com.sygate.scm.server.upgrade.ui.Main.createRecoveryFile(Main.java:719)
2012-12-06 14:42:16.662 THREAD 20 SEVERE: at com.sygate.scm.server.upgrade.Upgrade.doUpgrade(Upgrade.java:436)
2012-12-06 14:42:16.662 THREAD 20 SEVERE: at com.sygate.scm.server.upgrade.ui.UpgradeTask.go(UpgradeTask.java:127)
2012-12-06 14:42:16.662 THREAD 20 SEVERE: at com.sygate.scm.server.upgrade.ui.UpgradeProgressPanel$2.construct(UpgradeProgressPanel.java:138)
2012-12-06 14:42:16.662 THREAD 20 SEVERE: at com.sygate.scm.util.SwingWorker$2.run(SwingWorker.java:145)
2012-12-06 14:42:16.662 THREAD 20 SEVERE: at java.lang.Thread.run(Thread.java:722)
2012-12-06 14:42:16.662 THREAD 20 SEVERE: Caused by: com.sygate.scm.server.metadata.MetadataException:
2012-12-06 14:42:16.662 THREAD 20 SEVERE: at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:965)
2012-12-06 14:42:16.662 THREAD 20 SEVERE: at com.sygate.scm.server.metadata.MetadataManager.startTransaction(MetadataManager.java:86)
2012-12-06 14:42:16.662 THREAD 20 SEVERE: at com.sygate.scm.server.metadata.MetadataManager.startTransaction(MetadataManager.java:82)
2012-12-06 14:42:16.662 THREAD 20 SEVERE: at com.sygate.scm.server.configmanager.ConfigManager.startTransaction(ConfigManager.java:277)
2012-12-06 14:42:16.662 THREAD 20 SEVERE: ... 6 more
2012-12-06 14:42:16.662 THREAD 20 SEVERE: Caused by: java.sql.SQLException: [Sybase][JDBC Driver][SQL Anywhere]Database server not found
2012-12-06 14:42:16.662 THREAD 20 SEVERE: at sybase.jdbc4.sqlanywhere.IDriver.makeODBCConnection(Native Method)
2012-12-06 14:42:16.662 THREAD 20 SEVERE: at sybase.jdbc4.sqlanywhere.IDriver.connect(IDriver.java:772)
2012-12-06 14:42:16.662 THREAD 20 SEVERE: at java.sql.DriverManager.getConnection(DriverManager.java:579)
2012-12-06 14:42:16.662 THREAD 20 SEVERE: at java.sql.DriverManager.getConnection(DriverManager.java:243)
2012-12-06 14:42:16.662 THREAD 20 SEVERE: at sybase.jdbc4.sqlanywhere.ASADataSource.getConnection(ASADataSource.java:317)
2012-12-06 14:42:16.662 THREAD 20 SEVERE: at com.sygate.scm.server.db.util.DatabaseUtilities.getDataSourceDBConnection(DatabaseUtilities.java:398)
2012-12-06 14:42:16.662 THREAD 20 SEVERE: at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:285)
2012-12-06 14:42:16.662 THREAD 20 SEVERE: at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:270)
2012-12-06 14:42:16.662 THREAD 20 SEVERE: at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:260)
2012-12-06 14:42:16.662 THREAD 20 SEVERE: at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:963)
2012-12-06 14:42:16.662 THREAD 20 SEVERE: ... 9 more
2012-12-06 14:42:16.662 THREAD 20 SEVERE: Upgrade.doUpgrade com.sygate.scm.server.util.ServerException: Erreur de serveur inattendue.
2012-12-06 14:45:06.257 THREAD 15 INFO: UpgradeFinalPanel >> saveStage > Launching log file...
In fact my pb was occuring because my DB files were installed on a separate disk (E:\SEPM\DB) than binary SEPM files (D:\product\SEPM\). althought the SEPM 12RU2 setup was trying to start the DB in D:\product\SEPM\DB folder (or something like that) instead of the right db location on E:\SEPM\DB. Of course it could'nt find any db files at D:\product\SEPM\DB and couldn't start the SEPM database to go on the install process.
Even manualy, the SQLANYs_sem5 (in french for my case called:"Base de données intégrée Symantec") service couldn't start.
To troubleshoot this issue, i'd simply corrected the wrong DB path that the setup changed into the registry for SQLANYs_sem5:
correct the "parameters" key under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SQLANYs_sem5\Parameters with th good DB path.
--> the DB then started normaly.
After that i restarted the setup program to relaunch the upgrade process, all was ok until DB processing during which i had to rewrite the last registry key (that had been remisconfigured by the setup program) not waiting the setup program fails. As a result of this registery change during Db processing, the setup program had been able to end its job normaly.
But the story is not finished yet because the semsrv was unable to start dispite of all.
to make it start with success, the way i took was to make a repair action (config panel, add/remove...) to the SEPM installation. During this process, another DB processing occurs after auto-launching the Server Configuration Assistant Wizzard and fails again. Same issue, Same troubleshoot : correct again the "parameters" registery key for SQLANYs_sem5 service during this processing and all will go on as if nothing had appened !
Hope this will help those who are worrying not to get their SEPM work as expected after this upgrade or other situations where SEMSRV won't start.