I am getting the exact same error as Burnin.Ape.

Stuck at 10%.. can anyone from Symantec advise as to how to fix this?

Thanks
Daniel

How can i check, if the update of the database scheme worked for me?
In my testlab, the upgrade to mr2 worked fine. But in production env. i'm getting the error above.
Turned back to earlier snapshot and did the update again. Same result...

Ideas...?
Thanks

did anyone had luck? or a hint what else can be tried?

Is there a way to run the database upgrade wizard again without going through the entire installation?

I can't really uninstall and reinstall the entire SEPM.

OK, got it. Could you try to do a fresh install of MR-2 on a test system, and then restore the old DB and check if the same error persists ?

You may follow the steps given below to do so -

ON THE OLD INSTALLATION
Copy the "Server Private Key Backup folder" from:
\\ProgramFiles\Symantec\ Symantec Endpoint Protection Manager\Server Private Key Backup


Paste it to another storage area (as it will be deleted during Symantec Endpoint protection Manager uninstall)
Copy the "Data folder" from:
\\ProgramFiles\Symantec\ Symantec Endpoint Protection Manager\Data


Paste it to another storage area.
Copy the "sem5.db" database file from:
\\ProgramFiles\Symantec\ Symantec Endpoint Protection Manager\db


Paste it to another storage area.
Make a note of the "Encryption Password" used during the install.



ON THE NEW INSTALLATION AFTER THE DISASTER RECOVERY  OF OPERATING SYSTEM (OS)
Ensure that the server has the same IP Address and Host Name the Operating System has been Installed.
Install the "Symantec Endpoint Protection Manager" with the "Embedded Database."
Enter the "Encryption Password" that was used on the old "Symantec Endpoint Protection Manager" installation.
Log in to the Console
Click Admin.
Select Tasks> Servers.
Under "View Servers", expand Local Site.
Click the <computer name> that identifies the local site.
Select Tasks.
Click Manage Server Certificate.
In the "Welcome panel", click Next.
In the "Manage Server Certificate panel", select Update the Server Certificate
Click Next.
Under "Select the type of certificate to import", select JKS keystore.
Click Next.
Note: If one of the other certificate types has been implemented, select that type.


In the "JKS Keystore panel", click Browse.
Locate and select the backed up "keystore_<timestamp>.jks" keystore file.
Click OK
Open the "server_<timestamp>.xml" file
Select and copy the "keystore password."
Activate the "JKS Keystore" dialog box.
Paste the "keystore password" into the "Keystore" and "Key boxes."
Note: The only supported paste mechanism is Ctrl + V.


Click Next
Note: If you get an error message that says you have an invalid keystore file, you probably entered invalid passwords. Retry the password copy and paste. (This error message is misleading.)


In the "Complete panel", click Finish.
Stop the services for the "Symantec Embedded database" and the "Symantec Endpoint Protection Manager"
Go to:
\Program Files\Symantec Endpoint Protection Manager\

on the new "Symantec Endpoint Protection Manager" and remove the "Data folder."


Move the "old Data folder" under:
\Program Files\Symantec Endpoint Protection Manager\Data

from the old "Symantec Endpoint Protection Manager" install directory to the new "Symantec Endpoint Protection Manager" install directory.


Create a new folder named "db1" in:
\Program Files\Symantec Endpoint Protection Manager\


Move the "sem5.db" from the old "Symantec Endpoint Protection Manager" install directory.
Click Start>Run.
Type regedit
Navigate to:
HKey_Local_Machine\System\CurrentControlSet\services\ASANYs_sem5\Parameters


Open the value name Parameters and the original database:
\Program Files\Symantec Endpoint Protection Manager\db\sem5.db


Change it to:
\Program Files\Symantec Endpoint Protection Manager\db1\sem5.db


Move the "sem5.db" database:
\Program Files\Symantec Endpoint Protection Manager\db

from the old "Symantec Endpoint Protection Manager"  install directory to the new "Symantec Endpoint Protection Manager" install directory.


Go to Administrative Tools> Data Sources ODBC
Ensure the database connectivity after the changing the database file location to:
\Program Files\Symantec Endpoint Protection Manager\db1\sem5.db


Run the "Migration Server Configuration Wizard."
Click Yes to replace the database after entering the password
Login to the "Symantec Endpoint Protection Manager" using the old password.
Ensure that the Domain ID is same as it was on the old clients.
If it not, follow the direction in the below document to restore the Domain ID.  This will enable client communication http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007082112135948



This is Kedar's KB - so feel free to ask him or me any questions in case you face any issues on the same.

Ok, i tried two sceanrios.

1. Uninstall MR1, install MR2 and restore the keystore.
Same effect.

2. Did a fresh install of MR2 on new empty Server (W2k3) linking to the old DB.
Again, getting "Failed to connect to the server.
Make sure that the server is running and your session has not timed out.
If you can reach the server but cannot log on, make sure that you provided the correct parameters.
If you are experiencing network issues, contact your system administrator. ErrorCode: 0x80020000  [Site: Symantec EndPoint Security]  [Server: blackpearl]"

Why do i get this message? I'm already logged in. I can navigate through the console.

Everything i try ends in error. And its always the same error.
What does the table ANOMALYDETECTIONS stands for?
 
Just for testing reasons: I tried my very first DB Backup. On this, i had about 10 clients in the DB, only a few policies, nothing special.
But in the upgrade wizard log file, i'm getting the old error again.
****************************************************************************
SQL Exception:
SQL Command: ALTER TABLE ANOMALYDETECTIONS ADD ID CHAR(32) NOT NULL DEFAULT upper(replace(newid(),'-',''))
SQLState:  S1000
Message:  Column names in each table must be unique. Column name 'ID' in table 'ANOMALYDETECTIONS' is specified more than once.
Vendor:  2705
java.sql.SQLException: Column names in each table must be unique. Column name 'ID' in table 'ANOMALYDETECTIONS' is specified more than once.
 at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:364)
 at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2754)
 at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2195)
 at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:620)
 at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:483)
 at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:445)
 at net.sourceforge.jtds.jdbc.JtdsStatement.executeImpl(JtdsStatement.java:623)
 at net.sourceforge.jtds.jdbc.JtdsStatement.executeUpdate(JtdsStatement.java:1042)
 at net.sourceforge.jtds.jdbc.JtdsStatement.executeUpdate(JtdsStatement.java:999)
 at com.sygate.scm.server.db.util.DbHelper.execCommandFromScript(DbHelper.java:152)
 at com.sygate.scm.server.db.util.SqlDbHelper.upgrade(SqlDbHelper.java:237)
 at com.sygate.scm.server.upgrade.Upgrade.upgradeDatabaseSchema(Upgrade.java:708)
 at com.sygate.scm.server.upgrade.Upgrade.doUpgrade(Upgrade.java:198)
 at com.sygate.scm.server.upgrade.ui.UpgradeTask$ActualTask.<init>(UpgradeTask.java:190)
 at com.sygate.scm.server.upgrade.ui.UpgradeTask$1.construct(UpgradeTask.java:95)
 at com.sygate.scm.server.upgrade.ui.SwingWorker$2.run(SwingWorker.java:121)
 at java.lang.Thread.run(Thread.java:595)
java.sql.SQLException: Failed to upgrade schema in execCommandFromScript: java.sql.SQLException: Column names in each table must be unique. Column name 'ID' in table 'ANOMALYDETECTIONS' is specified more than once.
 at com.sygate.scm.server.db.util.DbHelper.execCommandFromScript(DbHelper.java:163)
 at com.sygate.scm.server.db.util.SqlDbHelper.upgrade(SqlDbHelper.java:237)
 at com.sygate.scm.server.upgrade.Upgrade.upgradeDatabaseSchema(Upgrade.java:708)
 at com.sygate.scm.server.upgrade.Upgrade.doUpgrade(Upgrade.java:198)
 at com.sygate.scm.server.upgrade.ui.UpgradeTask$ActualTask.<init>(UpgradeTask.java:190)
 at com.sygate.scm.server.upgrade.ui.UpgradeTask$1.construct(UpgradeTask.java:95)
 at com.sygate.scm.server.upgrade.ui.SwingWorker$2.run(SwingWorker.java:121)
 at java.lang.Thread.run(Thread.java:595)
java.sql.SQLException: Failed to upgrade schema: java.sql.SQLException: Failed to upgrade schema in execCommandFromScript: java.sql.SQLException: Column names in each table must be unique. Column name 'ID' in table 'ANOMALYDETECTIONS' is specified more than once.
 at com.sygate.scm.server.db.util.SqlDbHelper.upgrade(SqlDbHelper.java:249)
 at com.sygate.scm.server.upgrade.Upgrade.upgradeDatabaseSchema(Upgrade.java:708)
 at com.sygate.scm.server.upgrade.Upgrade.doUpgrade(Upgrade.java:198)
 at com.sygate.scm.server.upgrade.ui.UpgradeTask$ActualTask.<init>(UpgradeTask.java:190)
 at com.sygate.scm.server.upgrade.ui.UpgradeTask$1.construct(UpgradeTask.java:95)
 at com.sygate.scm.server.upgrade.ui.SwingWorker$2.run(SwingWorker.java:121)
 at java.lang.Thread.run(Thread.java:595)
Launching log file ...
****************************************************************************
If i try with a new fresh install, new DB, everything new. I don't get this message...
 
If i view the table ANOMALYDETECTIONS in the SQL Management Studio, there's no entry. No entry in the fresh DB and no entry in my original DB. It's just NULL.

Was this ever resolved? I have the exact same problem!

Thanks!