Endpoint Protection

 View Only
Back to discussions
Expand all | Collapse all

SEPM Embedded DB not starting hangs in "Starting"

  • 1.  SEPM Embedded DB not starting hangs in "Starting"

    Posted Oct 30, 2014 06:17 AM

    hi all

     

    i am using win2012 R2 with SEP 12.1.4b  and the server was running fine for a week now this morning the SEPM Embedded DB is hanging on "Starting" state even after a rebbot please help



  • 2.  RE: SEPM Embedded DB not starting hangs in "Starting"

    Posted Oct 30, 2014 06:30 AM
    Enabled advanced debugging for the SEPM and post the scm-server.log here for review


  • 3.  RE: SEPM Embedded DB not starting hangs in "Starting"

    Posted Oct 30, 2014 06:30 AM

    Does any activity done in SEPM server ?

    Could you please post the entire scm-server-0.log and catalina.out files?

    SEPM server login hung, no error code, cannot update Virus Definitions.

    Article:TECH157761 | Created: 2011-04-10 | Updated: 2011-09-06 | Article URL http://www.symantec.com/docs/TECH157761


  • 4.  RE: SEPM Embedded DB not starting hangs in "Starting"

    Posted Oct 30, 2014 06:34 AM

    can you check the size of sem5.log ?

    its under C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db

    its its too large then follow this document and more importantly make sure you have enough diskspace on C drive

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



  • 5.  RE: SEPM Embedded DB not starting hangs in "Starting"

    Posted Oct 30, 2014 07:00 AM

    hi all

    where do i find scm-server-0.log and catalina.out files



  • 6.  RE: SEPM Embedded DB not starting hangs in "Starting"

    Posted Oct 30, 2014 07:03 AM

    hi james

     

    i am unable to rename the sem5.log

    it say it in use, i think because of the embedded DB is hanging in starting



  • 7.  RE: SEPM Embedded DB not starting hangs in "Starting"

    Posted Oct 30, 2014 07:12 AM

    you will find the log under

    C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs

    whats th size of sem5.log? do you have any backup?

    if yes then go to services.msc

    find the embedded db service

    make it to disabled. click apply , click OK

    open the task manager, kill the dbsrv9.exe or dbrsrv12.exe ( based on the version)

    go back to services.msc check if you can start that service.



  • 8.  RE: SEPM Embedded DB not starting hangs in "Starting"

    Posted Oct 30, 2014 07:49 AM

    See here:

    How to debug the Symantec Endpoint Protection Manager



  • 9.  RE: SEPM Embedded DB not starting hangs in "Starting"

    Posted Oct 30, 2014 08:17 AM

    hi james

     

    thanks.

    the se5.log file is 9MB

    \

    2014-10-30 13:23:55.678 THREAD 12 SEVERE: ================== Server Environment ===================
    2014-10-30 13:23:55.678 THREAD 12 SEVERE: os.name = Windows NT (unknown)
    2014-10-30 13:23:55.678 THREAD 12 SEVERE: os.version = 6.3
    2014-10-30 13:23:55.678 THREAD 12 SEVERE: os.arch = x64
    2014-10-30 13:23:55.678 THREAD 12 SEVERE: java.version = 1.7.0_51
    2014-10-30 13:23:55.692 THREAD 12 SEVERE: java.vendor = Oracle Corporation
    2014-10-30 13:23:55.692 THREAD 12 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
    2014-10-30 13:23:55.692 THREAD 12 SEVERE: java.vm.version = 24.51-b03
    2014-10-30 13:23:55.692 THREAD 12 SEVERE: java.home = D:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\jre
    2014-10-30 13:23:55.692 THREAD 12 SEVERE: catalina.home = D:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat
    2014-10-30 13:23:55.692 THREAD 12 SEVERE: java.user = null
    2014-10-30 13:23:55.692 THREAD 12 SEVERE: user.language = en
    2014-10-30 13:23:55.692 THREAD 12 SEVERE: user.country = US
    2014-10-30 13:23:55.692 THREAD 12 SEVERE: scm.server.version = 12.1.4104.4130
    2014-10-30 13:25:09.576 THREAD 12 SEVERE:
    org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory ([Sybase][JDBC Driver][SQL Anywhere]Database server not found)
     at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1549)
     at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1388)
     at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044)
     at com.sygate.scm.server.db.util.DatabaseUtilities.getDataSourceDBConnection(DatabaseUtilities.java:402)
     at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:286)
     at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:271)
     at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:261)
     at com.sygate.scm.server.db.util.DatabaseUtilities.getDBConnection(DatabaseUtilities.java:2499)
     at com.sygate.scm.server.db.util.DatabaseUtilities.testConnection(DatabaseUtilities.java:2456)
     at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:131)
     at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1279)
     at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1192)
     at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1087)
     at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5210)
     at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5493)
     at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
     at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
     at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
     at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:632)
     at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:670)
     at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1839)
     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
     at java.util.concurrent.FutureTask.run(FutureTask.java:262)
     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
     at java.lang.Thread.run(Thread.java:744)
    Caused by: java.sql.SQLException: [Sybase][JDBC Driver][SQL Anywhere]Database server not found
     at sybase.jdbc4.sqlanywhere.IDriver.makeODBCConnection(Native Method)
     at sybase.jdbc4.sqlanywhere.IDriver.connect(IDriver.java:772)
     at org.apache.tomcat.dbcp.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38)
     at org.apache.tomcat.dbcp.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582)
     at org.apache.tomcat.dbcp.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:1556)
     at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1545)
     ... 25 more
    2014-10-30 13:25:09.613 THREAD 12 SEVERE:  in: com.sygate.scm.server.servlet.StartupServlet
    com.sygate.scm.server.util.ScmServerError: Failed to connect to database after tried 20 times, please start the database!
     at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:132)
     at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1279)
     at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1192)
     at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1087)
     at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5210)
     at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5493)
     at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
     at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
     at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
     at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:632)
     at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:670)
     at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1839)
     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
     at java.util.concurrent.FutureTask.run(FutureTask.java:262)
     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
     at java.lang.Thread.run(Thread.java:744)
    2014-10-30 13:25:09.654 THREAD 12 SEVERE: DomainId: null
    SiteId: null
    ServerId: 098016290A7A161200DCF3A3F2ACC784
    SystemEventId: 1281
    EventDesc: Unexpected server error.
    MessageId: 1
    ErrorCode: 268500992
    com.sygate.scm.server.util.ScmServerError: Failed to connect to database after tried 20 times, please start the database!
     at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:132)
     at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1279)
     at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1192)
     at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1087)
     at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5210)
     at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5493)
     at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
     at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
     at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
     at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:632)
     at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:670)
     at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1839)
     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
     at java.util.concurrent.FutureTask.run(FutureTask.java:262)
     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
     at java.lang.Thread.run(Thread.java:744)
    com.sygate.scm.server.util.ServerException: Unexpected server error.
     at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:406)
     at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:371)
     at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:367)
     at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:363)
     at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:314)
     at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1279)
     at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1192)
     at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1087)
     at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5210)
     at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5493)
     at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
     at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
     at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
     at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:632)
     at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:670)
     at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1839)
     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
     at java.util.concurrent.FutureTask.run(FutureTask.java:262)
     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
     at java.lang.Thread.run(Thread.java:744)
    Caused by: com.sygate.scm.server.util.ScmServerError: Failed to connect to database after tried 20 times, please start the database!
     at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:132)
     ... 16 more
    2014-10-30 13:25:12.715 THREAD 12 SEVERE: SEM: Connect to database failed
    java.sql.SQLException: SEM: Connect to database failed
     at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:339)
     at com.sygate.scm.server.util.logging.DbLogHandler.publish(DbLogHandler.java:58)
     at java.util.logging.Logger.log(Logger.java:610)
     at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:408)
     at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:371)
     at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:367)
     at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:363)
     at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:314)
     at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1279)
     at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1192)
     at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1087)
     at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5210)
     at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5493)
     at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
     at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
     at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
     at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:632)
     at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:670)
     at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1839)
     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
     at java.util.concurrent.FutureTask.run(FutureTask.java:262)
     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
     at java.lang.Thread.run(Thread.java:744)
    Caused by: java.lang.NullPointerException
     at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:290)
     ... 23 more
     



  • 10.  RE: SEPM Embedded DB not starting hangs in "Starting"

    Posted Oct 30, 2014 12:55 PM

    Its saying that it was not able to create a connection which is correct coz DB service is not started. 

    were you able to stop the db service after killing the exe?

    why dont you try running the management server configuration wizard once.

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



  • 11.  RE: SEPM Embedded DB not starting hangs in "Starting"
    Best Answer

    Posted Oct 30, 2014 12:59 PM

    Caused by: java.sql.SQLException: [Sybase][JDBC Driver][SQL Anywhere]Database server not found
    at sybase.jdbc4.sqlanywhere.IDriver.makeODBCConnection(Native Method)
    at sybase.jdbc4.sqlanywhere.IDriver.connect(IDriver.java:772)

    ErrorCode: 268500992
    com.sygate.scm.server.util.ScmServerError: Failed to connect to database after tried 20 times, please start the database!

     

    Try this

    Solution

     

    1) Stop the Symantec Endpoint Protection Manager and Symantec Embedded Database services.
    2) Rename or delete the current sem5.log
    3) Click Start > Run and type CMD then click OK
    4) In the Command Prompt type:
    For 32-bit: CD C:\Program Files\Symantec\Symantec Endpoint Protection Manager\ASA\win32\
    For 64-bit: CD C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\ASA\win32\
    5) Press Enter. This will change directories to the folder containing dbsrv11.exe.
    6) To force the recreation of sem5.log, type:
    For 32-bit: dbsrv11 -f "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db" (There is a space after -f and "C:\...)
    For 64-bit: dbsrv11 -f "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\db\sem5.db" (There is a space after -f and "C:\...)
    7) Press Enter
    8) Click Start > Run and type services.msc then click OK
    9) Start the Symantec Endpoint Protection Manager and Symantec Embedded Database services



  • 12.  RE: SEPM Embedded DB not starting hangs in "Starting"

    Posted Oct 30, 2014 01:29 PM

    I've always found the err.log and out.log files quite handy when troubleshooting problems with the Embedded DB.  They can be found in the below folder (same as where the DB files themselves are kept):

    C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db

    If the DB won't actually start, then this is the place to look first, as all the other logs are just going to say "Cannot connect to DB" :)



  • 13.  RE: SEPM Embedded DB not starting hangs in "Starting"

    Posted Oct 31, 2014 03:41 AM

    thanks james for all your help theabove process work.

    thanks also to the all the above guys as well

    highly appreciated.