Endpoint Protection

 View Only
Expand all | Collapse all

any problems with upgrade to 14.3 RU1 ?

  • 1.  any problems with upgrade to 14.3 RU1 ?

    Posted Dec 10, 2020 07:30 AM
    hy
    there are some problems in action with the upgrade to 14.3 RU1 release ?
    i'm using the embedded DB


  • 2.  RE: any problems with upgrade to 14.3 RU1 ?

    Posted Dec 10, 2020 08:39 AM

    Hi Andrea

    We were on embedded DB and SEPM upgrade to 14.3 RU1 went as usual, no problems. As there is db conversion to MS SQL Express setup lasts somewhat longer, but for me no issues.

    First thing I've noticed afterwards, LiveUpdate folder is gone (\Program Files (x86)\Symantec\LiveUpdate). On couple of occasions support asked me to manually run LUALL.EXE so I had an icon on the desktop. LUALL.EXE is now gone (or at least is not on this location any longer).

    SEP client on the server which hosts SEPM got corrupted. So much that it couldn't be uninstalled, but I had to use CleanWipe (very carefully).

    Nothing else to report.




  • 3.  RE: any problems with upgrade to 14.3 RU1 ?

    Posted Dec 10, 2020 09:07 AM
    hi a.devecerski
    thanks for you reply
    how did you resolve the liveupdate problem ?


  • 4.  RE: any problems with upgrade to 14.3 RU1 ?

    Posted Dec 10, 2020 09:44 AM
    Edited by Aleksandar Devecerski Dec 10, 2020 09:44 AM

    Didn't have to. Tested it immediately, it's working just fine.

    Just have to find a way to trigger the update not using SEPM console (or by manually downloading the definitions).




  • 5.  RE: any problems with upgrade to 14.3 RU1 ?

    Posted Dec 10, 2020 09:12 AM
      |   view attached
    The upgrade went alright, they added a few warnings and a prompt for FILESTREAM to be on in SQL now, which in my dev environment wasn't on and will cause the DB upgrade part to fail if its not.  Not a huge deal, you just go in and enable it and then re-launch the management server configuration wizard to finish the upgrade.

    Other warning was about TLS communication with SQL, its only a recommendation but here's the info on that: https://techdocs.broadcom.com/us/en/symantec-security-software/endpoint-security-and-management/endpoint-protection/all/upgrading-to-a-new-release-v14510472-d27e6/Configuring-encryption-communication-between-SEPM-and-SQL-Server.html.

    Recommend highly upgrading a dev environment before doing prod as the upgrade procedure is now slightly different with the new warnings and prompts.

    Only thing I've noticed so far, which maybe my environment, is the agent constantly reports an issue with "URL Reputation Protection is disabled. Click Fix" error the agent reports until someone clicks fix, a reboot does not resolve the issue.  So far I haven't seen it go away on its own either with a policy update which in my policy I do have URL Reputation disabled which is desired so wonder whats up with the warning.

    Going to submit a ticket about it as its concerning.


  • 6.  RE: any problems with upgrade to 14.3 RU1 ?

    Broadcom Employee
    Posted Dec 10, 2020 09:38 AM
    Hi Adam, There is a lock box next to the option to disable URL filtering. The lock box must be locked if you want URL REPUTATION to not display that error on clients. 






  • 7.  RE: any problems with upgrade to 14.3 RU1 ?

    Posted Dec 10, 2020 09:56 AM
    Yup that worked, wow didn't know if you locked it, the SEP client would then ignore it.  Good to know, also, for some reason I was confusing this with Network Traffic Redirection, this is something we'd probably want on anyways.  Thanks again John.


  • 8.  RE: any problems with upgrade to 14.3 RU1 ?

    Posted Dec 10, 2020 09:56 AM
    can you post a picture ?


  • 9.  RE: any problems with upgrade to 14.3 RU1 ?

    Posted Dec 10, 2020 09:59 AM
    I have uploaded a picture of what setting I changed to get that warning to go away, like I stated above, that IS something you'll want to seriously consider having turned on.



  • 10.  RE: any problems with upgrade to 14.3 RU1 ?

    Posted Dec 16, 2020 02:29 PM
    I recommend that the URL-filtering is OFF. First; we have expericenced that the URL-filter blocks traffic that should not have been blocked. I even verified that w Symantec tools, saying that the IP was ok. The blocking is not logged anywhere that I could find. Second; there's no central configuration option to allow certain URL's. The URL is blocked locally and no logging. Hence, I recommend that this setting is OFF. Please correct me if there's anyone out there who has more info to enlight this :-)

    ------------------------------
    DSB
    ------------------------------



  • 11.  RE: any problems with upgrade to 14.3 RU1 ?

    Broadcom Employee
    Posted Dec 16, 2020 02:32 PM

    You can use Trusted Web Domain for exclusions. This will work with URL Filtering.

    The logs can be found under IPS logs.



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



  • 12.  RE: any problems with upgrade to 14.3 RU1 ?

    Posted Dec 17, 2020 02:53 AM
    I don't agree that it should be on. It has blocked traffic that it shouldn't block, and there's no central configuration option to allow traffic. Symantec just blocks the URL, and it's not even logged anywhere that I can see. We have turned it off as well.

    ------------------------------
    DSB
    ------------------------------



  • 13.  RE: any problems with upgrade to 14.3 RU1 ?

    Posted Dec 14, 2020 11:47 AM
    " they added a few warnings and a prompt for FILESTREAM to be on in SQL now, which in my dev environment wasn't on and will cause the DB upgrade part to fail if its not.  Not a huge deal, you just go in and enable it and then re-launch the management server configuration wizard to finish the upgrade."


    What is it you went in an enabled?  Something in the server OS?  Or is this just following the SEPM upgrade steps essentially?


    ------------------------------
    rmo
    ------------------------------



  • 14.  RE: any problems with upgrade to 14.3 RU1 ?

    Posted Dec 15, 2020 02:22 PM
    Edited by Maver May 15, 2021 10:36 AM
    I can't get my DB upgraded. Immediately fails at 1%

    2020-12-15 13:13:41.326 THREAD 1 SEVERE: ================== Server Environment ===================
    2020-12-15 13:13:41.326 THREAD 1 SEVERE: os.name = Windows Server 2012
    2020-12-15 13:13:41.326 THREAD 1 SEVERE: os.version = 6.2
    2020-12-15 13:13:41.326 THREAD 1 SEVERE: os.arch = x64
    2020-12-15 13:13:41.326 THREAD 1 SEVERE: java.version = 11.0.7
    2020-12-15 13:13:41.326 THREAD 1 SEVERE: java.vendor = AdoptOpenJDK
    2020-12-15 13:13:41.326 THREAD 1 SEVERE: java.vm.name = OpenJDK 64-Bit Server VM
    2020-12-15 13:13:41.326 THREAD 1 SEVERE: java.vm.version = 11.0.7+10
    2020-12-15 13:13:41.326 THREAD 1 SEVERE: java.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\jre11
    2020-12-15 13:13:41.326 THREAD 1 SEVERE: catalina.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat
    2020-12-15 13:13:41.326 THREAD 1 SEVERE: java.user = null
    2020-12-15 13:13:41.326 THREAD 1 SEVERE: user.language = en
    2020-12-15 13:13:41.341 THREAD 1 SEVERE: user.country = US
    2020-12-15 13:13:41.341 THREAD 1 SEVERE: scm.server.version = 14.3.3384.1000
    2020-12-15 13:13:41.341 THREAD 1 INFO: Main> Main>> Checking upgrade arguments... Command-line argument is empty.
    2020-12-15 13:13:41.341 THREAD 1 INFO: Main> Main>> Server Home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat
    2020-12-15 13:13:41.357 THREAD 1 INFO: ServerXml>> verifyAndRetrieveROOTXml>> Verifying ROOT.xml...
    2020-12-15 13:13:41.388 THREAD 1 INFO: ServerXml>> verifyAndRetrieveXmlFile>> .xml file is valid, deleting backup file...
    2020-12-15 13:13:41.388 THREAD 1 INFO: ServerXml>> verifyAndRetrieveXmlFile>> .xml file is valid, deleting backup file...
    2020-12-15 13:13:41.404 THREAD 1 INFO: create a new RootXMLHandler
    2020-12-15 13:13:41.419 THREAD 1 INFO: readJdbcParameters >> jdbcURL: jdbc:sqlserver://SQL:1433;databaseName=sem5;encrypt=true;trustServerCertificate=true
    2020-12-15 13:13:41.419 THREAD 1 INFO: readJdbcParameters >> jdbcDriverClass: com.microsoft.sqlserver.jdbc.SQLServerDriver
    2020-12-15 13:13:41.451 THREAD 1 INFO: DatabaseUtilities> initDataSource>> jdbcDriverClass: com.microsoft.sqlserver.jdbc.SQLServerDriver
    2020-12-15 13:13:42.357 THREAD 1 INFO: verifyAndSetJre11FolderPermissions: Fisnished!
    2020-12-15 13:13:42.357 THREAD 1 INFO: applyAclsPreUpgrade: Finished!
    2020-12-15 13:13:42.373 THREAD 1 INFO: Main> Main>> Current DB schema version (14.3.1.1000), Testing DB connection... Current time = Tue Dec 15 13:13:42 CST 2020
    2020-12-15 13:13:42.388 THREAD 1 WARNING: SQLExpressDbHelper >> isInMigrationProcess, checking file: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\bin\migrationSummary.txt
    2020-12-15 13:13:42.388 THREAD 1 INFO: DatabaseUtilities> testDBConnection>> Testing DB connection using 'DefaultDatabaseConnection' method. Parameters used (needDateFormat: false, isRetryUntilDBUp: false, defaultConnectionMaxRetry: 20)
    2020-12-15 13:13:42.388 THREAD 1 INFO: initializing DBConnectionProxy
    2020-12-15 13:13:42.388 THREAD 1 INFO: loading impersonate library
    2020-12-15 13:13:42.388 THREAD 1 INFO: successfully loaded impersonate library
    2020-12-15 13:13:42.685 THREAD 1 INFO: Main> executePreLaunchSteps>> dbConnected: true, isEmbeddedDb: false
    2020-12-15 13:13:42.888 THREAD 1 INFO: Main> executePreLaunchSteps>> Config schema format is getting upgraded from (schema version from db): 14.3.0.0000
    2020-12-15 13:13:43.060 THREAD 1 INFO: Saving disaster recovery data to: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Server Private Key Backup\recovery_2020-12-15-13-13-43.zip
    2020-12-15 13:13:43.123 THREAD 1 INFO: Main> executePreLaunchSteps>> DbVersion: 14.3.0.0000 schemaVersionFromDB: 14.3.0.0000 isSpm51Mr7: false hasOtherOSAgents: false dbcompanySize: 1 dbConnected: true isTelemetryOptedInFromDB: true
    2020-12-15 13:13:43.123 THREAD 1 INFO: Main> checkUpgradeFeasibility>> Checking for upgrade feasibility, current schema version = 14.3.1.1000, schema version from db = 14.3.0.0000
    2020-12-15 13:13:43.123 THREAD 1 INFO: VersionToBeSupported: 14.3.0.0000
    2020-12-15 13:13:43.123 THREAD 1 INFO: SchemaVersion>> isSupported> versionToBeSupported '14.3.0.0000 is supported for this release
    2020-12-15 13:13:43.201 THREAD 1 INFO: SchemaVersion>> isSupported> isReleaseVersionFrom: true, isReleaseVersionTo: true
    2020-12-15 13:13:43.201 THREAD 1 INFO: SchemaVersion>> isSupported> isReleaseVersionFrom: true, isReleaseVersionTo: true
    2020-12-15 13:13:43.216 THREAD 1 INFO: Main> displayOnlineServerListIfAny>> Checking online servers. siteId = 0A906DBDAC1000600026BF4CD2DF71F7
    2020-12-15 13:13:43.232 THREAD 1 INFO: SYSOUT : Checking onlist status for server SEPM2
    2020-12-15 13:13:43.232 THREAD 1 INFO: SYSOUT : Not checking status. offline status detected
    2020-12-15 13:13:43.232 THREAD 1 INFO: SYSOUT : [name=SEPM2,id=469DDBE2AC10006001EB06C3FD0B7625] is offline
    2020-12-15 13:13:43.232 THREAD 1 INFO: Main> displayOnlineServerListIfAny>> Checking online servers. Exclude local server id = 469DDBE2AC10006001EB06C3FD0B7625
    2020-12-15 13:13:43.232 THREAD 1 INFO: Main> displayOnlineServerListIfAny>> Online servers = []
    2020-12-15 13:13:43.232 THREAD 1 INFO: Main> launchMainFrame>> isSpm51Mr7AndHasOtherOSAgents: false, isAutomated: false, dbServerVendor: MSSQLServer
    2020-12-15 13:13:43.404 THREAD 1 WARNING: SQLExpressDbHelper >> isInMigrationProcess, checking file: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\bin\migrationSummary.txt
    2020-12-15 13:13:43.404 THREAD 1 INFO: SEPM is upgraded from or later version (14.3.0.0000). no need to display User Credential panel
    2020-12-15 13:13:43.404 THREAD 1 INFO: Set DB administrator credential from root.xml
    2020-12-15 13:13:43.435 THREAD 1 INFO: DbUtil>>isDatabaseEmbeddedSQLExpress, result: false
    2020-12-15 13:13:43.435 THREAD 1 INFO: SQL server with SQL Auth mode. Display User Credential panel
    2020-12-15 13:13:43.451 THREAD 1 INFO: ServerConfigurationRemediator >> needChooseLaunchServicePort >> needChooseLaunchServicePort=false serverVersionPreUpgrade=14.3.558.0000
    2020-12-15 13:13:43.451 THREAD 1 INFO: MainFrame> MainFrame>> needToShowUpgradeServerPropPanel: false
    2020-12-15 13:13:43.607 THREAD 1 WARNING: SQLExpressDbHelper>>executePowshellCommand processing:
    args[0]: C:\Windows\system32\reg.exe
    args[1]: query
    args[2]: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunOnce
    args[3]: /v
    args[4]: Symantec Management Server Upgrade Wizard

    2020-12-15 13:13:43.638 THREAD 1 WARNING: SQLExpressDbHelper>>executePowshellCommand processing result: 1
    2020-12-15 13:13:43.638 THREAD 1 WARNING: DbUtil>>executePowshellCommand standard output:



    Error Output:
    ERROR: The system was unable to find the specified registry key or value.

    2020-12-15 13:13:45.388 THREAD 21 WARNING: SQLExpressDbHelper >> isInMigrationProcess, checking file: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\bin\migrationSummary.txt
    2020-12-15 13:13:45.388 THREAD 21 INFO: Skip using Cursors for MS JDBC to leverage Adaptive buffering
    2020-12-15 13:13:45.388 THREAD 21 INFO: getDatabaseConnectionWithNTLMv2Retry, jdbcURL: jdbc:sqlserver://SQL:1433;integratedSecurity=false;encrypt=true;trustServerCertificate=false, user: sem5
    2020-12-15 13:13:45.451 THREAD 21 SEVERE: exception retrieving connection
    2020-12-15 13:13:45.451 THREAD 21 SEVERE: exception retrieving connection
    2020-12-15 13:13:45.451 THREAD 21 INFO: SqlPropPanel > isServerCertTrusted() see exception
    2020-12-15 13:13:45.451 THREAD 21 SEVERE: com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target". ClientConnectionId:50b17313-6e8a-43c1-ab54-35dca71f3b06
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:3151)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1912)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:2708)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:2362)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectInternal(SQLServerConnection.java:2213)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:1276)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:861)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.sql/java.sql.DriverManager.getConnection(DriverManager.java:677)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.sql/java.sql.DriverManager.getConnection(DriverManager.java:228)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at com.sygate.scm.server.db.util.DBConnectionProxy.getConnectionFromDriverManager(DBConnectionProxy.java:414)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at com.sygate.scm.server.db.util.MSJDBCDriver.getConnection(MSJDBCDriver.java:182)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at com.sygate.scm.server.db.util.JDBCDriver.getDatabaseConnectionWithNTLMv2Retry(JDBCDriver.java:192)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at com.sygate.scm.server.db.util.DatabaseUtilities.getDatabaseConnectionWithNTLMv2Retry(DatabaseUtilities.java:617)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at com.sygate.scm.server.db.util.DatabaseUtilities.getDatabaseConnectionWithNTLMv2Retry(DatabaseUtilities.java:596)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at com.sygate.scm.server.db.util.DbUtil.isServerCertTrusted(DbUtil.java:3025)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at com.sygate.scm.server.db.util.DbUtil.checkTrustServerCert(DbUtil.java:2955)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at com.sygate.scm.server.db.util.DbUtil.checkTrustServerCert(DbUtil.java:2938)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at com.sygate.scm.server.upgrade.ui.WelcomePanel.saveStage(WelcomePanel.java:213)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at com.sygate.scm.server.upgrade.ui.MainFrame.nextBtnActionPerformed(MainFrame.java:344)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at com.sygate.scm.server.upgrade.ui.MainFrame$2.actionPerformed(MainFrame.java:261)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.desktop/javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1967)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.desktop/javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2308)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.desktop/javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:405)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.desktop/javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:262)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.desktop/javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:279)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.desktop/java.awt.Component.processMouseEvent(Component.java:6631)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.desktop/javax.swing.JComponent.processMouseEvent(JComponent.java:3342)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.desktop/java.awt.Component.processEvent(Component.java:6396)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.desktop/java.awt.Container.processEvent(Container.java:2263)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.desktop/java.awt.Component.dispatchEventImpl(Component.java:5007)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2321)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.desktop/java.awt.Component.dispatchEvent(Component.java:4839)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4918)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4547)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4488)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2307)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2772)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.desktop/java.awt.Component.dispatchEvent(Component.java:4839)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:772)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/java.security.AccessController.doPrivileged(Native Method)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:95)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:745)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:743)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/java.security.AccessController.doPrivileged(Native Method)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:742)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: Caused by: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:131)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:326)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:269)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:264)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/sun.security.ssl.CertificateMessage$T12CertificateConsumer.checkServerCerts(CertificateMessage.java:645)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/sun.security.ssl.CertificateMessage$T12CertificateConsumer.onCertificate(CertificateMessage.java:464)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/sun.security.ssl.CertificateMessage$T12CertificateConsumer.consume(CertificateMessage.java:360)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/sun.security.ssl.SSLHandshake.consume(SSLHandshake.java:392)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/sun.security.ssl.HandshakeContext.dispatch(HandshakeContext.java:444)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/sun.security.ssl.HandshakeContext.dispatch(HandshakeContext.java:422)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/sun.security.ssl.TransportContext.dispatch(TransportContext.java:183)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:164)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1144)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1055)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:395)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1820)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: ... 53 more
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:439)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:306)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/sun.security.validator.Validator.validate(Validator.java:264)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:313)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:233)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:110)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at com.microsoft.sqlserver.jdbc.TDSChannel$HostNameOverrideX509TrustManager.checkServerTrusted(IOBuffer.java:1498)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/sun.security.ssl.AbstractTrustManagerWrapper.checkServerTrusted(SSLContextImpl.java:1510)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/sun.security.ssl.CertificateMessage$T12CertificateConsumer.checkServerCerts(CertificateMessage.java:629)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: ... 64 more
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/sun.security.provider.certpath.SunCertPathBuilder.build(SunCertPathBuilder.java:141)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:126)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/java.security.cert.CertPathBuilder.build(CertPathBuilder.java:297)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: at java.base/sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:434)
    2020-12-15 13:13:45.466 THREAD 21 SEVERE: ... 72 more
    2020-12-15 13:13:45.466 THREAD 21 INFO: getDatabaseConnectionWithNTLMv2Retry, jdbcURL: jdbc:sqlserver://SQL:1433;integratedSecurity=false;encrypt=true;trustServerCertificate=false, user: sem5
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: exception retrieving connection
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: exception retrieving connection
    2020-12-15 13:13:45.529 THREAD 21 INFO: SqlPropPanel > isServerCertTrusted() see exception
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target". ClientConnectionId:e60e97fb-8ce9-4ee5-ab56-6e9b171e8096
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:3151)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1912)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:2708)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:2362)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectInternal(SQLServerConnection.java:2213)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:1276)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:861)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.sql/java.sql.DriverManager.getConnection(DriverManager.java:677)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.sql/java.sql.DriverManager.getConnection(DriverManager.java:228)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at com.sygate.scm.server.db.util.DBConnectionProxy.getConnectionFromDriverManager(DBConnectionProxy.java:414)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at com.sygate.scm.server.db.util.MSJDBCDriver.getConnection(MSJDBCDriver.java:182)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at com.sygate.scm.server.db.util.JDBCDriver.getDatabaseConnectionWithNTLMv2Retry(JDBCDriver.java:192)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at com.sygate.scm.server.db.util.DatabaseUtilities.getDatabaseConnectionWithNTLMv2Retry(DatabaseUtilities.java:617)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at com.sygate.scm.server.db.util.DatabaseUtilities.getDatabaseConnectionWithNTLMv2Retry(DatabaseUtilities.java:596)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at com.sygate.scm.server.db.util.DbUtil.isServerCertTrusted(DbUtil.java:3025)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at com.sygate.scm.server.db.util.DbUtil.checkTrustServerCert(DbUtil.java:2955)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at com.sygate.scm.server.db.util.DbUtil.checkTrustServerCert(DbUtil.java:2938)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at com.sygate.scm.server.upgrade.ui.WelcomePanel.saveStage(WelcomePanel.java:213)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at com.sygate.scm.server.upgrade.ui.MainFrame.nextBtnActionPerformed(MainFrame.java:344)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at com.sygate.scm.server.upgrade.ui.MainFrame$2.actionPerformed(MainFrame.java:261)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.desktop/javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1967)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.desktop/javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2308)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.desktop/javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:405)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.desktop/javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:262)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.desktop/javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:279)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.desktop/java.awt.Component.processMouseEvent(Component.java:6631)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.desktop/javax.swing.JComponent.processMouseEvent(JComponent.java:3342)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.desktop/java.awt.Component.processEvent(Component.java:6396)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.desktop/java.awt.Container.processEvent(Container.java:2263)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.desktop/java.awt.Component.dispatchEventImpl(Component.java:5007)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2321)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.desktop/java.awt.Component.dispatchEvent(Component.java:4839)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4918)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4547)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4488)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2307)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2772)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.desktop/java.awt.Component.dispatchEvent(Component.java:4839)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:772)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/java.security.AccessController.doPrivileged(Native Method)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:95)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:745)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:743)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/java.security.AccessController.doPrivileged(Native Method)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:742)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: Caused by: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:131)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:326)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:269)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:264)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/sun.security.ssl.CertificateMessage$T12CertificateConsumer.checkServerCerts(CertificateMessage.java:645)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/sun.security.ssl.CertificateMessage$T12CertificateConsumer.onCertificate(CertificateMessage.java:464)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/sun.security.ssl.CertificateMessage$T12CertificateConsumer.consume(CertificateMessage.java:360)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/sun.security.ssl.SSLHandshake.consume(SSLHandshake.java:392)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/sun.security.ssl.HandshakeContext.dispatch(HandshakeContext.java:444)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/sun.security.ssl.HandshakeContext.dispatch(HandshakeContext.java:422)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/sun.security.ssl.TransportContext.dispatch(TransportContext.java:183)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:164)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1144)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1055)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:395)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1820)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: ... 53 more
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:439)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:306)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/sun.security.validator.Validator.validate(Validator.java:264)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:313)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:233)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:110)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at com.microsoft.sqlserver.jdbc.TDSChannel$HostNameOverrideX509TrustManager.checkServerTrusted(IOBuffer.java:1498)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/sun.security.ssl.AbstractTrustManagerWrapper.checkServerTrusted(SSLContextImpl.java:1510)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/sun.security.ssl.CertificateMessage$T12CertificateConsumer.checkServerCerts(CertificateMessage.java:629)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: ... 64 more
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/sun.security.provider.certpath.SunCertPathBuilder.build(SunCertPathBuilder.java:141)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:126)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/java.security.cert.CertPathBuilder.build(CertPathBuilder.java:297)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: at java.base/sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:434)
    2020-12-15 13:13:45.529 THREAD 21 SEVERE: ... 72 more
    2020-12-15 13:14:00.466 THREAD 21 INFO: getDatabaseConnectionWithNTLMv2Retry, jdbcURL: jdbc:sqlserver://SQL:1433;databaseName=sem5;encrypt=true;trustServerCertificate=true, user: sa
    2020-12-15 13:14:00.498 THREAD 27 WARNING: Upgrade> doUpgrade>> Upgrade process started @ : 0
    2020-12-15 13:14:00.498 THREAD 27 INFO: Upgrade> doUpgrade>> Initializing upgrade steps...
    2020-12-15 13:14:00.498 THREAD 27 INFO: UpgradeStep >> checkUpgradeStatus.
    2020-12-15 13:14:00.498 THREAD 27 INFO: Upgrade> doUpgrade>> Initializing upgrade steps done!
    2020-12-15 13:14:00.498 THREAD 27 WARNING: SQLExpressDbHelper >> isInMigrationProcess, checking file: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\bin\migrationSummary.txt
    2020-12-15 13:14:00.513 THREAD 27 WARNING: Upgrade> doUpgrade>> Stopping SemSrv...
    2020-12-15 13:14:00.513 THREAD 27 INFO: SemServiceManager> getServiceStatus>> Retrieve status for service SepBridgeSrv
    2020-12-15 13:14:00.529 THREAD 27 SEVERE: SemServiceManager> getServiceStatus>> Error code from sc query: 1060
    2020-12-15 13:14:00.529 THREAD 27 INFO: SemServiceManager> getServiceStatus>> Retrieve status for service SepBridgeUploaderSrv
    2020-12-15 13:14:00.544 THREAD 27 SEVERE: SemServiceManager> getServiceStatus>> Error code from sc query: 1060
    2020-12-15 13:14:00.576 THREAD 27 INFO: The Symantec Endpoint Protection Manager API Service service is not started.More help is available by typing NET HELPMSG 3521.
    2020-12-15 13:14:00.576 THREAD 27 INFO: SemServiceManager> serviceControl>> Executed command - stop semapisrv, process return value = 2
    2020-12-15 13:14:00.576 THREAD 27 INFO: SemServiceManager> waitForServiceTermination>> Waiting for service termination: semapisrv
    2020-12-15 13:14:00.576 THREAD 27 INFO: SemServiceManager> getServiceStatus>> Retrieve status for service semapisrv
    2020-12-15 13:14:00.591 THREAD 27 INFO: SemServiceManager> getServiceStatus>> The status for semapisrv' service is 1
    2020-12-15 13:14:00.591 THREAD 27 INFO: SemServiceManager> waitForServiceTermination>> Service is stopped.
    2020-12-15 13:14:00.607 THREAD 27 INFO: The Symantec Endpoint Protection Manager service is not started.More help is available by typing NET HELPMSG 3521.
    2020-12-15 13:14:00.607 THREAD 27 INFO: SemServiceManager> serviceControl>> Executed command - stop semsrv, process return value = 2
    2020-12-15 13:14:00.607 THREAD 27 INFO: SemServiceManager> waitForServiceTermination>> Waiting for service termination: semsrv
    2020-12-15 13:14:00.607 THREAD 27 INFO: SemServiceManager> getServiceStatus>> Retrieve status for service semsrv
    2020-12-15 13:14:00.623 THREAD 27 INFO: SemServiceManager> getServiceStatus>> The status for semsrv' service is 1
    2020-12-15 13:14:00.623 THREAD 27 INFO: SemServiceManager> waitForServiceTermination>> Service is stopped.
    2020-12-15 13:14:00.638 THREAD 27 INFO: The Symantec Endpoint Protection Manager Webserver service is not started.More help is available by typing NET HELPMSG 3521.
    2020-12-15 13:14:00.638 THREAD 27 INFO: SemServiceManager> serviceControl>> Executed command - stop semwebsrv, process return value = 2
    2020-12-15 13:14:00.654 THREAD 27 INFO: The Symantec Endpoint Protection Launcher service is not started.More help is available by typing NET HELPMSG 3521.
    2020-12-15 13:14:00.654 THREAD 27 INFO: SemServiceManager> serviceControl>> Executed command - stop semlaunchsrv, process return value = 2
    2020-12-15 13:14:00.654 THREAD 27 INFO: SemServiceManager> waitForServiceTermination>> Waiting for service termination: semlaunchsrv
    2020-12-15 13:14:00.654 THREAD 27 INFO: SemServiceManager> getServiceStatus>> Retrieve status for service semlaunchsrv
    2020-12-15 13:14:00.669 THREAD 27 INFO: SemServiceManager> getServiceStatus>> The status for semlaunchsrv' service is 1
    2020-12-15 13:14:00.669 THREAD 27 INFO: SemServiceManager> waitForServiceTermination>> Service is stopped.
    2020-12-15 13:14:00.669 THREAD 27 INFO: SemServiceManager> getServiceStatus>> Retrieve status for service SepBridgeSrv
    2020-12-15 13:14:00.685 THREAD 27 SEVERE: SemServiceManager> getServiceStatus>> Error code from sc query: 1060
    2020-12-15 13:14:00.685 THREAD 27 INFO: SemServiceManager> getServiceStatus>> Retrieve status for service SepBridgeUploaderSrv
    2020-12-15 13:14:00.685 THREAD 27 SEVERE: SemServiceManager> getServiceStatus>> Error code from sc query: 1060
    2020-12-15 13:14:00.685 THREAD 27 WARNING: Upgrade> doUpgrade>> Stopping SemSrv done!
    2020-12-15 13:14:00.685 THREAD 27 INFO: Skip using Cursors for MS JDBC to leverage Adaptive buffering
    2020-12-15 13:14:00.701 THREAD 27 INFO: ServerXml> createBackupFile>> Is backup file created ? true
    2020-12-15 13:14:00.701 THREAD 27 INFO: ServerXml> backupServerROOTXmlFiles>> Is ROOT.xml.bak file created ? true
    2020-12-15 13:14:00.701 THREAD 27 INFO: ServerXml> createBackupFile>> Is backup file created ? true
    2020-12-15 13:14:00.701 THREAD 27 INFO: ServerXml> backupServerROOTXmlFiles>> Is Server.xml.bak file deleted ? true
    2020-12-15 13:14:00.701 THREAD 27 INFO: Skip using Cursors for MS JDBC to leverage Adaptive buffering
    2020-12-15 13:14:00.701 THREAD 27 INFO: DatabaseUtilities> testDBConnection>> Testing DB connection using 'DefaultDatabaseConnection' method. Parameters used (needDateFormat: false, isRetryUntilDBUp: false, defaultConnectionMaxRetry: 20)
    2020-12-15 13:14:00.732 THREAD 27 INFO: LicenseUtils> isLicenseInstallationValid>> sep.slf =true OD file=true
    2020-12-15 13:14:00.779 THREAD 27 INFO: UpgradeDBUtil> createODBC>> Creating ODBC... [dbServer: SQL, dbDomain: , dbUser: REPORTER_sem5sem5, dbPwd: ***, dbName: sem5, dbServerPort: 1433, dbVendor: MSSQLServer, SPMport: 8443, remotePort: 9090]
    2020-12-15 13:14:00.826 THREAD 27 INFO: UpgradeDBUtil> createODBC>> Creating ODBC done!
    2020-12-15 13:14:00.826 THREAD 27 INFO: Upgrade> grantSEMUserSQLDBOwnerPrivilege>> Granting 'sem5' 'db_owner' privilege...
    2020-12-15 13:14:00.826 THREAD 27 INFO: getDatabaseConnectionWithNTLMv2Retry, jdbcURL: jdbc:sqlserver://SQL:1433;databaseName=sem5;encrypt=true;trustServerCertificate=true, user: sem5
    2020-12-15 13:14:00.841 THREAD 27 INFO: Upgrade> grantSemUserSqlDbOwnerPrivilege>> Granting 'sem5' db_owner privilege done!
    2020-12-15 13:14:00.888 THREAD 27 INFO: Upgrade >> Begin upgrading DB isolation READ_COMMITTED_SNAPSHOT...
    2020-12-15 13:14:00.888 THREAD 27 INFO: DbUtil >> setDBtoReadSnapshort...
    2020-12-15 13:14:00.888 THREAD 27 INFO: Begin setting DB isolation READ_COMMITTED_SNAPSHOT...
    2020-12-15 13:14:00.998 THREAD 27 INFO: DbUtil >> setDBtoReadSnapshort, Finished setting DB isolation READ_COMMITTED_SNAPSHOT!
    2020-12-15 13:14:00.998 THREAD 27 INFO: Upgrade >> Finished upgrading DB isolation READ_COMMITTED_SNAPSHOT!
    2020-12-15 13:14:00.998 THREAD 27 INFO: UpgradeStep >> checkUpgradeStatus.
    2020-12-15 13:14:00.998 THREAD 27 INFO: UpgradeStep >> checkUpgradeStatus.
    2020-12-15 13:14:00.998 THREAD 27 INFO: Set the config manager cache threshold to 500!
    2020-12-15 13:14:01.044 THREAD 27 INFO: SchemaVersion>> isSupported> isReleaseVersionFrom: true, isReleaseVersionTo: true
    2020-12-15 13:14:01.044 THREAD 27 INFO: SchemaVersion>> isSupported> isReleaseVersionFrom: true, isReleaseVersionTo: true
    2020-12-15 13:14:01.044 THREAD 27 INFO: Upgrade> doUpgrade>> Config schema format is getting upgraded from 14.3.0.0000 to 14.3.1.1000
    2020-12-15 13:14:01.060 THREAD 27 INFO: Upgrade> setUnrestrictedMaxLogFileSize>> Max Log File Size from DB: 2097152
    2020-12-15 13:14:01.060 THREAD 27 INFO: Upgrade> setUnrestrictedMaxLogFileSize>> Max Log File Size is 2TB, No need to change the Max Trasaction Log Size to Unrestircted size.
    2020-12-15 13:14:01.076 THREAD 27 WARNING: Upgrade> doUpgrade>> Enable SQL Server Filestream before database schema upgrade...
    2020-12-15 13:14:01.076 THREAD 27 INFO: Failed to query Database Embedded Status, exec: Unexpected server error.
    2020-12-15 13:14:01.076 THREAD 27 INFO: DbUtil>>isDatabaseEmbeddedSQLExpress, result: false
    2020-12-15 13:14:01.076 THREAD 27 INFO: Skip using Cursors for MS JDBC to leverage Adaptive buffering
    2020-12-15 13:14:01.076 THREAD 27 INFO: DatabaseUtilities> testDBConnection>> Testing DB connection using 'DefaultDatabaseConnection' method. Parameters used (needDateFormat: false, isRetryUntilDBUp: false, defaultConnectionMaxRetry: 20)
    2020-12-15 13:14:01.091 THREAD 27 INFO: getDatabaseConnectionWithNTLMv2Retry, jdbcURL: jdbc:sqlserver://SQL:1433;databaseName=sem5;encrypt=true;trustServerCertificate=true, user: sa
    2020-12-15 13:14:01.091 THREAD 27 WARNING: DbUtil>>isSQLServerFilestreamEnabled...
    2020-12-15 13:14:01.091 THREAD 27 WARNING: DbUtil>>getSQLServerRunningFilestreamLevel...
    2020-12-15 13:14:01.091 THREAD 27 WARNING: DbUtil>>getSQLServerRunningFilestreamLevel, runningValue: 2
    2020-12-15 13:14:01.091 THREAD 27 WARNING: DbUtil>>isSQLServerFilestreamEnabled done, enable status and level high enough: true
    2020-12-15 13:14:01.091 THREAD 27 INFO: Skip using Cursors for MS JDBC to leverage Adaptive buffering
    2020-12-15 13:14:01.091 THREAD 27 INFO: DatabaseUtilities> testDBConnection>> Testing DB connection using 'DefaultDatabaseConnection' method. Parameters used (needDateFormat: false, isRetryUntilDBUp: false, defaultConnectionMaxRetry: 20)
    2020-12-15 13:14:01.107 THREAD 27 INFO: getDatabaseConnectionWithNTLMv2Retry, jdbcURL: jdbc:sqlserver://SQL:1433;databaseName=sem5;encrypt=true;trustServerCertificate=true, user: sa
    2020-12-15 13:14:01.107 THREAD 27 WARNING: DbUtil>>isSQLServerFilestreamEnabled...
    2020-12-15 13:14:01.107 THREAD 27 WARNING: DbUtil>>getSQLServerRunningFilestreamLevel...
    2020-12-15 13:14:01.107 THREAD 27 WARNING: DbUtil>>getSQLServerRunningFilestreamLevel, runningValue: 2
    2020-12-15 13:14:01.107 THREAD 27 WARNING: DbUtil>>isSQLServerFilestreamEnabled done, enable status and level high enough: true
    2020-12-15 13:14:01.107 THREAD 27 WARNING: DbUtil>>configSQLServerFilestreamFileGroup>>Config SQLServer Filestream file group...
    2020-12-15 13:14:01.123 THREAD 27 WARNING: Upgrade> updateTransactionLogFileSize>> Original log size is 2097152
    2020-12-15 13:14:01.123 THREAD 27 SEVERE: com.microsoft.sqlserver.jdbc.SQLServerException: ALTER DATABASE failed because FILESTREAM filegroups cannot be added to a database that has either the READ_COMMITTED_SNAPSHOT or the ALLOW_SNAPSHOT_ISOLATION option set to ON. To add FILESTREAM filegroups, you must set READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_ISOLATION to OFF.
    2020-12-15 13:14:01.123 THREAD 27 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:262)
    2020-12-15 13:14:01.123 THREAD 27 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1632)
    2020-12-15 13:14:01.123 THREAD 27 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(SQLServerStatement.java:872)
    2020-12-15 13:14:01.123 THREAD 27 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(SQLServerStatement.java:767)
    2020-12-15 13:14:01.123 THREAD 27 SEVERE: at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7375)
    2020-12-15 13:14:01.123 THREAD 27 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:3206)
    2020-12-15 13:14:01.123 THREAD 27 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:247)
    2020-12-15 13:14:01.123 THREAD 27 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:222)
    2020-12-15 13:14:01.123 THREAD 27 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(SQLServerStatement.java:743)
    2020-12-15 13:14:01.123 THREAD 27 SEVERE: at com.sygate.scm.server.db.util.DbUtil.configSQLServerFilestreamFileGroup(DbUtil.java:2176)
    2020-12-15 13:14:01.123 THREAD 27 SEVERE: at com.sygate.scm.server.upgrade.Upgrade.configSqlServerFilestream(Upgrade.java:4309)
    2020-12-15 13:14:01.123 THREAD 27 SEVERE: at com.sygate.scm.server.upgrade.Upgrade.doUpgrade(Upgrade.java:672)
    2020-12-15 13:14:01.123 THREAD 27 SEVERE: at com.sygate.scm.server.upgrade.ui.UpgradeTask.go(UpgradeTask.java:147)
    2020-12-15 13:14:01.123 THREAD 27 SEVERE: at com.sygate.scm.server.upgrade.ui.UpgradeProgressPanel$2.construct(UpgradeProgressPanel.java:248)
    2020-12-15 13:14:01.123 THREAD 27 SEVERE: at com.sygate.scm.util.SwingWorker$2.run(SwingWorker.java:151)
    2020-12-15 13:14:01.123 THREAD 27 SEVERE: at java.base/java.lang.Thread.run(Thread.java:834)
    2020-12-15 13:14:01.123 THREAD 27 SEVERE: Upgrade.doUpgrade com.microsoft.sqlserver.jdbc.SQLServerException: ALTER DATABASE failed because FILESTREAM filegroups cannot be added to a database that has either the READ_COMMITTED_SNAPSHOT or the ALLOW_SNAPSHOT_ISOLATION option set to ON. To add FILESTREAM filegroups, you must set READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_ISOLATION to OFF.
    2020-12-15 13:14:01.123 THREAD 27 INFO: Deleting file C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\conf\Catalina\localhost\ROOT.xml.bak
    2020-12-15 13:14:01.123 THREAD 27 INFO: ServerXml> deleteBackupFile>> Is backup file deleted ? true
    2020-12-15 13:14:01.123 THREAD 27 INFO: ServerXml> deleteServerROOTXmlBackupFiles>> Is ROOT.xml.bak file deleted ? true
    2020-12-15 13:14:01.123 THREAD 27 INFO: Deleting file C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\conf\server.xml.bak
    2020-12-15 13:14:01.123 THREAD 27 INFO: ServerXml> deleteBackupFile>> Is backup file deleted ? true
    2020-12-15 13:14:01.138 THREAD 27 INFO: ServerXml> deleteServerROOTXmlBackupFiles>> Is Server.xml.bak file deleted ? true
    2020-12-15 13:14:01.138 THREAD 27 WARNING: Upgrade> doUpgrade>> Upgrade process completed in (ms) : 640
    2020-12-15 13:14:01.169 THREAD 27 INFO: AuditUtil> auditEvent>> The Upgrading is executed by windows user: 
    2020-12-15 13:14:01.185 THREAD 21 INFO: MainFrame>> doInitFinalPanel> Upgrade.serviceInstallState = 0
    2020-12-15 13:14:03.232 THREAD 21 INFO: Upgrade> updateVSICorSVAClientExistsOrNotStatus>> Started. started@ 1608059643216ms
    2020-12-15 13:14:03.263 THREAD 21 INFO: checkQueryCount> run>> VSICCLIENT_COUNT: 0
    2020-12-15 13:14:03.263 THREAD 21 INFO: checkQueryCount> run>> SVA_COUNT: 0
    2020-12-15 13:14:03.263 THREAD 21 INFO: Upgrade> updateVSICorSVAClientExistsOrNotStatus>> Started. started@ 1608059643263ms
    2020-12-15 13:14:03.279 THREAD 21 INFO: checkQueryCount> run>> VSICCLIENT_COUNT: 0
    2020-12-15 13:14:03.279 THREAD 21 INFO: checkQueryCount> run>> SVA_COUNT: 0
    2020-12-15 13:14:04.373 THREAD 21 INFO: Utility>> runScmHelper: props#0, File=C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\bin\scmhelper_1608059644341.ini
    2020-12-15 13:14:04.373 THREAD 21 INFO: Utility>> runScmHelper: props#1, Command=SetRegistryForSymQual
    2020-12-15 13:14:04.373 THREAD 21 INFO: Utility>> runScmHelper: props#2, ErrorCode=0
    2020-12-15 13:14:04.373 THREAD 21 INFO: Utility>> runScmHelper: OK!
    2020-12-15 13:14:04.373 THREAD 21 INFO: UpgradeFinalPanel> saveStage>> Launching log file..




  • 15.  RE: any problems with upgrade to 14.3 RU1 ?

    Posted Dec 16, 2020 08:38 AM
    I opened a case due I am facing same issue and they seems to be working in some workaround for that. In addicion, I had a case since long time ( 32183496 ) about MacOS not reporting definitions to SEPM, totally related with their client since some 14.0 version, third time I opened a case and they close without solution. Can you believe I asked them DO NOT CLOSE it that time again, they just ignored me and closed it without solution. That support becames terribly unbelievable. Every time they close it i lost I historic and have to create a new one, where a level 1 tech start making same all non sense questions.

    For God what happened with this Company?


  • 16.  RE: any problems with upgrade to 14.3 RU1 ?

    Posted Dec 16, 2020 08:39 AM
    Btw this is the related article about this upgrade issue itself:

    https://knowledge.broadcom.com/external/article/204664/


  • 17.  RE: any problems with upgrade to 14.3 RU1 ?

    Posted Dec 16, 2020 09:40 AM
    Edited by Maver May 15, 2021 10:32 AM
    I saw that before the upgrade...those errors don't appear to be like mine which appear to be: ALTER DATABASE failed because FILESTREAM filegroups cannot be added to a database that has either the READ_COMMITTED_SNAPSHOT or the ALLOW_SNAPSHOT_ISOLATION option set to ON. To add FILESTREAM filegroups, you must set READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_ISOLATION to OFF.

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




  • 18.  RE: any problems with upgrade to 14.3 RU1 ?

    Posted Mar 15, 2021 11:07 AM
    Hi Mavor,
    Did you ever get any help with this error?  I am getting the same error on two SEPM's load balanced with an external SQL server.  Been through multiple support technicians that keep referring to the same KB's, and even tried the latest 14.3 RU1 MP1, but still getting the same error.

    ------------------------------
    Sr. Systems Administrator
    ICU Medical
    ------------------------------



  • 19.  RE: any problems with upgrade to 14.3 RU1 ?

    Posted Mar 15, 2021 05:17 PM
    I had to revert back to a snapshot of the SEPM VM running pre RU1. Guess i won't be upgrading to RU1/MP1 then. Hope they figure it out for you.


  • 20.  RE: any problems with upgrade to 14.3 RU1 ?

    Posted Dec 15, 2020 03:44 AM
    Edited by jinwai Dec 15, 2020 03:46 AM
    https://community.broadcom.com/symantecenterprise/communities/community-home/digestviewer/viewquestion?ContributedContentKey=2018a5d4-e6e1-4c02-9a56-ce391d961dd8&CommunityKey=1ecf5f55-9545-44d6-b0f4-4e4a7f5f5e68&tab=digestviewer

    Incompatible - Symantec SEP v14.3 RU1 (14.3.3384.1000) and Cisco AnyConnect v4.9.04053 in MacOS Big Sur

    Reported to Symantec.
    Anyone else also facing this issue?




  • 21.  RE: any problems with upgrade to 14.3 RU1 ?

    Posted Feb 04, 2021 03:19 PM
    I am having the same issue with the SEP Client reporting that the "URL Reputation Protection is disabled".  The feature is enabled in the IPS policy on the SEP Manager and when checking the SEP client settings locally, the box is checked for "Enable URL Reputation" under the Intrusion Prevention tab in the Network and Host Exploit Mitigation Settings area. The SEP client GUI shows a Big Red Error and the SEP client tray icon shows a Red Shield instead of a Green Dot. The only way to suppress the error is to uncheck "Enable URL Reputation" in the IPS policy on the SEP Manager AND click the Lock Icon beside "Enable URL Reputation". This issue first appeared when I upgraded to 14.3 RU1 (14.3.3384.1000) and I assumed it was a bug so I waited for the next release.  When 14.3 RU1 Refresh was released I hoped it would be fixed but the issue still exists in 14.3 RU1 Refresh (14.3.3385.1000). In my opinion this appears to be a bug that Broadcom needs to fix ASAP. I have opened a case for this issue and am waiting feedback. I also opened a case when 14.3 RU1 was released and the resolution was to Repair the SEP Client. That did resolve the issue but I had to repair approximately 10 SEP Clients and that is not an acceptable solution for large environments where there may be hundreds or thousands of SEP clients with the issue.


  • 22.  RE: any problems with upgrade to 14.3 RU1 ?

    Posted Feb 05, 2021 07:11 AM
    The SEP product is really getting worst with escalating licensing cost. I think the old developers had left. I am not sure how come the size limit on the online submission folder was removed with a 14.x release. Now I have domain controllers with no connection to the internet is running out of space. Another frustration is when a support call is logged no matter how much notes, screenshots and information I provide the support staff will not read any of those and start asking level 1 support questions.
    Anyways, this satire with SEP is over since moving to Crowdstrike in few months..
    After 20yrs with Symantec AV thanks to Broadcom for the plans to slowly killing it.



    Sent from handheld. Please ignore shortness & typos.

    DISCLAIMER: This email message, including any attachments, is intended for the individual or entity to whom it is addressed and may contain information that is confidential, privileged and/or exempt from disclosure under applicable law. If you have received this email in error you must not disclose or use the information in it. Please delete the email and any copies and notify the sender. Confidentiality or privilege are not waived or lost by reason of the mistaken delivery to you. Views expressed in this message are those of the individual sender, and are not necessarily the views of the Department of Communities and Justice. The Department accepts no liability for any loss or damage arising from the use of this email or attachments and recommends that the recipient check this email and any attached files for the presence of viruses.