Endpoint Protection

 View Only
  • 1.  Symantec Enpoint Protection Manager service doesn't stay running

    Posted Apr 21, 2010 04:30 AM

    Hi

    I have problem with login to SEP Console, so I search for the problem and I see that the service Symantec SEP dosn't stay running.


    The log of the scm-server-0.log is:

    2010-04-21 10:21:33.187 GRAVE: ================== Server Environment ===================
    2010-04-21 10:21:33.187 GRAVE: os.name = Windows 2003
    2010-04-21 10:21:33.187 GRAVE: os.version = 5.2
    2010-04-21 10:21:33.187 GRAVE: os.arch = x86
    2010-04-21 10:21:33.187 GRAVE: java.version = 1.5.0_15
    2010-04-21 10:21:33.187 GRAVE: java.vendor = Sun Microsystems Inc.
    2010-04-21 10:21:33.187 GRAVE: java.vm.name = Java HotSpot(TM) Server VM
    2010-04-21 10:21:33.187 GRAVE: java.vm.version = 1.5.0_15-b04
    2010-04-21 10:21:33.187 GRAVE: java.home = E:\Symantec\Symantec Endpoint Protection Manager\jdk\jre
    2010-04-21 10:21:33.187 GRAVE: catalina.home = E:\Symantec\Symantec Endpoint Protection Manager\tomcat
    2010-04-21 10:21:33.203 GRAVE: java.user = null
    2010-04-21 10:21:33.203 GRAVE: user.language = it
    2010-04-21 10:21:33.203 GRAVE: user.country = IT
    2010-04-21 10:21:33.203 GRAVE: scm.server.version = 11.0.4202.75
    2010-04-21 10:21:35.640 GRAVE: ================== StartClientTransport ===================
    2010-04-21 10:21:36.921 GRAVE: Unknown Exception in: com.sygate.scm.server.servlet.StartupServlet
    java.net.ConnectException: Connection refused: connect
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
        at java.net.Socket.connect(Socket.java:520)
        at java.net.Socket.connect(Socket.java:470)
        at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
        at sun.net.www.http.HttpClient.openServer(HttpClient.java:388)
        at sun.net.www.http.HttpClient.openServer(HttpClient.java:523)
        at sun.net.www.http.HttpClient.<init>(HttpClient.java:231)
        at sun.net.www.http.HttpClient.New(HttpClient.java:304)
        at sun.net.www.http.HttpClient.New(HttpClient.java:321)
        at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:813)
        at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:765)
        at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:690)
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:934)
        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: Impossibile connettersi al server.

    Assicurarsi che il server sia in esecuzione e che la sessione non sia scaduta.
    Se è possibile raggiungere il server ma non eseguire l'accesso, verificare di aver specificato i parametri corretti.
    In caso di problemi relativi alla rete, contattare l'amministratore di sistema. 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)

    Can someone help me on finding the problem?

    Thanks


  • 2.  RE: Symantec Enpoint Protection Manager service doesn't stay running

    Posted Apr 21, 2010 04:50 AM
    Restart the server and try?
    If not helps repair SEPM from add/remove programs.
    Do do done any configuration changes recently?


  • 3.  RE: Symantec Enpoint Protection Manager service doesn't stay running

    Posted Apr 21, 2010 05:00 AM

    I have restarted the server twice, trying also to change the version of java from 1.6 to 1.5 but I see that there is a version of java under the \Symantec Endpoint Protection Manager\jdk\bin and it is always the 1.5 version.

    No configuration changes recently. I will try to repair SEPM.


  • 4.  RE: Symantec Enpoint Protection Manager service doesn't stay running

    Posted Apr 21, 2010 05:08 AM
    do not try to change java version.If any java you installed separately in SEPM uninstall it.


  • 5.  RE: Symantec Enpoint Protection Manager service doesn't stay running

    Posted Apr 21, 2010 06:25 AM

    I have unistalled all the java version that were installed outside SEPM.
    I have installed the new version of SEPM (11.0.5) over the old version (11.0.4202), beacuse i haven't anymore the installer files of 11.0.4202 to make a repair.
    I have reboot the server after all operation, but the service doesn't stay running.

    I had to unistall and re-install SEPM?
    In this case can I save all the configuration that i have inside the SEPM to avoid reconfiguring all?

    Thanks


  • 6.  RE: Symantec Enpoint Protection Manager service doesn't stay running

    Posted Apr 21, 2010 07:54 AM

    Hi Michele,

    Are you running the embedded database? If so, it sounds like you have some database damage.  The problem you are going to run into is if you did the backups (database + keystore), you have to use the same version of the SEPM for the recovery to work. You might have to do a fresh install. There is an application called SylinkReplacer that allows for an updated sylink.xml file to be pushed out via subnet. I know you'll to create new policies, groups etc... But, if you have a lot of clients that need the new sylink.xml file, this tool can be a time saver.

    SylinkReplacer:
    https://www-secure.symantec.com/connect/downloads/sylinkreplacer-tool-connecting-sep-clients-sepm

    If you have to do a fresh install, might as well upgrade to the latest and greatest RU6. Hop on fileconnect and download the install files.

    Mike



  • 7.  RE: Symantec Enpoint Protection Manager service doesn't stay running

    Posted Apr 21, 2010 09:34 AM
    Hey,

    Also check if in IIS the Symantec website is started.

    Make sure that the Embedded database service is started (if using Embedded Database.)