Endpoint Protection

 View Only
Expand all | Collapse all

Could not connect database fail when Upgrading from 14.3 MP1 to 14.3 RU1

  • 1.  Could not connect database fail when Upgrading from 14.3 MP1 to 14.3 RU1

    Posted Jan 15, 2021 07:25 AM
    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


  • 2.  RE: Could not connect database fail when Upgrading from 14.3 MP1 to 14.3 RU1

    Posted Jan 15, 2021 07:31 AM
    just ran upgrade.bat on sep install\bin folder, got this:

    2021-01-15 07:29:13.895 THREAD 1 SEVERE: java.lang.NoClassDefFoundError: org/apache/commons/lang3/StringUtils
    2021-01-15 07:29:13.896 THREAD 1 SEVERE: at com.sygate.scm.server.db.util.MSJDBCDriver.initializeJDBCParameters(MSJDBCDriver.java:136)
    2021-01-15 07:29:13.896 THREAD 1 SEVERE: at com.sygate.scm.server.db.util.JDBCDriver.getInstance(JDBCDriver.java:89)
    2021-01-15 07:29:13.896 THREAD 1 SEVERE: at com.sygate.scm.server.db.util.DatabaseUtilities.initDataSource(DatabaseUtilities.java:3706)
    2021-01-15 07:29:13.896 THREAD 1 SEVERE: at com.sygate.scm.server.db.util.DatabaseUtilities.initDataSource(DatabaseUtilities.java:3688)
    2021-01-15 07:29:13.896 THREAD 1 SEVERE: at com.sygate.scm.server.db.util.DatabaseUtilities.initDataSource(DatabaseUtilities.java:3674)
    2021-01-15 07:29:13.896 THREAD 1 SEVERE: at com.sygate.scm.server.upgrade.ui.Main.<init>(Main.java:365)
    2021-01-15 07:29:13.896 THREAD 1 SEVERE: at com.sygate.scm.server.upgrade.ui.Main.main(Main.java:1142)
    2021-01-15 07:29:13.898 THREAD 1 SEVERE: Caused by: java.lang.ClassNotFoundException: org.apache.commons.lang3.StringUtils
    2021-01-15 07:29:13.898 THREAD 1 SEVERE: at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581)
    2021-01-15 07:29:13.898 THREAD 1 SEVERE: at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
    2021-01-15 07:29:13.898 THREAD 1 SEVERE: at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
    2021-01-15 07:29:13.898 THREAD 1 SEVERE: ... 7 more

    its so weird behavior


  • 3.  RE: Could not connect database fail when Upgrading from 14.3 MP1 to 14.3 RU1

    Posted Jan 15, 2021 07:46 AM
    SQL version: Microsoft SQL Server 2016 (SP2-GDR) (KB4583460) - 13.0.5103.6 (X64) Nov 1 2020 00:13:28 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows Server 2016 Datacenter 10.0 <X64> (Build 14393: ) (Hypervisor)


  • 4.  RE: Could not connect database fail when Upgrading from 14.3 MP1 to 14.3 RU1

    Posted Jan 15, 2021 08:18 AM
    So if I try run upgrade wizard again, it seems stuck and interesting I see the dabtase goes to single user mode:







  • 5.  RE: Could not connect database fail when Upgrading from 14.3 MP1 to 14.3 RU1

    Broadcom Employee
    Posted Jan 15, 2021 10:41 AM
    What is the case number?


    This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.





  • 6.  RE: Could not connect database fail when Upgrading from 14.3 MP1 to 14.3 RU1

    Posted Jan 15, 2021 10:42 AM
    Hi John,

    Case:

    32483441




  • 7.  RE: Could not connect database fail when Upgrading from 14.3 MP1 to 14.3 RU1

    Broadcom Employee
    Posted Jan 15, 2021 10:44 AM

    Can you please run Symdiag on this system so we can take a look at all of the logs?  Then upload to the case.

    How to collect full support logs for Support with the SymDiag utility



    ------------------------------
    John Owens
    Strategic Support Engineer | Symantec Enterprise Division (SED)
    Symantec
    United States
    ------------------------------



  • 8.  RE: Could not connect database fail when Upgrading from 14.3 MP1 to 14.3 RU1

    Posted Jan 15, 2021 10:47 AM
    John, I should have mentioned, second tech the reached me an hour ago, asked me to restore the SEPM VM snapshot, which I did and told me to wait a new tech webex sessioin run the the upgrade again.

    I made couple follow us, because the last tech get shift endded, so I am waiting receive webex of a new tech.

    Let me know if you would like to get connect to watch it. I am just waiting this to try again,

    In case persist same problem, i can run the symdiag for sure.

    thanks


  • 9.  RE: Could not connect database fail when Upgrading from 14.3 MP1 to 14.3 RU1

    Posted Jan 15, 2021 04:38 PM
    John, have u idea how to avoid this on Setup side:

    Note: I am able to access database using same credentials via management studio, i needed to follow this:https://blog.sqlauthority.com/2008/11/04/sql-server-fix-error-4064-cannot-open-user-default-database-login-failed-login-failed-for-user/

    thanks



  • 10.  RE: Could not connect database fail when Upgrading from 14.3 MP1 to 14.3 RU1

    Posted Jan 15, 2021 05:04 PM
    never mind it was related to this, could get solved

    SQL SERVER - Fix : Error: 4064 - Cannot open user default database. Login failed. Login failed for user - SQL Authority with Pinal Dave
    SQL Authority with Pinal Dave remove preview
    SQL SERVER - Fix : Error: 4064 - Cannot open user default database. Login failed. Login failed for user - SQL Authority with Pinal Dave
    I have received following question nearly 10 times in last week though emails. Many users have received following error while connecting to the database. This error happens when database is dropped for which is default for some of the database user. When user try to login and their default database is dropped following error shows up.
    View this on SQL Authority with Pinal Dave >


    thnaks


  • 11.  RE: Could not connect database fail when Upgrading from 14.3 MP1 to 14.3 RU1

    Posted Jan 15, 2021 07:33 PM
    I chose to totally uninstall SEPM with clean wipe, set snapshot back, reinstall it again with recovery key and bkp.

    Its second try, it keeps stuck on 1% during several hours

    2021-01-15 16:54:02.421 THREAD 60 INFO: SemServiceManager> getServiceStatus>> Retrieve status for service semlaunchsrv
    2021-01-15 16:54:02.470 THREAD 60 SEVERE: SemServiceManager> getServiceStatus>> Error code from sc query: 1060
    2021-01-15 16:54:02.471 THREAD 60 INFO: SemServiceManager> waitForServiceTermination>> Service is stopped.
    2021-01-15 16:54:02.471 THREAD 60 INFO: SemServiceManager> getServiceStatus>> Retrieve status for service SepBridgeSrv
    2021-01-15 16:54:02.519 THREAD 60 SEVERE: SemServiceManager> getServiceStatus>> Error code from sc query: 1060
    2021-01-15 16:54:02.519 THREAD 60 INFO: SemServiceManager> getServiceStatus>> Retrieve status for service SepBridgeUploaderSrv
    2021-01-15 16:54:02.587 THREAD 60 SEVERE: SemServiceManager> getServiceStatus>> Error code from sc query: 1060
    2021-01-15 16:54:02.589 THREAD 60 SEVERE: ServerUtil> addSepmHostToTrustedInternetZone>> Unable to add registry key:SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\EscDomains\na1prsavw2734v
    2021-01-15 16:54:02.589 THREAD 60 INFO: getDatabaseConnectionWithNTLMv2Retry, jdbcURL: jdbc:sqlserver://NA1PRSDBW2477V.global.publicisgroupe.net:1620;integratedSecurity=false;encrypt=true;trustServerCertificate=true, user: dmzkwsep2db_RO
    2021-01-15 16:54:02.606 THREAD 60 WARNING: DbUtil>>isSQLServerFilestreamEnabled...
    2021-01-15 16:54:02.606 THREAD 60 WARNING: DbUtil>>getSQLServerRunningFilestreamLevel...
    2021-01-15 16:54:02.609 THREAD 60 WARNING: DbUtil>>getSQLServerRunningFilestreamLevel, runningValue: 0
    2021-01-15 16:54:02.609 THREAD 60 WARNING: DbUtil>>isSQLServerFilestreamEnabled, further check if if it was configured from SQL Server Configuration Management
    2021-01-15 16:54:02.609 THREAD 60 WARNING: DbUtil>>enableSQLServerFilestreamAccessLevel>>Enable SQLServer Filestream access level...
    2021-01-15 16:54:02.621 THREAD 60 WARNING: DbUtil>>enableSQLServerFilestreamAccessLevel>>Enabled SQLServer Filestream access level succesfully!
    2021-01-15 16:54:02.621 THREAD 60 WARNING: DbUtil>>getSQLServerRunningFilestreamLevel...
    2021-01-15 16:54:02.621 THREAD 60 WARNING: DbUtil>>getSQLServerRunningFilestreamLevel, runningValue: 0
    2021-01-15 16:54:02.622 THREAD 60 WARNING: DbUtil>>isSQLServerFilestreamEnabled done, enable status and level high enough: false
    2021-01-15 16:54:06.081 THREAD 60 INFO: getDatabaseConnectionWithNTLMv2Retry, jdbcURL: jdbc:sqlserver://NA1PRSDBW2477V.global.publicisgroupe.net:1620;databaseName=dmzkwsep2;integratedSecurity=false;encrypt=true;trustServerCertificate=true, user: dmzkwsep2db
    2021-01-15 16:54:06.099 THREAD 60 INFO: DbUtil >> setDBtoReadSnapshort...
    2021-01-15 16:54:06.099 THREAD 60 INFO: Begin setting DB isolation READ_COMMITTED_SNAPSHOT...


    I just don't know what to do more with this and support seems not have idea what to do. I will upload the symdiag

    I am feeling so frutrating that a process that used to be simple is now so painful and we are not assisted



  • 12.  RE: Could not connect database fail when Upgrading from 14.3 MP1 to 14.3 RU1

    Posted Jan 17, 2021 02:16 PM
    So, i installed back MP1 without problem. So I tried regular RU1 upgrade process again and same problem, stucks on this:




  • 13.  RE: Could not connect database fail when Upgrading from 14.3 MP1 to 14.3 RU1

    Broadcom Employee
    Posted Jan 18, 2021 10:07 AM
    Can you post the upgrade-0.log?

    ------------------------------
    John Owens
    Strategic Support Engineer | Symantec Enterprise Division (SED)
    Symantec
    United States
    ------------------------------



  • 14.  RE: Could not connect database fail when Upgrading from 14.3 MP1 to 14.3 RU1

    Posted Jan 18, 2021 10:10 AM
    John, I was about to re-post here. I found a workround by my self, i ran following on SQL

    ALTER DATABASE TestDB SET READ_COMMITTED_SNAPSHOT ON 

    Since setup seems to be stuck on that piece. So once done, and retryuing it, I could get it concluded 100%

    Hopefully you can give this feedback to Dev team or something


  • 15.  RE: Could not connect database fail when Upgrading from 14.3 MP1 to 14.3 RU1

    Posted Jan 18, 2021 10:18 AM
    Edited by Maver May 15, 2021 10:32 AM
    My RU1 upgrade fails @ 1% DB upgrade: https://community.broadcom.com/symantecenterprise/communities/community-home/digestviewer/viewthread?MessageKey=864e8bea-77d2-4a87-86c2-ae84e4c225ae&CommunityKey=1ecf5f55-9545-44d6-b0f4-4e4a7f5f5e68&tab=digestviewer#bm864e8bea-77d2-4a87-86c2-ae84e4c225ae

    So i restored my VM snapshot of SEP Mgr and everything seems to work except i get an error on logging into SEPM Console and the 1st three sections are blank.​

    ------------------------------
    ------------------------------



  • 16.  RE: Could not connect database fail when Upgrading from 14.3 MP1 to 14.3 RU1

    Broadcom Employee
    Posted Jan 18, 2021 10:21 AM
    Hi Maver,

    I would open a new thread for this issue.  You might check Reporting.log for the issue.

    Thanks!







  • 17.  RE: Could not connect database fail when Upgrading from 14.3 MP1 to 14.3 RU1

    Posted Jan 18, 2021 10:28 AM
    Hi John,

    I have had Case#32438314 opened for a while starting with failed RU1 upgrade.

    Thanks

    ------------------------------
    Maverick Technologies
    ------------------------------



  • 18.  RE: Could not connect database fail when Upgrading from 14.3 MP1 to 14.3 RU1

    Broadcom Employee
    Posted Jan 19, 2021 01:56 PM

    14.3 RU1 b3385 English SEPM refresh is now available on the Software Download Portal.

    Relevant documentation is now updated.

    Released versions: https://knowledge.broadcom.com/external/article/154575

    Fix Notes: https://knowledge.broadcom.com/external/article/204064/



    ------------------------------
    John Owens
    Strategic Support Engineer | Symantec Enterprise Division (SED)
    Symantec
    United States
    ------------------------------



  • 19.  RE: Could not connect database fail when Upgrading from 14.3 MP1 to 14.3 RU1

    Posted Jan 19, 2021 02:59 PM
    Thanks John.

    Should be already available like below:

    ?


  • 20.  RE: Could not connect database fail when Upgrading from 14.3 MP1 to 14.3 RU1

    Broadcom Employee
    Posted Jan 19, 2021 03:00 PM
    Click on Endpoint Protection link. You will see the upload date as of today. That is correct.

    ------------------------------
    John Owens
    Strategic Support Engineer | Symantec Enterprise Division (SED)
    Symantec
    United States
    ------------------------------



  • 21.  RE: Could not connect database fail when Upgrading from 14.3 MP1 to 14.3 RU1

    Posted Jan 19, 2021 03:02 PM
    Oh course, downloading now. thanks


  • 22.  RE: Could not connect database fail when Upgrading from 14.3 MP1 to 14.3 RU1

    Posted Jan 19, 2021 03:51 PM
    Hi @John Owens in this new 14.3 RU1 refresh build, all the issues which we were seeing in the earlier 14.3 RU1 is fixed and is now safe to upgrade to  14.3 RU1 refresh build?

    Appreciate your feedback on this. Thanks​

    ------------------------------
    Symantec Enthusiast
    ------------------------------



  • 23.  RE: Could not connect database fail when Upgrading from 14.3 MP1 to 14.3 RU1

    Broadcom Employee
    Posted Jan 19, 2021 03:59 PM

    This refresh resolves the following 2 issues:

    Additional fixes for 14.3.3385.1000

    SEPM upgrade to 14.3 RU1 encounters an error if a repair installation is performed

    Fix ID: ESCRT-5679

    Symptoms: SEPM upgrade to 14.3 RU1 is interrupted due to missing cryptoj.jar if a repair installation is performed.

    Solution: Corrected an issue during repair installations that could prevent a specific JAR file from being placed in its proper location.

    SEPM upgrade to 14.3 RU1 encounters a SQL Exception if database mirroring is enabled

    Fix ID: ESCRT-5685

    Symptoms: SEPM upgrade to 14.3 RU1 is unable to proceed if database mirroring is enabled. The following error is observed: "The operation cannot be performed on database "sem5" because it is involved in a database mirroring session or an availability group."

    Solution: Corrected an issue that impacted support for database mirroring SQL Server configurations.





    ------------------------------
    John Owens
    Strategic Support Engineer | Symantec Enterprise Division (SED)
    Symantec
    United States
    ------------------------------



  • 24.  RE: Could not connect database fail when Upgrading from 14.3 MP1 to 14.3 RU1

    Posted Jan 20, 2021 08:42 AM
    I ran the RU1 release on my DEV env. First server was fast and smooth. Second one, faced some db connection issues, I am using domain svc account for db authentication. I did rdp the server itself with svc account, ran the repair again, it worked. However, now SEPM services is getting stoped. The logs says:

    2021-01-20 14:35:49.067 THREAD 1 SEVERE: ServerUtil >> SEPM runs on AWS? false
    2021-01-20 14:35:49.192 THREAD 1 SEVERE: StartupServlet> verifySchemaVersion>> Database Schema Version = 14.3.1.1000, Server Schema Version = 14.3.1.1000
    2021-01-20 14:35:49.239 THREAD 1 SEVERE: StartupServlet> verifyDatabaseReleaseFlagServerVersion>> Release Version flag or server version does not match!
    2021-01-20 14:35:49.239 THREAD 1 SEVERE: Server version or release flag does not match.
    2021-01-20 14:35:49.286 THREAD 1 SEVERE: in: com.sygate.scm.server.servlet.StartupServlet
    com.sygate.scm.server.util.ScmServerError: Server version or release flag does not match.
    at com.sygate.scm.server.servlet.StartupServlet.verifyDatabaseReleaseFlagServerVersion(StartupServlet.java:863)
    at com.sygate.scm.server.servlet.StartupServlet.registerServer(StartupServlet.java:375)
    at com.sygate.scm.server.servlet.StartupServlet.startServer(StartupServlet.java:659)
    at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:203)
    at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1134)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1089)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:983)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4871)
    at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5180)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:717)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:690)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:705)
    at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:631)
    at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1831)
    at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
    at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
    at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
    at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118)
    at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:526)
    at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:425)
    at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1576)
    at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:309)
    at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123)
    at org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:423)
    at org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:366)
    at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:936)
    at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:841)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
    at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1384)
    at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1374)
    at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
    at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
    at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:140)
    at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:909)
    at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:262)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
    at org.apache.catalina.core.StandardService.startInternal(StandardService.java:421)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
    at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:930)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
    at org.apache.catalina.startup.Catalina.start(Catalina.java:633)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.base/java.lang.reflect.Method.invoke(Method.java:566)
    at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:343)
    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:474)
    2021-01-20 14:35:49.333 THREAD 1 SEVERE: StartupServlet> init>> Error occurred. SEPM Service shot down.

    and

    2021/01/20 14:35:43:895 : main : Initiating new JVMProcess on RMI[8100] -- Params[[sepm, 8100, 49742699]]
    2021/01/20 14:35:44:629 : RMI TCP Connection(1)-127.0.0.1 : [com.creamtec.ajaxswing.ClientAgentImpl] Initialization complete, instances in JVM = 1
    2021/01/20 14:35:55:302 : Thread-0 : [com.creamtec.ajaxswing.JVMProcess$1] Health check failed, exiting

    If anyone have an ideia.

    thanks



  • 25.  RE: Could not connect database fail when Upgrading from 14.3 MP1 to 14.3 RU1

    Posted Jan 20, 2021 02:19 PM
    Have an ideia how can workaround it? I will have to try disaster recovery to set it again. How I can grab latest clean wipe. Regular for download on Symantec still on first RU1 version.





  • 26.  RE: Could not connect database fail when Upgrading from 14.3 MP1 to 14.3 RU1

    Broadcom Employee
    Posted Jan 20, 2021 03:32 PM

    This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.





  • 27.  RE: Could not connect database fail when Upgrading from 14.3 MP1 to 14.3 RU1

    Posted Jan 20, 2021 12:28 AM
    Hi John,

    We had the same issue as mentioned in # 12. Finally we have successfully upgraded to 14.3.3385.1000. I've noticed upgrade wizard gave the following pop-up to enable SQL FILESTREAM. I don't recall I've seen this pop-up prior to this upgrade. Is this something new in this version?

    We had to break our DB clustering in order to complete the upgrade - is this addressed in build 14.3.3385.1000?   


    Thank you for your help.
    Moin