Endpoint Protection

 View Only
Expand all | Collapse all

Problem with SEP Manager Console after upgrading server from 2003 R2 to 2008 SP2

  • 1.  Problem with SEP Manager Console after upgrading server from 2003 R2 to 2008 SP2

    Posted Aug 20, 2009 07:46 AM
    Hi

    I have just finished upgrading from Server 2003 R2 to 2008 SP2 on the server running our EndPoint Protection. After doing so I can't connect to the management console. I get the following message:
    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.

    I have tried running the "Management Server Configuration Wizard" but that doesn't change the result.

    Might this be a problem because Server 2008 uses different ports than Server 2003 and that why I can't connect?

    /Lasse



  • 2.  RE: Problem with SEP Manager Console after upgrading server from 2003 R2 to 2008 SP2
    Best Answer

    Posted Aug 20, 2009 07:55 AM
    From

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

    find the scm-server0.log and paste it here.

    find the ports related to symantec


    https://www-secure.symantec.com/connect/forums/what-ports-are-used

    first do a repair of sepm  from add/remove programs

    paste the logs here

    the problem should be related to IIS

    is this a 64 bit server?




  • 3.  RE: Problem with SEP Manager Console after upgrading server from 2003 R2 to 2008 SP2

    Posted Aug 20, 2009 07:59 AM
    posting scm-server0. log and catalina.out might help us find the root cause.Both of them are located under drive :\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs


  • 4.  RE: Problem with SEP Manager Console after upgrading server from 2003 R2 to 2008 SP2

    Broadcom Employee
    Posted Aug 20, 2009 08:05 AM

    what is the port , that has been set to use now?

    can you verify if the conf.properties under the \Symantec Endpoint Protection Manager\tomcat\etc  to verify the ports..

     

    check the scm-server-0.log for error



  • 5.  RE: Problem with SEP Manager Console after upgrading server from 2003 R2 to 2008 SP2

    Posted Aug 20, 2009 08:26 AM
    We are running on a 32 bit system and I have already tried running a repair.

    scm-server-0.log:
    2009-08-20 12:05:09.443 SEVERE: ================== Server Environment ===================
    2009-08-20 12:05:09.445 SEVERE: os.name = Windows Vista
    2009-08-20 12:05:09.445 SEVERE: os.version = 6.0
    2009-08-20 12:05:09.446 SEVERE: os.arch = x86
    2009-08-20 12:05:09.446 SEVERE: java.version = 1.5.0_15
    2009-08-20 12:05:09.447 SEVERE: java.vendor = Sun Microsystems Inc.
    2009-08-20 12:05:09.447 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
    2009-08-20 12:05:09.447 SEVERE: java.vm.version = 1.5.0_15-b04
    2009-08-20 12:05:09.448 SEVERE: java.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\jdk\jre
    2009-08-20 12:05:09.448 SEVERE: catalina.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat
    2009-08-20 12:05:09.449 SEVERE: java.user = null
    2009-08-20 12:05:09.449 SEVERE: user.language = en
    2009-08-20 12:05:09.450 SEVERE: user.country = US
    2009-08-20 12:05:09.450 SEVERE: scm.server.version = 11.0.4202.75
    2009-08-20 12:05:11.814 SEVERE: ================== StartClientTransport ===================
    2009-08-20 12:05:11.997 SEVERE: Unknown Exception in: com.sygate.scm.server.servlet.StartupServlet
    java.lang.Exception: HTTP 400 Bad Request, URL: http://localhost:8014/secars/secars.dll?action=34
     at com.sygate.scm.common.communicate.Communicator.getRequestInputStream(Communicator.java:556)
     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: Unexpected server error. ErrorCode: 0x10010000
     at com.sygate.scm.common.communicate.Communicator.getRequestInputStream(Communicator.java:580)
     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)

    catalina.out:
    Aug 20, 2009 12:05:05 PM org.apache.coyote.http11.Http11BaseProtocol init
    INFO: Initializing Coyote HTTP/1.1 on http-9090
    Aug 20, 2009 12:05:06 PM org.apache.coyote.http11.Http11BaseProtocol init
    INFO: Initializing Coyote HTTP/1.1 on http-8444
    Starting service SCM
    Apache Tomcat/4.1.37-LE-jdk1.4
    Has valid SAV license
    Info>> No SNAC license file in C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\etc\license
    Aug 20, 2009 12:05:09 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: ================== Server Environment ===================
    Aug 20, 2009 12:05:09 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: os.name = Windows Vista
    Aug 20, 2009 12:05:09 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: os.version = 6.0
    Aug 20, 2009 12:05:09 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: os.arch = x86
    Aug 20, 2009 12:05:09 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: java.version = 1.5.0_15
    Aug 20, 2009 12:05:09 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: java.vendor = Sun Microsystems Inc.
    Aug 20, 2009 12:05:09 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: java.vm.name = Java HotSpot(TM) Server VM
    Aug 20, 2009 12:05:09 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: java.vm.version = 1.5.0_15-b04
    Aug 20, 2009 12:05:09 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: java.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\jdk\jre
    Aug 20, 2009 12:05:09 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: catalina.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat
    Aug 20, 2009 12:05:09 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: java.user = null
    Aug 20, 2009 12:05:09 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: user.language = en
    Aug 20, 2009 12:05:09 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: user.country = US
    Aug 20, 2009 12:05:09 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: scm.server.version = 11.0.4202.75


  • 6.  RE: Problem with SEP Manager Console after upgrading server from 2003 R2 to 2008 SP2

    Posted Aug 20, 2009 08:37 AM
    Seeems like in your IIS
    You have restrictions for IP
    By default it should be all allowed

    http://support.microsoft.com/kb/842693

    Make the above change on your IIS 7..





  • 7.  RE: Problem with SEP Manager Console after upgrading server from 2003 R2 to 2008 SP2

    Posted Aug 21, 2009 03:21 AM
    Hi Rafeeq

    Do you know how I change the restrictions on a Server 2008 running IIS 7?


  • 8.  RE: Problem with SEP Manager Console after upgrading server from 2003 R2 to 2008 SP2

    Posted Aug 21, 2009 03:50 AM
    you need to reinstall SEPM
    only backup database and server certificate

    or try to Repair SEPM from Programs and features


  • 9.  RE: Problem with SEP Manager Console after upgrading server from 2003 R2 to 2008 SP2

    Posted Aug 21, 2009 03:59 AM
    When you say reinstall, do you meen that I have to completely remove SEPM and then install it again?

    I have tried backing up a SEPM database before and then restoring it, after doing a fresh installation of SEPM, but in that case after doing the restore I couldn't open SEPM.


  • 10.  RE: Problem with SEP Manager Console after upgrading server from 2003 R2 to 2008 SP2

    Posted Aug 21, 2009 04:26 AM
    Hi

    I have added the rights to the SEPM folder and subfolder but it doesn't change the result.

    If I start all the SEPM services and try to login to the SEPM console and it fails then the "Symantec Endpoint Protection Manager" services is stopped.

    I am sure that is's a problem with rights/permissions on the server after doing the upgrade to Server 2008. I could properly get it to work by removing SEPM completely and then install it from the beginning but then I have to add all our users to the SEPM again.


  • 11.  RE: Problem with SEP Manager Console after upgrading server from 2003 R2 to 2008 SP2

    Posted Aug 21, 2009 04:26 AM
    than it seems that SEPM service cannot start

    try to give  rights to SEPM  folder (and subfolders) to :
    1) iis_iuser - read rights
    2) full rights to NETWORK SERVICE user

    and try to start SEPM service




  • 12.  RE: Problem with SEP Manager Console after upgrading server from 2003 R2 to 2008 SP2

    Posted Aug 21, 2009 05:20 AM
    can you try running iis diag

    http://www.iis.net/downloads/default.aspx?tabid=34&g=6&i=1286

    this will tell u where permissions are missing.



  • 13.  RE: Problem with SEP Manager Console after upgrading server from 2003 R2 to 2008 SP2

    Posted Aug 21, 2009 05:48 AM
    check that SEPM service is stoped
    then delete all logs in Symantec Endpoint Protection Manager\tomcat\logs
    start SEPM service and look for semsvc.exe process in task manager
    when it will disapper - post scm-server-0.log here


  • 14.  RE: Problem with SEP Manager Console after upgrading server from 2003 R2 to 2008 SP2

    Posted Aug 21, 2009 06:01 AM

    Here is the result. Check the line with BOLD.
    I did a check of the folder "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Inetpub\secars" and the folder is empty, no secars.dll.
    Might the problem be that Server 2003 used the folder C:\Program Files and Server 2008 uses ProgramData?

    I just tried running the installation for the SEPM and it returned the following message:
    Unable to copy installation file (.\SEPM\SAV.XML) to the Symantec Endpoint Protection Manager application

    2009-08-21 09:54:36.509 SEVERE: ================== Server Environment ===================
    2009-08-21 09:54:36.510 SEVERE: os.name = Windows Vista
    2009-08-21 09:54:36.511 SEVERE: os.version = 6.0
    2009-08-21 09:54:36.511 SEVERE: os.arch = x86
    2009-08-21 09:54:36.512 SEVERE: java.version = 1.5.0_15
    2009-08-21 09:54:36.512 SEVERE: java.vendor = Sun Microsystems Inc.
    2009-08-21 09:54:36.512 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
    2009-08-21 09:54:36.513 SEVERE: java.vm.version = 1.5.0_15-b04
    2009-08-21 09:54:36.513 SEVERE: java.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\jdk\jre
    2009-08-21 09:54:36.514 SEVERE: catalina.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat
    2009-08-21 09:54:36.514 SEVERE: java.user = null
    2009-08-21 09:54:36.515 SEVERE: user.language = en
    2009-08-21 09:54:36.515 SEVERE: user.country = US
    2009-08-21 09:54:36.516 SEVERE: scm.server.version = 11.0.4202.75
    2009-08-21 09:54:38.557 SEVERE: ================== StartClientTransport ===================
    2009-08-21 09:54:38.628 SEVERE: Unknown Exception in: com.sygate.scm.server.servlet.StartupServlet
    java.lang.Exception: HTTP 400 Bad Request, URL: http://localhost:8014/secars/secars.dll?action=34
     at com.sygate.scm.common.communicate.Communicator.getRequestInputStream(Communicator.java:556)
     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: Unexpected server error. ErrorCode: 0x10010000
     at com.sygate.scm.common.communicate.Communicator.getRequestInputStream(Communicator.java:580)
     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)
     



  • 15.  RE: Problem with SEP Manager Console after upgrading server from 2003 R2 to 2008 SP2

    Posted Aug 21, 2009 06:17 AM
    ok
    now please try to give full control to EVERYONE to SEPM folder and subfolders
    and start the sepm service


  • 16.  RE: Problem with SEP Manager Console after upgrading server from 2003 R2 to 2008 SP2

    Posted Aug 21, 2009 06:53 AM

    I just tried doing a repair (again), this time it completed successfully and it looks like SEPM is working again.

    Thanks for all the replies and suggestions.



  • 17.  RE: Problem with SEP Manager Console after upgrading server from 2003 R2 to 2008 SP2

    Posted Aug 21, 2009 07:10 AM
    Happy that its working fine now
    my first suggestion was to do a repair.
    wondering why the repair worked this time
    400 does have anything with authentication
    its just saying that it does not know where the home folders are ( inetpub) where configurations are saved.
    doing a repair, put the sepm configurations in IIS , its  7 after upgrade



  • 18.  RE: Problem with SEP Manager Console after upgrading server from 2003 R2 to 2008 SP2

    Posted Aug 21, 2009 07:27 AM
    the first repair didn't help cause NETWORK SERVICE and iis users didn't have access to some files\folders