Hello everyone,
I have started upgrading my SEPM infra in Prod to RU1, due some upgrade weird behaviors which I was able to solve and conclude the upgrade for 4 servers in my infra, I got stuck in one SEPM server in DMZ. Facing following error msgs even after multiple retries:
2021-01-14 22:58:54.083 THREAD 1 WARNING: SQLExpressDbHelper >> isInMigrationProcess, checking file: D:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\bin\migrationSummary.txt
2021-01-14 22:58:54.090 THREAD 1 INFO: DatabaseUtilities> testDBConnection>> Testing DB connection using 'DefaultDatabaseConnection' method. Parameters used (needDateFormat: false, isRetryUntilDBUp: false, defaultConnectionMaxRetry: 20)
2021-01-14 22:58:54.095 THREAD 1 INFO: initializing DBConnectionProxy
2021-01-14 22:58:54.095 THREAD 1 INFO: loading impersonate library
2021-01-14 22:58:54.108 THREAD 1 INFO: successfully loaded impersonate library
2021-01-14 22:58:54.508 THREAD 1 INFO: Could not connect to the database, wait for 1 second to retry... caller: getDataSourceDBConnection
2021-01-14 22:58:55.547 THREAD 1 INFO: Could not connect to the database, wait for 1 second to retry... caller: getDataSourceDBConnection
2021-01-14 22:58:56.580 THREAD 1 INFO: Could not connect to the database, wait for 1 second to retry... caller: getDataSourceDBConnection
2021-01-14 22:58:57.603 THREAD 1 INFO: Could not connect to the database, wait for 1 second to retry... caller: getDataSourceDBConnection
2021-01-14 22:58:58.627 THREAD 1 INFO: Could not connect to the database, wait for 1 second to retry... caller: getDataSourceDBConnection
2021-01-14 22:58:59.653 THREAD 1 INFO: Could not connect to the database, wait for 1 second to retry... caller: getDataSourceDBConnection
2021-01-14 22:59:00.676 THREAD 1 INFO: Could not connect to the database, wait for 1 second to retry... caller: getDataSourceDBConnection
2021-01-14 22:59:01.699 THREAD 1 INFO: Could not connect to the database, wait for 1 second to retry... caller: getDataSourceDBConnection
2021-01-14 22:59:02.724 THREAD 1 INFO: Could not connect to the database, wait for 1 second to retry... caller: getDataSourceDBConnection
2021-01-14 22:59:03.767 THREAD 1 INFO: Could not connect to the database, wait for 1 second to retry... caller: getDataSourceDBConnection
2021-01-14 22:59:04.796 THREAD 1 INFO: Could not connect to the database, wait for 1 second to retry... caller: getDataSourceDBConnection
2021-01-14 22:59:05.822 THREAD 1 INFO: Could not connect to the database, wait for 1 second to retry... caller: getDataSourceDBConnection
2021-01-14 22:59:06.860 THREAD 1 INFO: Could not connect to the database, wait for 1 second to retry... caller: getDataSourceDBConnection
2021-01-14 22:59:07.878 THREAD 1 INFO: Could not connect to the database, wait for 1 second to retry... caller: getDataSourceDBConnection
2021-01-14 22:59:08.901 THREAD 1 INFO: Could not connect to the database, wait for 1 second to retry... caller: getDataSourceDBConnection
2021-01-14 22:59:09.924 THREAD 1 INFO: Could not connect to the database, wait for 1 second to retry... caller: getDataSourceDBConnection
2021-01-14 22:59:10.952 THREAD 1 INFO: Could not connect to the database, wait for 1 second to retry... caller: getDataSourceDBConnection
2021-01-14 22:59:11.972 THREAD 1 INFO: Could not connect to the database, wait for 1 second to retry... caller: getDataSourceDBConnection
2021-01-14 22:59:12.992 THREAD 1 INFO: Could not connect to the database, wait for 1 second to retry... caller: getDataSourceDBConnection
2021-01-14 22:59:14.049 THREAD 1 SEVERE: com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user 'dmzkwsep2db'. ClientConnectionId:0ff2ae27-2868-4b2d-a7c9-d08f789aa99e
2021-01-14 22:59:14.049 THREAD 1 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:262)
2021-01-14 22:59:14.049 THREAD 1 SEVERE: at com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(tdsparser.java:283)
2021-01-14 22:59:14.049 THREAD 1 SEVERE: at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:129)
2021-01-14 22:59:14.050 THREAD 1 SEVERE: at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:37)
2021-01-14 22:59:14.050 THREAD 1 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerConnection.sendLogon(SQLServerConnection.java:5233)
2021-01-14 22:59:14.050 THREAD 1 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerConnection.logon(SQLServerConnection.java:3988)
2021-01-14 22:59:14.050 THREAD 1 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerConnection$LogonCommand.doExecute(SQLServerConnection.java:3932)
2021-01-14 22:59:14.050 THREAD 1 SEVERE: at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7375)
2021-01-14 22:59:14.050 THREAD 1 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:3206)
2021-01-14 22:59:14.050 THREAD 1 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:2713)
2021-01-14 22:59:14.050 THREAD 1 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:2362)
2021-01-14 22:59:14.050 THREAD 1 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectInternal(SQLServerConnection.java:2213)
2021-01-14 22:59:14.050 THREAD 1 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:1276)
2021-01-14 22:59:14.050 THREAD 1 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerDataSource.getConnectionInternal(SQLServerDataSource.java:1222)
2021-01-14 22:59:14.051 THREAD 1 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerDataSource.getConnection(SQLServerDataSource.java:85)
2021-01-14 22:59:14.051 THREAD 1 SEVERE: at com.sygate.scm.server.db.util.DBConnectionProxy.getConnectionBasedOnDataSource(DBConnectionProxy.java:264)
2021-01-14 22:59:14.051 THREAD 1 SEVERE: at com.sygate.scm.server.db.util.DBConnectionProxy.getConnectionFromDataSource(DBConnectionProxy.java:332)
2021-01-14 22:59:14.051 THREAD 1 SEVERE: at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:470)
2021-01-14 22:59:14.051 THREAD 1 SEVERE: at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:448)
2021-01-14 22:59:14.051 THREAD 1 SEVERE: at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:417)
2021-01-14 22:59:14.051 THREAD 1 SEVERE: at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:405)
2021-01-14 22:59:14.051 THREAD 1 SEVERE: at com.sygate.scm.server.db.util.DatabaseUtilities.testDBConnection(DatabaseUtilities.java:3745)
2021-01-14 22:59:14.051 THREAD 1 SEVERE: at com.sygate.scm.server.upgrade.ui.Main.<init>(Main.java:407)
2021-01-14 22:59:14.051 THREAD 1 SEVERE: at com.sygate.scm.server.upgrade.ui.Main.main(Main.java:1142)
2021-01-14 22:59:14.051 THREAD 1 INFO: DatabaseUtilities> testDBConnection>> Exception - Can't connect to database.
2021-01-14 22:59:14.052 THREAD 1 WARNING: SQLExpressDbHelper >> isInMigrationProcess, checking file: D:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\bin\migrationSummary.txt
The app account is a sysadmin db account on my sep SQL database. I have not problems to access it with management studio, no credentials problem.
Interesting DB team mentioned that , upgrade process seems to be trying change the database option Allow_snapshot_isolation to on for the database dmzkwsep2 as a result it was making database dmzkwsep2 in single user mode.
I put a case with Broadcom but as usual the first leval techs send no-sense docs and get it so slow to escalate it.
This my most important SEPM now due clients are working from home.
Let me know if anyone has any comment that could help me.
Thanks all
Cesar Americo