Endpoint Protection

 View Only
Back to discussions
Expand all | Collapse all

Cannot start SEPM service, after moving DB to SQL standard. Get error: "The Java Virtual Machine has exited with a code of -1"

  • 1.  Cannot start SEPM service, after moving DB to SQL standard. Get error: "The Java Virtual Machine has exited with a code of -1"

    Posted May 20, 2014 08:26 AM

    I was having an issue where SEPM 12.1.4 was not receiveing the latest updates. I created a forum thread (https://www-secure.symantec.com/connect/forums/sepm-not-getting-latest-virus-definitions) to get some advice and it was suggested that I move the DB from SQL express to full blown SQL. I did that and initially there were no issues. I was able to login to SEPM, lauch live update, get the version in SEPM to match the latest live update version. Then I restarted the server and tried to lgoin to SEPM again and it failed with "failed to connect to the server"

     

     Checked the server services and found the Symantec Endpoint Protection Manager service was stopped.  I started it, but about a minute later it would stop and the Application Event Log said "The Java Virtual Machine has exited with a code of -1, the service is being stopped" with a source of "semsrv", Event ID "4096".  Starting the service again and reboots of the server did not help.

     

    Not really sure what I should try next. Any suggestions?



  • 2.  RE: Cannot start SEPM service, after moving DB to SQL standard. Get error: "The Java Virtual Machine has exited with a code of -1"

    Posted May 20, 2014 08:31 AM

    Can you turn on advanced debugging?

    How to debug the Symantec Endpoint Protection Manager

    You can post scm-server-log here for review



  • 3.  RE: Cannot start SEPM service, after moving DB to SQL standard. Get error: "The Java Virtual Machine has exited with a code of -1"

    Broadcom Employee
    Posted May 20, 2014 08:35 AM

    post the scm-server-0.log



  • 4.  RE: Cannot start SEPM service, after moving DB to SQL standard. Get error: "The Java Virtual Machine has exited with a code of -1"

    Posted May 20, 2014 08:42 AM

    2014-05-20 08:37:19.730 THREAD 12 SEVERE: ================== Server Environment ===================
    2014-05-20 08:37:19.733 THREAD 12 SEVERE: os.name = Windows Server 2008 R2
    2014-05-20 08:37:19.734 THREAD 12 SEVERE: os.version = 6.1
    2014-05-20 08:37:19.735 THREAD 12 SEVERE: os.arch = x64
    2014-05-20 08:37:19.735 THREAD 12 SEVERE: java.version = 1.7.0_25
    2014-05-20 08:37:19.736 THREAD 12 SEVERE: java.vendor = Oracle Corporation
    2014-05-20 08:37:19.737 THREAD 12 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
    2014-05-20 08:37:19.737 THREAD 12 SEVERE: java.vm.version = 23.25-b01
    2014-05-20 08:37:19.738 THREAD 12 SEVERE: java.home = D:\Symantec\jre
    2014-05-20 08:37:19.739 THREAD 12 SEVERE: catalina.home = D:\Symantec\tomcat
    2014-05-20 08:37:19.739 THREAD 12 SEVERE: java.user = null
    2014-05-20 08:37:19.740 THREAD 12 SEVERE: user.language = en
    2014-05-20 08:37:19.741 THREAD 12 SEVERE: user.country = US
    2014-05-20 08:37:19.741 THREAD 12 SEVERE: scm.server.version = 12.1.4013.4013
    2014-05-20 08:39:32.815 THREAD 12 SEVERE: 
    org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Unable to get information from SQL Server: ROS-AVSRV04.)
        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:1266)
        at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1185)
        at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1080)
        at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
        at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
        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:633)
        at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:657)
        at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1637)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
        at java.util.concurrent.FutureTask.run(FutureTask.java:166)
        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:724)
    Caused by: java.sql.SQLException: Unable to get information from SQL Server: ROS-AVSRV04.
        at net.sourceforge.jtds.jdbc.MSSqlServerInfo.<init>(MSSqlServerInfo.java:97)
        at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:276)
        at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)
        at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:184)
        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)
        ... 26 more
    2014-05-20 08:39:32.830 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:1266)
        at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1185)
        at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1080)
        at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
        at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
        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:633)
        at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:657)
        at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1637)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
        at java.util.concurrent.FutureTask.run(FutureTask.java:166)
        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:724)
    2014-05-20 08:39:32.868 THREAD 12 SEVERE: DomainId: null
    SiteId: null
    ServerId: 313AF395AC15047400358542C636BD25
    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:1266)
        at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1185)
        at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1080)
        at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
        at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
        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:633)
        at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:657)
        at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1637)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
        at java.util.concurrent.FutureTask.run(FutureTask.java:166)
        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:724)
    com.sygate.scm.server.util.ServerException: Unexpected server error.
        at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:399)
        at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:364)
        at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:360)
        at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:356)
        at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:314)
        at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1266)
        at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1185)
        at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1080)
        at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
        at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
        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:633)
        at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:657)
        at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1637)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
        at java.util.concurrent.FutureTask.run(FutureTask.java:166)
        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:724)
    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)
        ... 17 more
    2014-05-20 08:39:39.873 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:401)
        at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:364)
        at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:360)
        at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:356)
        at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:314)
        at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1266)
        at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1185)
        at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1080)
        at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
        at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
        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:633)
        at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:657)
        at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1637)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
        at java.util.concurrent.FutureTask.run(FutureTask.java:166)
        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:724)
    Caused by: java.lang.NullPointerException
        at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:290)
        ... 24 more

     



  • 5.  RE: Cannot start SEPM service, after moving DB to SQL standard. Get error: "The Java Virtual Machine has exited with a code of -1"

    Posted May 20, 2014 09:15 AM

    see this articles

    Event ID 4096 Java -1 error in event viewer, SEPM service will not stay in started state. "Failed to connect to server" message during login to SEPM.

    Article:TECH181655  | Created: 2012-02-17  | Updated: 2012-12-17  | Article URL http://www.symantec.com/docs/TECH181655

    Error semsrv Event Id 4096 , Symantec Endpoint Protection Manager service does not start

    Article:TECH194813  | Created: 2012-08-13  | Updated: 2013-05-31  | Article URL http://www.symantec.com/docs/TECH194813


  • 6.  RE: Cannot start SEPM service, after moving DB to SQL standard. Get error: "The Java Virtual Machine has exited with a code of -1"

    Posted May 20, 2014 09:53 AM

    Thanks James but unfortunately neither of those apply to the issue in my case.



  • 7.  RE: Cannot start SEPM service, after moving DB to SQL standard. Get error: "The Java Virtual Machine has exited with a code of -1"

    Posted May 20, 2014 09:55 AM

    pete, Brain, I am waiting for the moderators to approve the log output post.



  • 8.  RE: Cannot start SEPM service, after moving DB to SQL standard. Get error: "The Java Virtual Machine has exited with a code of -1"

    Posted May 20, 2014 10:01 AM

    Can you ensure SQL service is up and running as well?



  • 9.  RE: Cannot start SEPM service, after moving DB to SQL standard. Get error: "The Java Virtual Machine has exited with a code of -1"

    Posted May 20, 2014 10:43 AM

    Yes, SQL services are running. I can connect to the instance in SQL studio and can see the DB.



  • 10.  RE: Cannot start SEPM service, after moving DB to SQL standard. Get error: "The Java Virtual Machine has exited with a code of -1"

    Broadcom Employee
    Posted May 21, 2014 10:40 AM

    Hi,

    Restart both SQL agent and SQL server services. Restart Symantec Endpoint Protection Manager service as well.


     



  • 11.  RE: Cannot start SEPM service, after moving DB to SQL standard. Get error: "The Java Virtual Machine has exited with a code of -1"

    Posted May 21, 2014 10:46 AM

    Try this

    Tuning the Performance of the Symantec Endpoint Protection Manager console

    Article:TECH105179  | Created: 2008-01-18  | Updated: 2013-11-05  | Article URL http://www.symantec.com/docs/TECH105179

     

    see this thread if more troubleshooting

    https://www-secure.symantec.com/connect/forums/sepm-121-cannot-log-management-console