This issue has been solved.

Upgrade Server to 12.1.1000.157 failed - The upgrade tool cannot grant the database user privilege.

Created: 26 Jul 2012 | Updated: 14 Oct 2012
Dushan Gomez's picture
Dushan Gomez
Login to vote
0 0 Votes

Hi,

I'm in the middle of upgrading the SEPM from v11.0.6005 into SEPM v12.1 RU1 and it is stuck in running the upgrade.bat file ?

My Database is SQL Server 2005 SP4

I have input / use the same account for the Windows Authentication which is also the db_owner and even got sysadmin role but always end up with the following error:

 

Initializing...
The upgrade tool cannot grant the database user privilege. You must provide the database user authentication mode (SQL/WIN), system administrator account and password when launching the upgrade tool, and the database user authentication mode must be the same as used in SEPM.
Error occurred

can anyone please let me know what to do as I cannot login to my SEPM console and none of my clients are updating at the moment.

Thanks in advance

Quick Look Solution

HI, User issue has been 

HI,

User issue has been  resolved kindly check user last thread

https://www-secure.symantec.com/connect/forums/how-come-i-got-duplicated-sep-client-my-sepm-database

https://www-secure.symantec.com/connect/forums/wrong-sep-client-installed-64-bit-server

Filed Under

Tags:
, , , , , , , , , , ,

Comments

Dushan Gomez
26
Jul
2012
Votes
+1

Error log attached

 


2012-07-26 18:56:20.244 THREAD 1 SEVERE: ================== Server Environment ===================

2012-07-26 18:56:20.244 THREAD 1 SEVERE: os.name = Windows Server 2008

2012-07-26 18:56:20.244 THREAD 1 SEVERE: os.version = 6.0

2012-07-26 18:56:20.244 THREAD 1 SEVERE: os.arch = x86

2012-07-26 18:56:20.244 THREAD 1 SEVERE: java.version = 1.6.0_26

2012-07-26 18:56:20.244 THREAD 1 SEVERE: java.vendor = Sun Microsystems Inc.

2012-07-26 18:56:20.244 THREAD 1 SEVERE: java.vm.name = Java HotSpot(TM) Client VM

2012-07-26 18:56:20.244 THREAD 1 SEVERE: java.vm.version = 20.1-b02

2012-07-26 18:56:20.244 THREAD 1 SEVERE: java.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\jre

2012-07-26 18:56:20.244 THREAD 1 SEVERE: catalina.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat

2012-07-26 18:56:20.244 THREAD 1 SEVERE: java.user = null

2012-07-26 18:56:20.244 THREAD 1 SEVERE: user.language = en

2012-07-26 18:56:20.244 THREAD 1 SEVERE: user.country = AU

2012-07-26 18:56:20.244 THREAD 1 SEVERE: scm.server.version = 12.1.1000.157

2012-07-26 18:56:20.244 THREAD 1 INFO: Main>> Main> Upgrade parameters 

2012-07-26 18:56:20.244 THREAD 1 INFO: Main>> Main> Upgrade args length = 0

2012-07-26 18:56:20.244 THREAD 1 INFO: Main>> Main> Unable to get the command-line arguments

2012-07-26 18:56:20.244 THREAD 1 INFO: Main>> Main> Server Home: C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat

2012-07-26 18:56:21.337 THREAD 1 INFO: Main>> Main> You are using MSSQL server.

2012-07-26 18:56:21.400 THREAD 1 SEVERE: java.sql.SQLException: Login failed for user ''. The user is not associated with a trusted SQL Server connection.

2012-07-26 18:56:21.400 THREAD 1 SEVERE:  at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)

2012-07-26 18:56:21.400 THREAD 1 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)

2012-07-26 18:56:21.400 THREAD 1 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)

2012-07-26 18:56:21.400 THREAD 1 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.login(TdsCore.java:610)

2012-07-26 18:56:21.400 THREAD 1 SEVERE:  at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:345)

2012-07-26 18:56:21.400 THREAD 1 SEVERE:  at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)

2012-07-26 18:56:21.400 THREAD 1 SEVERE:  at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:184)

2012-07-26 18:56:21.400 THREAD 1 SEVERE:  at net.sourceforge.jtds.jdbcx.JtdsDataSource.getConnection(JtdsDataSource.java:188)

2012-07-26 18:56:21.400 THREAD 1 SEVERE:  at net.sourceforge.jtds.jdbcx.JtdsDataSource.getConnection(JtdsDataSource.java:137)

2012-07-26 18:56:21.400 THREAD 1 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDataSourceDBConnection(DatabaseUtilities.java:522)

2012-07-26 18:56:21.400 THREAD 1 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:419)

2012-07-26 18:56:21.400 THREAD 1 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:404)

2012-07-26 18:56:21.400 THREAD 1 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:394)

2012-07-26 18:56:21.400 THREAD 1 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.testDBConnection(DatabaseUtilities.java:2876)

2012-07-26 18:56:21.400 THREAD 1 SEVERE:  at com.sygate.scm.server.upgrade.ui.Main.<init>(Main.java:221)

2012-07-26 18:56:21.400 THREAD 1 SEVERE:  at com.sygate.scm.server.upgrade.ui.Main.main(Main.java:763)

2012-07-26 18:56:21.400 THREAD 1 INFO: UpgradeDBUtil: testDBConnection: Exception - Can't connect to database.

2012-07-26 18:56:21.400 THREAD 1 INFO: Main>> Main> DB test connection failed. Cannot continue with upgrade tool.

2012-07-26 18:56:21.400 THREAD 1 INFO: Main>> executePreLaunchSteps> DbVersion: 11.0.6.0 schemaVersionFromDB: 11.0.6.0 isSpm51Mr7: false hasOtherOSAgents: false dbcompanySize: 2 dbConnected: false

2012-07-26 18:56:21.400 THREAD 1 INFO: Main>> checkUpgradeFeasibility> Checking for upgrade feasibility, current schema version = 12.1.1.0, schema version from db = 11.0.6.0

2012-07-26 18:56:21.416 THREAD 1 INFO: Main>> launchMainFrame> Launching the UI

2012-07-26 18:56:21.712 THREAD 1 INFO: Has valid SAV license

2012-07-26 18:56:21.712 THREAD 1 INFO: Info>> No SNAC license file in C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\etc\license

2012-07-26 18:56:21.728 THREAD 1 INFO: isUserDBOwner: Couldn't verify sem5 user is db_owner.

2012-07-26 18:56:21.728 THREAD 1 SEVERE: java.sql.SQLException: Login failed for user ''. The user is not associated with a trusted SQL Server connection.

2012-07-26 18:56:21.728 THREAD 1 SEVERE:  at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)

2012-07-26 18:56:21.728 THREAD 1 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)

2012-07-26 18:56:21.728 THREAD 1 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)

2012-07-26 18:56:21.728 THREAD 1 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.login(TdsCore.java:610)

2012-07-26 18:56:21.728 THREAD 1 SEVERE:  at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:345)

2012-07-26 18:56:21.728 THREAD 1 SEVERE:  at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)

2012-07-26 18:56:21.728 THREAD 1 SEVERE:  at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:184)

2012-07-26 18:56:21.728 THREAD 1 SEVERE:  at java.sql.DriverManager.getConnection(DriverManager.java:582)

2012-07-26 18:56:21.728 THREAD 1 SEVERE:  at java.sql.DriverManager.getConnection(DriverManager.java:185)

2012-07-26 18:56:21.728 THREAD 1 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDatabaseConnection(DatabaseUtilities.java:742)

2012-07-26 18:56:21.728 THREAD 1 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.isUserDBOwner(DatabaseUtilities.java:2466)

2012-07-26 18:56:21.728 THREAD 1 SEVERE:  at com.sygate.scm.server.upgrade.UpgradeDBUtil.isUserDBOwner(UpgradeDBUtil.java:679)

2012-07-26 18:56:21.728 THREAD 1 SEVERE:  at com.sygate.scm.server.upgrade.ui.MainFrame.areUserCredRequired(MainFrame.java:431)

2012-07-26 18:56:21.728 THREAD 1 SEVERE:  at com.sygate.scm.server.upgrade.ui.MainFrame.<init>(MainFrame.java:110)

2012-07-26 18:56:21.728 THREAD 1 SEVERE:  at com.sygate.scm.server.upgrade.ui.Main.launchMainFrame(Main.java:389)

2012-07-26 18:56:21.728 THREAD 1 SEVERE:  at com.sygate.scm.server.upgrade.ui.Main.<init>(Main.java:290)

2012-07-26 18:56:21.728 THREAD 1 SEVERE:  at com.sygate.scm.server.upgrade.ui.Main.main(Main.java:763)

2012-07-26 18:56:21.744 THREAD 1 INFO: isDefaultWebSite: null

2012-07-26 18:56:21.744 THREAD 1 INFO: iisPort: 80

2012-07-26 18:56:21.744 THREAD 1 INFO: bReplaceIISwithApache: false

2012-07-26 18:56:21.775 THREAD 1 INFO: isLicenseInstallationValid:  sep.slf =true  OD file=true

2012-07-26 18:57:13.087 THREAD 16 INFO: getDatabaseConnectionWithNTLMv2Retry isWinAuth : true

2012-07-26 18:57:13.087 THREAD 16 INFO: getDatabaseConnectionWithNTLMv2Retry trying NTLMv2 first jdbcURL: : jdbc:jtds:sqlserver://SQL-DBServer:1433/sem5;preparesql=2;;domain=MyCompanyDomain;useNTLMv2=true

2012-07-26 18:57:14.212 THREAD 16 INFO: scm.webserver.https.port is not found in conf.properties

2012-07-26 18:57:14.212 THREAD 16 INFO: scm.iis.https.port is not found in conf.properties

2012-07-26 18:57:14.212 THREAD 16 INFO: scm.iisproxy.http.port is not found in conf.properties

2012-07-26 18:57:14.212 THREAD 16 INFO: scm.iisproxy.https.port is not found in conf.properties

2012-07-26 18:57:14.228 THREAD 16 INFO: Executing command - stop semsrv

2012-07-26 18:57:19.306 THREAD 16 INFO: The Symantec Endpoint Protection Manager service is stopping..

2012-07-26 18:57:19.306 THREAD 16 INFO: The Symantec Endpoint Protection Manager service was stopped successfully.

2012-07-26 18:57:19.306 THREAD 16 INFO: 

2012-07-26 18:57:19.306 THREAD 16 INFO: Waiting for service termination: semsrv

2012-07-26 18:57:19.306 THREAD 16 INFO: Checking whether the service is running semsrv

2012-07-26 18:57:19.384 THREAD 16 INFO: Service is not running.

2012-07-26 18:57:19.384 THREAD 16 INFO: Executing command - stop semwebsrv

2012-07-26 18:57:24.446 THREAD 16 INFO: The Symantec Endpoint Protection Manager Webserver service is stopping..

2012-07-26 18:57:24.446 THREAD 16 INFO: The Symantec Endpoint Protection Manager Webserver service was stopped successfully.

2012-07-26 18:57:24.446 THREAD 16 INFO: 

2012-07-26 18:57:25.446 THREAD 16 INFO: scm.webserver.https.port is not found in conf.properties

2012-07-26 18:57:25.446 THREAD 16 INFO: scm.iis.https.port is not found in conf.properties

2012-07-26 18:57:25.446 THREAD 16 INFO: scm.iisproxy.http.port is not found in conf.properties

2012-07-26 18:57:25.446 THREAD 16 INFO: scm.iisproxy.https.port is not found in conf.properties

2012-07-26 18:57:26.446 THREAD 16 INFO: scm.webserver.https.port is not found in conf.properties

2012-07-26 18:57:26.446 THREAD 16 INFO: scm.iis.https.port is not found in conf.properties

2012-07-26 18:57:26.446 THREAD 16 INFO: scm.iisproxy.http.port is not found in conf.properties

2012-07-26 18:57:26.446 THREAD 16 INFO: scm.iisproxy.https.port is not found in conf.properties

2012-07-26 18:57:47.352 THREAD 23 INFO: Initializing ...

2012-07-26 18:57:47.384 THREAD 23 INFO: Executing command - stop semsrv

2012-07-26 18:57:47.462 THREAD 23 INFO: The Symantec Endpoint Protection Manager service is not started.

2012-07-26 18:57:47.462 THREAD 23 INFO: 

2012-07-26 18:57:47.462 THREAD 23 INFO: More help is available by typing NET HELPMSG 3521.

2012-07-26 18:57:47.462 THREAD 23 INFO: 

2012-07-26 18:57:47.462 THREAD 23 INFO: Waiting for service termination: semsrv

2012-07-26 18:57:47.462 THREAD 23 INFO: Checking whether the service is running semsrv

2012-07-26 18:57:47.540 THREAD 23 INFO: Service is not running.

2012-07-26 18:57:47.540 THREAD 23 INFO: Executing command - stop semwebsrv

2012-07-26 18:57:47.602 THREAD 23 INFO: The Symantec Endpoint Protection Manager Webserver service is not started.

2012-07-26 18:57:47.602 THREAD 23 INFO: 

2012-07-26 18:57:47.602 THREAD 23 INFO: More help is available by typing NET HELPMSG 3521.

2012-07-26 18:57:47.602 THREAD 23 INFO: 

2012-07-26 18:57:47.602 THREAD 23 INFO: Stop SemSrv done.

2012-07-26 18:57:47.602 THREAD 23 INFO: Action Start:0

2012-07-26 18:57:47.618 THREAD 23 INFO: initDataSource 

2012-07-26 18:57:47.634 THREAD 23 SEVERE: java.sql.SQLException: Login failed for user ''. The user is not associated with a trusted SQL Server connection.

2012-07-26 18:57:47.634 THREAD 23 SEVERE:  at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)

2012-07-26 18:57:47.634 THREAD 23 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)

2012-07-26 18:57:47.634 THREAD 23 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)

2012-07-26 18:57:47.634 THREAD 23 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.login(TdsCore.java:610)

2012-07-26 18:57:47.634 THREAD 23 SEVERE:  at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:345)

2012-07-26 18:57:47.634 THREAD 23 SEVERE:  at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)

2012-07-26 18:57:47.634 THREAD 23 SEVERE:  at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:184)

2012-07-26 18:57:47.634 THREAD 23 SEVERE:  at net.sourceforge.jtds.jdbcx.JtdsDataSource.getConnection(JtdsDataSource.java:188)

2012-07-26 18:57:47.634 THREAD 23 SEVERE:  at net.sourceforge.jtds.jdbcx.JtdsDataSource.getConnection(JtdsDataSource.java:137)

2012-07-26 18:57:47.634 THREAD 23 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDataSourceDBConnection(DatabaseUtilities.java:522)

2012-07-26 18:57:47.634 THREAD 23 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:419)

2012-07-26 18:57:47.634 THREAD 23 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:404)

2012-07-26 18:57:47.634 THREAD 23 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:394)

2012-07-26 18:57:47.634 THREAD 23 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.testDBConnection(DatabaseUtilities.java:2876)

2012-07-26 18:57:47.634 THREAD 23 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.initDataSource(DatabaseUtilities.java:2856)

2012-07-26 18:57:47.634 THREAD 23 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.initDataSource(DatabaseUtilities.java:2686)

2012-07-26 18:57:47.634 THREAD 23 SEVERE:  at com.sygate.scm.server.upgrade.Upgrade.doUpgrade(Upgrade.java:302)

2012-07-26 18:57:47.634 THREAD 23 SEVERE:  at com.sygate.scm.server.upgrade.ui.UpgradeTask.go(UpgradeTask.java:94)

2012-07-26 18:57:47.634 THREAD 23 SEVERE:  at com.sygate.scm.server.upgrade.ui.UpgradeProgressPanel$2.construct(UpgradeProgressPanel.java:131)

2012-07-26 18:57:47.634 THREAD 23 SEVERE:  at com.sygate.scm.util.SwingWorker$2.run(SwingWorker.java:145)

2012-07-26 18:57:47.634 THREAD 23 SEVERE:  at java.lang.Thread.run(Thread.java:662)

2012-07-26 18:57:47.634 THREAD 23 INFO: UpgradeDBUtil: testDBConnection: Exception - Can't connect to database.

2012-07-26 18:57:49.899 THREAD 23 INFO: isUserDBOwner: Couldn't verify sem5 user is db_owner.

2012-07-26 18:57:49.899 THREAD 23 SEVERE: java.sql.SQLException: Login failed for user ''. The user is not associated with a trusted SQL Server connection.

2012-07-26 18:57:49.899 THREAD 23 SEVERE:  at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)

2012-07-26 18:57:49.899 THREAD 23 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)

2012-07-26 18:57:49.899 THREAD 23 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)

2012-07-26 18:57:49.899 THREAD 23 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.login(TdsCore.java:610)

2012-07-26 18:57:49.899 THREAD 23 SEVERE:  at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:345)

2012-07-26 18:57:49.899 THREAD 23 SEVERE:  at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)

2012-07-26 18:57:49.899 THREAD 23 SEVERE:  at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:184)

2012-07-26 18:57:49.899 THREAD 23 SEVERE:  at java.sql.DriverManager.getConnection(DriverManager.java:582)

2012-07-26 18:57:49.899 THREAD 23 SEVERE:  at java.sql.DriverManager.getConnection(DriverManager.java:185)

2012-07-26 18:57:49.899 THREAD 23 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDatabaseConnection(DatabaseUtilities.java:742)

2012-07-26 18:57:49.899 THREAD 23 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.isUserDBOwner(DatabaseUtilities.java:2466)

2012-07-26 18:57:49.899 THREAD 23 SEVERE:  at com.sygate.scm.server.upgrade.UpgradeDBUtil.isUserDBOwner(UpgradeDBUtil.java:679)

2012-07-26 18:57:49.899 THREAD 23 SEVERE:  at com.sygate.scm.server.upgrade.Upgrade.grantSEMUserPrivilege(Upgrade.java:2487)

2012-07-26 18:57:49.899 THREAD 23 SEVERE:  at com.sygate.scm.server.upgrade.Upgrade.doUpgrade(Upgrade.java:385)

2012-07-26 18:57:49.899 THREAD 23 SEVERE:  at com.sygate.scm.server.upgrade.ui.UpgradeTask.go(UpgradeTask.java:94)

2012-07-26 18:57:49.899 THREAD 23 SEVERE:  at com.sygate.scm.server.upgrade.ui.UpgradeProgressPanel$2.construct(UpgradeProgressPanel.java:131)

2012-07-26 18:57:49.899 THREAD 23 SEVERE:  at com.sygate.scm.util.SwingWorker$2.run(SwingWorker.java:145)

2012-07-26 18:57:49.899 THREAD 23 SEVERE:  at java.lang.Thread.run(Thread.java:662)

2012-07-26 18:57:49.899 THREAD 23 INFO: grantSEMUserPrivilege isDBowner false

2012-07-26 18:57:49.915 THREAD 23 INFO: retrieveUserForWinAuth: Couldn't retrieve sem5 user. 

2012-07-26 18:57:49.915 THREAD 23 SEVERE: java.sql.SQLException: Login failed for user ''. The user is not associated with a trusted SQL Server connection.

2012-07-26 18:57:49.915 THREAD 23 SEVERE:  at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)

2012-07-26 18:57:49.915 THREAD 23 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)

2012-07-26 18:57:49.915 THREAD 23 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)

2012-07-26 18:57:49.915 THREAD 23 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.login(TdsCore.java:610)

2012-07-26 18:57:49.915 THREAD 23 SEVERE:  at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:345)

2012-07-26 18:57:49.915 THREAD 23 SEVERE:  at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)

2012-07-26 18:57:49.915 THREAD 23 SEVERE:  at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:184)

2012-07-26 18:57:49.915 THREAD 23 SEVERE:  at java.sql.DriverManager.getConnection(DriverManager.java:582)

2012-07-26 18:57:49.915 THREAD 23 SEVERE:  at java.sql.DriverManager.getConnection(DriverManager.java:185)

2012-07-26 18:57:49.915 THREAD 23 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDatabaseConnection(DatabaseUtilities.java:742)

2012-07-26 18:57:49.915 THREAD 23 SEVERE:  at com.sygate.scm.server.upgrade.UpgradeDBUtil.retrieveUserForWinAuth(UpgradeDBUtil.java:389)

2012-07-26 18:57:49.915 THREAD 23 SEVERE:  at com.sygate.scm.server.upgrade.Upgrade.grantSEMUserPrivilege(Upgrade.java:2498)

2012-07-26 18:57:49.915 THREAD 23 SEVERE:  at com.sygate.scm.server.upgrade.Upgrade.doUpgrade(Upgrade.java:385)

2012-07-26 18:57:49.915 THREAD 23 SEVERE:  at com.sygate.scm.server.upgrade.ui.UpgradeTask.go(UpgradeTask.java:94)

2012-07-26 18:57:49.915 THREAD 23 SEVERE:  at com.sygate.scm.server.upgrade.ui.UpgradeProgressPanel$2.construct(UpgradeProgressPanel.java:131)

2012-07-26 18:57:49.915 THREAD 23 SEVERE:  at com.sygate.scm.util.SwingWorker$2.run(SwingWorker.java:145)

2012-07-26 18:57:49.915 THREAD 23 SEVERE:  at java.lang.Thread.run(Thread.java:662)

2012-07-26 18:57:49.915 THREAD 23 INFO: grantUserDBOwner: adminUrl : jdbc:jtds:sqlserver://SQL-DBServer:1433/sem5;preparesql=2;;domain=MyCompanyDomain, dbaUser : service-endpoint, semUserName : 

2012-07-26 18:57:50.009 THREAD 23 INFO: grantUserDBOwner: Couldn't grant user  as db_owner. 

2012-07-26 18:57:50.009 THREAD 23 SEVERE: java.sql.SQLException: User or role '' does not exist in this database.

2012-07-26 18:57:50.009 THREAD 23 SEVERE:  at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)

2012-07-26 18:57:50.009 THREAD 23 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)

2012-07-26 18:57:50.009 THREAD 23 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)

2012-07-26 18:57:50.009 THREAD 23 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:632)

2012-07-26 18:57:50.009 THREAD 23 SEVERE:  at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:584)

2012-07-26 18:57:50.009 THREAD 23 SEVERE:  at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:546)

2012-07-26 18:57:50.009 THREAD 23 SEVERE:  at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.execute(JtdsPreparedStatement.java:561)

2012-07-26 18:57:50.009 THREAD 23 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.grantUserDBOwner(DatabaseUtilities.java:2518)

2012-07-26 18:57:50.009 THREAD 23 SEVERE:  at com.sygate.scm.server.upgrade.UpgradeDBUtil.grantUserDBOwner(UpgradeDBUtil.java:416)

2012-07-26 18:57:50.009 THREAD 23 SEVERE:  at com.sygate.scm.server.upgrade.Upgrade.grantSEMUserPrivilege(Upgrade.java:2504)

2012-07-26 18:57:50.009 THREAD 23 SEVERE:  at com.sygate.scm.server.upgrade.Upgrade.doUpgrade(Upgrade.java:385)

2012-07-26 18:57:50.009 THREAD 23 SEVERE:  at com.sygate.scm.server.upgrade.ui.UpgradeTask.go(UpgradeTask.java:94)

2012-07-26 18:57:50.009 THREAD 23 SEVERE:  at com.sygate.scm.server.upgrade.ui.UpgradeProgressPanel$2.construct(UpgradeProgressPanel.java:131)

2012-07-26 18:57:50.009 THREAD 23 SEVERE:  at com.sygate.scm.util.SwingWorker$2.run(SwingWorker.java:145)

2012-07-26 18:57:50.009 THREAD 23 SEVERE:  at java.lang.Thread.run(Thread.java:662)

2012-07-26 18:57:50.009 THREAD 23 INFO: doUpgrade: Failed to grant the sem user privilege.

2012-07-26 18:57:50.009 THREAD 23 SEVERE: java.lang.Throwable: Cannot grant the sem user privilege.

2012-07-26 18:57:50.009 THREAD 23 SEVERE:  at com.sygate.scm.server.upgrade.Upgrade.doUpgrade(Upgrade.java:390)

2012-07-26 18:57:50.009 THREAD 23 SEVERE:  at com.sygate.scm.server.upgrade.ui.UpgradeTask.go(UpgradeTask.java:94)

2012-07-26 18:57:50.009 THREAD 23 SEVERE:  at com.sygate.scm.server.upgrade.ui.UpgradeProgressPanel$2.construct(UpgradeProgressPanel.java:131)

2012-07-26 18:57:50.009 THREAD 23 SEVERE:  at com.sygate.scm.util.SwingWorker$2.run(SwingWorker.java:145)

2012-07-26 18:57:50.009 THREAD 23 SEVERE:  at java.lang.Thread.run(Thread.java:662)

2012-07-26 18:57:50.024 THREAD 23 SEVERE: Upgrade.doUpgrade java.lang.Throwable: Cannot grant the sem user privilege.

2012-07-26 18:58:03.102 THREAD 16 INFO: UpgradeFinalPanel >> saveStage > Launching log file...
 

Dushan Gomez
IT Manager
VCP 4 and 5 | MCITP Exchange Server | MCTS SharePoint Server | MCP Windows XP

 

Mithun Sanghavi
Symantec Employee
Accredited
26
Jul
2012
Votes
+1

Upon checking your Logs

Hello,

Upon checking your logs we found the following - 

2012-07-26 18:57:47.634 THREAD 23 SEVERE: java.sql.SQLException: Login failed for user ''. The user is not associated with a trusted SQL Server connection.

.........

.............

2012-07-26 18:57:47.634 THREAD 23 INFO: UpgradeDBUtil: testDBConnection: Exception - Can't connect to database.

2012-07-26 18:57:49.899 THREAD 23 INFO: isUserDBOwner: Couldn't verify sem5 user is db_owner.

2012-07-26 18:57:49.899 THREAD 23 SEVERE: java.sql.SQLException: Login failed for user ''. The user is not associated with a trusted SQL Server connection.

 

Check the Articles provided below: 

"Failed to connect to the database." error when attempting to install Symantec Endpoint Protection Manager 11.x (SEPM) to a Microsoft SQL backend using Windows Authentication.

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

"Login failed for user 'username'. The user is not associated with a trusted SQL Server connection" in install_log.err while installing Symantec Endpoint Protection Manager (SEPM) on Microsoft SQL 2005 

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

About SQL Server database authentication modes http://www.symantec.com/docs/HOWTO55332

About SQL Server configuration settings http://www.symantec.com/docs/HOWTO55330

Hope that helps!!

Mithun Sanghavi
Symantec Technical Support Engineer, SEP
MIM | MCSA | MCTS | STS | ITIL v3

Twitter: @mithun_sanghavi

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.<&a

Dushan Gomez
26
Jul
2012
Votes
+1

Hi Mithun, For this

Hi Mithun,

For this article: http://www.symantec.com/business/support/index?page=content&id=TECH122555

As per the current RSoP.msc the result is "No Minimum" and the SQL server has already using both mixed and SQL auth.

Dushan Gomez
IT Manager
VCP 4 and 5 | MCITP Exchange Server | MCTS SharePoint Server | MCP Windows XP

 

Dushan Gomez
26
Jul
2012
Votes
+1

sa username is disabled in my SQL Server for security purpose

Hi Mithun,

I'm upgrading SEPM into v12.1 RU1 not a clean install of SEPM v11.0.6005 ?

Do I need to enable the sa SQL username and know password (SQL Server 2005 SP4). as per this article: http://www.symantec.com/business/support/index?page=content&id=TECH90870

Dushan Gomez
IT Manager
VCP 4 and 5 | MCITP Exchange Server | MCTS SharePoint Server | MCP Windows XP

 

Mithun Sanghavi
Symantec Employee
Accredited
26
Jul
2012
Votes
+1

Yes.

Hello,

Yes. We require sa level user account to make the necessary modifications to the database for the migration.  There is no workaround.  Note that this data is not stored by the SEPM, and is only used for one-time authentication.

Mithun Sanghavi
Symantec Technical Support Engineer, SEP
MIM | MCSA | MCTS | STS | ITIL v3

Twitter: @mithun_sanghavi

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.<&a

Dushan Gomez
26
Jul
2012
Votes
+1

Ah ok, I have enable it

Ah ok, I have enable it because I just knew it that sa is disabled after I upgrade with SQL 2005 SP4 with the latest CU. But i haven't restart the service yet due to this is production server.

Dushan Gomez
IT Manager
VCP 4 and 5 | MCITP Exchange Server | MCTS SharePoint Server | MCP Windows XP

 

Brian81
Trusted Advisor
Certified
26
Jul
2012
Votes
+1

Can you login to the SQL DB

Can you login to the SQL DB with that account?

SEP Knowledge Base

Endpoint SWAT

Dushan Gomez
26
Jul
2012
Votes
+1

yes

Yes Brian,

I can login using the sem5 SQL user ccount to the SQL Server with the SEM5 database, I can even execute this SQL code but without any result:

SELECT computer_name, 
       Dateadd(s, CONVERT(BIGINT, [time_stamp]) / 1000, '01-01-1970 00:00:00') 
       AS 
       [Time Stamp], 
       Cast((CASE WHEN ip_addr1 < 0 THEN 0xFFFFFFFF + ip_addr1 ELSE ip_addr1 END 
       / 256 
       / 256 / 256) & 0xFF AS VARCHAR) 
       + '.' + Cast((CASE WHEN ip_addr1 < 0 THEN 0xFFFFFFFF + ip_addr1 ELSE 
       ip_addr1 
       END / 256 / 256) & 0xFF AS VARCHAR) 
       + '.' + Cast((CASE WHEN ip_addr1 < 0 THEN 0xFFFFFFFF + ip_addr1 ELSE 
       ip_addr1 
       END / 256) & 0xFF AS VARCHAR) + '.' 
       + Cast( CASE WHEN ip_addr1 < 0 THEN 0xFFFFFFFF + ip_addr1 ELSE ip_addr1 
       END & 
       0xFF AS VARCHAR) 
       AS LOCAL_IP_ADDRESS 
FROM   sem_computer 
WHERE  computer_name IN (SELECT computer_name 
                         FROM   sem_computer 
                         GROUP  BY computer_name 
                         HAVING ( Count(computer_name) > 1 )) 

Dushan Gomez
IT Manager
VCP 4 and 5 | MCITP Exchange Server | MCTS SharePoint Server | MCP Windows XP

 

SAMI ALAMMARI
Partner
Accredited
26
Sep
2012
Votes
+5

hi you must delelte user sem5

hi

you must delelte user sem5 and then create new sem5 login

To delelte user sem5 :

open the sm5 database and choose security , users , locate and

delete the sem5 user

To create new sem5 user :

From the top of the hierarchly , open security , logins
Right Click Logins and choose New Login
Login Name : sem5
Enter password

On the left choose User Mapping and place a check next to sem5
In database role membership for : sem5 , place a check next to

dbowner(publice should already be check) and then click ok
Connect the SEPM to database by " repointing server to a new SQL

server

BALFAKIH COMPUTERS
 
alammri@balfakih.com
Partner
27
Sep
2012
Votes
+2

hi all : The user is not

hi all :

The user is not associated with a trusted SQL Server connection"

may be user problem if can deleted it and create a new user may be solved problem

i am happans same but when moving sql database from server A to server B , then reconfigured server B to pointing to SQL Server an error occureed , so that i am created new user sem5 then login

Ashish-Sharma
Accredited
27
Sep
2012
Votes
+1
SOLUTION

HI, User issue has been 

HI,

User issue has been  resolved kindly check user last thread

https://www-secure.symantec.com/connect/forums/how-come-i-got-duplicated-sep-client-my-sepm-database

https://www-secure.symantec.com/connect/forums/wrong-sep-client-installed-64-bit-server

Thanks In Advance

Ashish Sharma

SEPM Knowledgebase Documents  

 

Dushan Gomez
14
Oct
2012
Votes
0

yes thank you for the reply

yes thank you for the reply back Ashish !

Dushan Gomez
IT Manager
VCP 4 and 5 | MCITP Exchange Server | MCTS SharePoint Server | MCP Windows XP