Endpoint Protection

 View Only
Expand all | Collapse all

Problems starting SEPM console

  • 1.  Problems starting SEPM console

    Posted Jun 23, 2009 03:54 PM
    Our installation of SEP 11.0.4 was running great until the other day when I attempted to log in.   The initial errors were that it could not connect to the report server.   After following the advice of others in the forum to attempt to do a repair install, now when attempting to log in to SEPM, receive the "Failed to Connect to Server" message.   Looking at services, noticed that the Symantec Endpoint Protection Manager service is stopped.  Start the service, and it starts, then shuts down after about 10 seconds and displays "The Java Virtual Machine has exited with a code of -1" in the event viewer. 

    I've done the following troubleshooting steps:

    1) Ran the Management Server Configuration Wizard.
    2)  Verifies that USERS has the correct permissions to the directory that SEP is installed to.
    3) Verified that
    3) Put Tomcat in debug mode.  Below are the debug files:

    This is the catalina.out file:

    Jun 23, 2009 12:01:56 PM org.apache.coyote.http11.Http11BaseProtocol init
    INFO: Initializing Coyote HTTP/1.1 on http-9090
    Jun 23, 2009 12:01:58 PM org.apache.coyote.http11.Http11BaseProtocol init
    INFO: Initializing Coyote HTTP/1.1 on http-8443
    Starting service SCM
    Apache Tomcat/4.1.37-LE-jdk1.4
    Has valid SAV license
    Info>> No SNAC license file in E:\Symantec\Symantec Endpoint Protection Manager\tomcat\etc\license
    Jun 23, 2009 12:02:01 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: ================== Server Environment ===================
    Jun 23, 2009 12:02:01 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: os.name = Windows 2003
    Jun 23, 2009 12:02:01 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: os.version = 5.2
    Jun 23, 2009 12:02:01 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: os.arch = x86
    Jun 23, 2009 12:02:01 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: java.version = 1.5.0_15
    Jun 23, 2009 12:02:01 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: java.vendor = Sun Microsystems Inc.
    Jun 23, 2009 12:02:01 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: java.vm.name = Java HotSpot(TM) Server VM
    Jun 23, 2009 12:02:01 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: java.vm.version = 1.5.0_15-b04
    Jun 23, 2009 12:02:01 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: java.home = E:\Symantec\Symantec Endpoint Protection Manager\jdk\jre
    Jun 23, 2009 12:02:01 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: catalina.home = E:\Symantec\Symantec Endpoint Protection Manager\tomcat
    Jun 23, 2009 12:02:01 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: java.user = null
    Jun 23, 2009 12:02:01 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: user.language = en
    Jun 23, 2009 12:02:01 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: user.country = US
    Jun 23, 2009 12:02:01 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: scm.server.version = 11.0.4000.2295


    And below is the scm-server-0.log file:

    2009-06-23 12:02:01.569 SEVERE: ================== Server Environment ===================
    2009-06-23 12:02:01.569 SEVERE: os.name = Windows 2003
    2009-06-23 12:02:01.569 SEVERE: os.version = 5.2
    2009-06-23 12:02:01.569 SEVERE: os.arch = x86
    2009-06-23 12:02:01.569 SEVERE: java.version = 1.5.0_15
    2009-06-23 12:02:01.569 SEVERE: java.vendor = Sun Microsystems Inc.
    2009-06-23 12:02:01.569 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
    2009-06-23 12:02:01.569 SEVERE: java.vm.version = 1.5.0_15-b04
    2009-06-23 12:02:01.569 SEVERE: java.home = E:\Symantec\Symantec Endpoint Protection Manager\jdk\jre
    2009-06-23 12:02:01.569 SEVERE: catalina.home = E:\Symantec\Symantec Endpoint Protection Manager\tomcat
    2009-06-23 12:02:01.569 SEVERE: java.user = null
    2009-06-23 12:02:01.585 SEVERE: user.language = en
    2009-06-23 12:02:01.585 SEVERE: user.country = US
    2009-06-23 12:02:01.585 SEVERE: scm.server.version = 11.0.4000.2295
    2009-06-23 12:02:04.632 SEVERE: ================== StartClientTransport ===================
    2009-06-23 12:02:04.788 SEVERE: Unknown Exception in: com.sygate.scm.server.servlet.StartupServlet
    java.io.IOException: Error writing to server
    at sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:421)
    at sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:433)
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:955)
    at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:367)
    at com.sygate.scm.common.communicate.Communicator.getRequestInputStream(Communicator.java:542)
    at com.sygate.scm.server.util.ClientTransportHelper.startClientTransport(ClientTransportHelper.java:72)
    at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:104)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:880)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:768)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3484)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:3710)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1148)
    at org.apache.catalina.core.StandardHost.start(StandardHost.java:697)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1148)
    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:311)
    at org.apache.catalina.core.StandardService.start(StandardService.java:450)
    at org.apache.catalina.core.StandardServer.start(StandardServer.java:2213)
    at org.apache.catalina.startup.Catalina.start(Catalina.java:484)
    at org.apache.catalina.startup.Catalina.execute(Catalina.java:371)
    at org.apache.catalina.startup.Catalina.process(Catalina.java:134)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:151)
    com.sygate.scm.common.communicate.CommunicationException: Failed to connect to the server.

    Make sure that the server is running and your session has not timed out.
    If you can reach the server but cannot log on, make sure that you provided the correct parameters.
    If you are experiencing network issues, contact your system administrator. ErrorCode: 0x80020000
    at com.sygate.scm.common.communicate.Communicator.getRequestInputStream(Communicator.java:575)
    at com.sygate.scm.server.util.ClientTransportHelper.startClientTransport(ClientTransportHelper.java:72)
    at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:104)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:880)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:768)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3484)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:3710)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1148)
    at org.apache.catalina.core.StandardHost.start(StandardHost.java:697)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1148)
    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:311)
    at org.apache.catalina.core.StandardService.start(StandardService.java:450)
    at org.apache.catalina.core.StandardServer.start(StandardServer.java:2213)
    at org.apache.catalina.startup.Catalina.start(Catalina.java:484)
    at org.apache.catalina.startup.Catalina.execute(Catalina.java:371)
    at org.apache.catalina.startup.Catalina.process(Catalina.java:134)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:151)


    Anyone have any suggestions?

    Thanks!

    Mike



  • 2.  RE: Problems starting SEPM console
    Best Answer

    Posted Jun 23, 2009 04:14 PM
    Rebooted the server and it's fat dumb and happy!


  • 3.  RE: Problems starting SEPM console

    Posted Jun 30, 2009 11:45 AM
    Change port from 8005 to 8006 and restart sepm service.