Endpoint Protection

 View Only
  • 1.  SEPM Not able to start

    Posted Oct 22, 2012 10:05 AM

    here is the log. I have installed SEPM on windows server 2008 r2 64bit

    2012-10-22 19:31:46.417 SEVERE: ================== Server Environment ===================
    2012-10-22 19:31:46.432 SEVERE: os.name = Windows Server 2008
    2012-10-22 19:31:46.432 SEVERE: os.version = 6.1
    2012-10-22 19:31:46.432 SEVERE: os.arch = x86
    2012-10-22 19:31:46.432 SEVERE: java.version = 1.6.0_14
    2012-10-22 19:31:46.432 SEVERE: java.vendor = Sun Microsystems Inc.
    2012-10-22 19:31:46.432 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
    2012-10-22 19:31:46.432 SEVERE: java.vm.version = 14.0-b16
    2012-10-22 19:31:46.432 SEVERE: java.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\jdk\jre
    2012-10-22 19:31:46.432 SEVERE: catalina.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat
    2012-10-22 19:31:46.432 SEVERE: java.user = null
    2012-10-22 19:31:46.432 SEVERE: user.language = en
    2012-10-22 19:31:46.432 SEVERE: user.country = US
    2012-10-22 19:31:46.432 SEVERE: scm.server.version = 11.0.5002.333
    2012-10-22 19:31:48.414 SEVERE: ================== StartClientTransport ===================
    2012-10-22 19:31:48.460 SEVERE: Unknown Exception in: com.sygate.scm.server.servlet.StartupServlet
    java.lang.Exception: HTTP 500 Internal Server Error, URL: http://localhost:8014/secars/secars.dll?action=34
        at com.sygate.scm.common.communicate.Communicator.getRequestInputStream(Communicator.java:626)
        at com.sygate.scm.server.util.ClientTransportHelper.startClientTransport(ClientTransportHelper.java:147)
        at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:106)
        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:597)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:151)
    com.sygate.scm.common.communicate.CommunicationException: Unexpected server error. ErrorCode: 0x10010000
        at com.sygate.scm.common.communicate.Communicator.getRequestInputStream(Communicator.java:650)
        at com.sygate.scm.server.util.ClientTransportHelper.startClientTransport(ClientTransportHelper.java:147)
        at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:106)
        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:597)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:151)
     



  • 2.  RE: SEPM Not able to start

    Posted Oct 22, 2012 10:12 AM

    HI,

    What error are occured when you have try to login in SEPM console ?

    Check this artical

    500 INTERNAL SERVER ERROR clients are not able to register with the Symantec Endpoint Protection Manager

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

    Unexpected server error 0x10010000 <site name> <server>

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



  • 3.  RE: SEPM Not able to start

    Broadcom Employee
    Posted Oct 22, 2012 10:24 AM

    Hi,

    Possible Cause:IIS is set to 32-bit mode on Windows Server 2008 64 bit operating system when installing Symantec Endpoint Protection Manager. This can also occur if another website is subsequently installed that requires 32-bit compatibility (for example, Windows Server Update Services (WSUS).

    Possible Solution:

    Switch IIS to 64 bit mode

    1. Open IIS > Application Pool and look for Default App Pool.
    2. Right click on DefaultApp Pool and choose Advanced Settings...
    3. Change the “Enable 32-bit Applications” to False.

    This should disable the 32-bit functionality & enable the 64-bit functionality.

    Go through the following article to know more details:

    Java -1 Errors and HTTP 500 errors when connecting to the Symantec Endpoint Protection Manager on a Windows Server 2008 64 bit'

    http://www.symantec.com/docs/TECH96006



  • 4.  RE: SEPM Not able to start

    Posted Oct 22, 2012 10:24 AM


  • 5.  RE: SEPM Not able to start
    Best Answer

    Trusted Advisor
    Posted Oct 22, 2012 10:34 AM

    Hello,

    This also happens if install SEPM on Windows Server 2008 64bit. If so, please run following to run IIS as 64 bit mode.

    Set the Enable32bitAppOnWin64 option to False at the Parent level under the master Web site level. To do this, follow these steps:

    1. In IIS Manager, click Application Pools.
    2. In the Actions pane, click Set Application Pool Defaults.
    3. In the General section, set the Enable32bitAppOnWin64 option to False.

    Check this Article:

    Java -1 Errors and HTTP 500 errors when connecting to the Symantec Endpoint Protection Manager on a Windows Server 2008 64 bit

    http://www.symantec.com/docs/TECH96006

    How do you run the Symantec Endpoint Protection Manager (SEPM) on a 64-bit machine - IIS (7 or 6), the Database (Embedded or SQL), ASP(1.0 and 2.0), Java as 32-bit or 64-bit

    http://www.symantec.com/docs/TECH96970

    Again, The minimum SEP 11 version you should be using is in the RU7 family; 11.0.7000, 11.0.7100 or latest of the SEP 11's, 11.0.7200.

    Is this a fresh installation or was the SEPM working previously?

    If this is a Fresh Installation, the first suggestion would be to install SEP 11.0.7200 rather than older version of SEP 11.0 RU5. Check this - 

    Latest Symantec Endpoint Protection Releases - SEP 12.1 RU1 MP1 and SEP 11.0. RU7 MP2

    Hope that helps!!



  • 6.  RE: SEPM Not able to start

    Posted Oct 23, 2012 01:25 AM

    Thanks Mithun its started working