I'm getting this message when trying to upgrade. I verified I can login with sem5 account and it is db_owner.

Going to what version of 12.1?

Does this apply:

http://www.symantec.com/docs/TECH162182

Hi,

Thank you for posting in Symantec community.

Could you check with sa user? 

Yes, should have mentioned. 12.1 RU5. The latest.

Ok I'll go to the admin and check that. But I thought I should be able to with the sem5 account, so that there's no need to deal with the sa account. Anyhow, I will check.

You need sa

Still getting the same error. DB admin gave me SA admin rights and I still could not login. He came by and tried his sysadmin account to no avail.

Where can I see anerror log for this from SEPM point of view? I will also check DB error logs to see if I'm hitting the correct server.

thanks.

I got through the upgrade wizard. I had to give new permissions to sem5 user account.

Now I'm getting this during the "Step One: Database Server Authentication" window:

Sem5 account is db owner. Does this look like an account issue? 

Hi,

Could you attach scm-server-0.log & INSTALL_LOG.ERR in the directory C:\Program Files\Symantec\Symantec Endpoint Protection\tomcat\logs\

It could be an account issue.

Created an account with SA rights and now we are getting a different error. 
"While reconfiguring the server, you are not allowed to change the credentials with which the database was created"

Check the symantec article

Symantec Endpoint Protection 12.1: SQL server login credentials cannot be verified when upgrading the Manager

24-Oct-2014 3:00:12 PM  STDERR: java.sql.SQLException: Invalid object name 'LOCAL_METADATA'.
24-Oct-2014 3:00:12 PM  STDERR:     at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:372)
24-Oct-2014 3:00:12 PM  STDERR:     at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2988)
24-Oct-2014 3:00:12 PM  STDERR:     at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2421)
24-Oct-2014 3:00:12 PM  STDERR:     at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:671)
24-Oct-2014 3:00:12 PM  STDERR:     at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQLQuery(JtdsStatement.java:505)
24-Oct-2014 3:00:12 PM  STDERR:     at net.sourceforge.jtds.jdbc.JtdsStatement.executeQuery(JtdsStatement.java:1427)
24-Oct-2014 3:00:12 PM  STDERR:     at com.sygate.scm.server.util.ServerUtil.getDBSchemaVersion(ServerUtil.java:1685)
24-Oct-2014 3:00:12 PM  STDERR:     at com.sygate.scm.install.ui.MainFrame.configureDB(MainFrame.java:1188)
24-Oct-2014 3:00:12 PM  STDERR:     at com.sygate.scm.install.ui.MainFrame.nextBtnActionPerformed(MainFrame.java:4466)
24-Oct-2014 3:00:12 PM  STDERR:     at com.sygate.scm.install.ui.MainFrame.access$400(MainFrame.java:277)
24-Oct-2014 3:00:12 PM  STDERR:     at com.sygate.scm.install.ui.MainFrame$5$1.construct(MainFrame.java:4030)
24-Oct-2014 3:00:12 PM  STDERR:     at com.sygate.scm.util.SwingWorker$2.run(SwingWorker.java:145)
24-Oct-2014 3:00:12 PM  STDERR:     at java.lang.Thread.run(Thread.java:745)
24-Oct-2014 3:00:12 PM  STDERR: java.sql.SQLException: Invalid object name 'LOCAL_METADATA'.
24-Oct-2014 3:00:12 PM  STDERR:     at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:372)
24-Oct-2014 3:00:12 PM  STDERR:     at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2988)
24-Oct-2014 3:00:12 PM  STDERR:     at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2421)
24-Oct-2014 3:00:12 PM  STDERR:     at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:671)
24-Oct-2014 3:00:12 PM  STDERR:     at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQLQuery(JtdsStatement.java:505)
24-Oct-2014 3:00:12 PM  STDERR:     at net.sourceforge.jtds.jdbc.JtdsStatement.executeQuery(JtdsStatement.java:1427)
24-Oct-2014 3:00:12 PM  STDERR:     at com.sygate.scm.server.util.ServerUtil.getDBSchemaVersion(ServerUtil.java:1685)
24-Oct-2014 3:00:12 PM  STDERR:     at com.sygate.scm.install.ui.MainFrame.configureDB(MainFrame.java:1188)
24-Oct-2014 3:00:12 PM  STDERR:     at com.sygate.scm.install.ui.MainFrame.nextBtnActionPerformed(MainFrame.java:4466)
24-Oct-2014 3:00:12 PM  STDERR:     at com.sygate.scm.install.ui.MainFrame.access$400(MainFrame.java:277)
24-Oct-2014 3:00:12 PM  STDERR:     at com.sygate.scm.install.ui.MainFrame$5$1.construct(MainFrame.java:4030)
24-Oct-2014 3:00:12 PM  STDERR:     at com.sygate.scm.util.SwingWorker$2.run(SwingWorker.java:145)
24-Oct-2014 3:00:12 PM  STDERR:     at java.lang.Thread.run(Thread.java:745)

Hi,

Make sure Instead of the default dbo schema, custom named schema is not configured. If so mention correct schema name.

Also attach complete set of logs. Instead of copy/paste attach the entire file.

We need scm-server-0.log, Catalina.out and Install_log.err

All the files should be present here: C:\Program Files\Symantec\Symantec Endpoint Protection\tomcat\logs\

I tried the domain account and it says you cannot use a different username than the one you created the database with. I looked on the database error logs and saw this:
"Login failed for user 'sem5'. Reason: Failed to open the explicitly specified database."

Any insight on this? thanks.

I created a new database sem5_DEV successfully. The bottom screenshot shows the top window with schema 'sem5' which has been the issue. Bottom window works which has the 'dbo' schema. 

I cannot change the schema to 'dbo', as the error I get is user 'sem5' is mapped to the database.

I have a case opened with Symantec for 3 weeks now in parallel with forum post and searching hoping someone can help with this issue. I have supplied Symantec with every log file using the sym help tool. And raised to 3rd level support still to no avail.

Does anyone have a different approach? Can't I create a brabd new database and import the data from the original database?

Just to be clear, an account with 'SA' rights is OR isn't good enough? 

Install a new SEPM, with new DB, once installed,import the db from SEPM.

I did a new install and able to connect successfully.

Can you explain the import process, is it from SEPM or MSSQL. I have a backup of the DB generated from SEPM database backup (.zip), should we use that?

from sepm also you can do

yes use the backup generated from SEPM, hope you have installed same version of SEPM as the backup

here is the document

http://www.symantec.com/business/support/index?page=content&id=TECH102738

If you now have installed a 12.1.5 SEPM and have the old 11.x SEPM running, you can do what I did back then and "move" the Clients to the new server either by

- doing an uninstall/install,

- upgrading the sylink via Sylinkreplacer

- use this nifty trick: https://www-secure.symantec.com/connect/forums/moving-clients-sep11-sep12-site-without-manually-replacing-sylinkxml

The latter worked great for me.

Edit: You can also Export and Inport all the Policies you had in SEP11 but I strongly advise you to recreate them as the v12 has a ton more/different settings than 11.

I did that and this during the process:

However I am now able to login to SEPM and see my policies and clients. Although the clients ALL say 'Offline' 

Thats good, did you update the key ? 

When you run the Management Configuration Wizard, did you attached the latest Server Private Key??

Its explained here

http://www.symantec.com/business/support/index?page=content&id=TECH160736

if clients are less , use this method

http://www.symantec.com/business/support/index?page=content&id=TECH199124

yes I did. but all clients still 'offline' according to SEPM. And logging into a few of them, no green light on the badge in the taskbar.

My worry is that schema error message posted above.

And twice now, the clients listed in the clients container disappear after a while.

Somethings not right. I'm thinking of goign back to version 11 and backtracking the steps.

Those clients info are already in DB. there is a cert missmatch thats why they would disappear.

I would run management server configwizard one more time to see if it throws up that error again.

are those clients in user mode?