Endpoint Protection

 View Only
Expand all | Collapse all

Cannot login to SEP Manager - Failed to connect to server

Migration User

Migration UserMay 07, 2009 07:25 AM

Migration User

Migration UserMay 28, 2009 09:41 PM

  • 1.  Cannot login to SEP Manager - Failed to connect to server

    Posted Apr 27, 2009 04:42 PM
    Hello,

    I'm not sure what I'm missing here.

    I"ve installed Symantec Endpoint Protection multiple times allowing SEP to create its own ports.  No other software is running on this server.
    Attempts to login to SEP Manager returns: 

    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've checked and ensured all SEP related services are running and that the website is running in IIS.

    Any thoughts would be appreciated.

    Regards,
    Rudy


  • 2.  RE: Cannot login to SEP Manager - Failed to connect to server

    Posted Apr 27, 2009 04:55 PM
    Do you think you could post the event log for this? You might just try resetting the IIS services. To do this follow these steps:

    Click Start, then Run.
    Type inetmgr, then click OK.
    Right click on the Server name (location) immediately under Internet Information Services.
    Click Disconnect.
    Close the Internet Information Services (IIS) Manager window.
    Click Start, then Run.
    Type services.msc, then click OK.
    Right-click the IIS Admin Service and click Restart.


    This is also posted in our KB at this link.

    http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008030400460348

    Hope this helps,
    Grant-



  • 3.  RE: Cannot login to SEP Manager - Failed to connect to server

    Posted Apr 27, 2009 07:45 PM
    Hi Rudolf, are you running embedded or SQL database? usually this happens when there's communication error if you are using external database.


  • 4.  RE: Cannot login to SEP Manager - Failed to connect to server

    Broadcom Employee
    Posted Apr 28, 2009 01:38 AM
    hi,
    hopefully the DB is running.
    check for the timestamp in the scm-server-o.log for the error..

    Pete


  • 5.  RE: Cannot login to SEP Manager - Failed to connect to server

    Posted Apr 28, 2009 02:31 AM
     Could there be possible network issues that need to be looked at like policies on firewall at endpoints?


  • 6.  RE: Cannot login to SEP Manager - Failed to connect to server

    Posted Apr 28, 2009 03:03 AM
    Open and post these logs:
    c:\program files\symantec\sepm\tomcat\log\scm-server-0.log and catalina.out.
    IIS logs could be useful as well.


  • 7.  RE: Cannot login to SEP Manager - Failed to connect to server

    Posted Apr 28, 2009 01:35 PM
    I found this in the knowledgebase.  I hope this helps:

    http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008051410484848

    Here is the article:

    Symptoms:

    The Symantec Endpoint Protection Manager Service starts momentarily, then stops.
    Attempting to access the Reporting Website (http://<hostname>:<port>/reporting) via a web browser produces a 403 error page.
    Clients are unable to communicate with the SEPM.
    When attempting to log into the SEPM Console, the following error message is produced:
    "Failed to connect to 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."


    Cause:
    These errors can occur when Microsoft Internet Information Services (IIS) has been configured to block access based on IP Address or Domain Name.





    Solution:
    This issue can be resolved by either adding the IP address, Subnet range, or domain name of the client(s) you would like to be able to access the SEPM.
    Open the IIS Manager control panel
    Expand the local computer tree in the right panel
    Expand the Web Sites tree in the right panel
    Right-click on the Web Site containing the SEPM and Reporting virtual directories and choose Properties
    Click on the Directory Security Tab
    Click the Edit button under IP address and domain name restrictions
    Choose whether you want to allow all systems access to the SEPM Web Site by default, or whether you want to deny all systems access to the SEPM Web Site by default.
    To allow all systems access the SEPM website by default, choose the Granted Access radio button. Add any IPs, Subnets, or Domains you wish to block to the list.
    To deny all systems access the SEPM website by default, choose the Denied Access radio button. With this option all computers you wish to communicate with the SEPM MUST be added to the list.
    Restart the Symantec Endpoint Protection Manager Service.


  • 8.  RE: Cannot login to SEP Manager - Failed to connect to server

    Posted May 07, 2009 07:25 AM
    Please reset the password


  • 9.  RE: Cannot login to SEP Manager - Failed to connect to server

    Posted May 07, 2009 07:40 AM
    You can resolved this by either adding the IP address, Subnet range, or domain name of the client(s) you would like to be able to access the SEPM.

    1. Open the IIS Manager control panel
    2. Expand the local computer tree in the right panel
    3. Expand the Web Sites tree in the right panel
    4. Right-click on the Web Site containing the SEPM and Reporting virtual directories and choose Properties
    5. Click on the Directory Security Tab
    6. Click the Edit button under IP address and domain name restrictions
    7. Choose whether you want to allow all systems access to the SEPM Web Site by default, or whether you want to deny all systems access to the SEPM Web Site by default.
    1. To allow all systems access the SEPM website by default, choose the Granted Access radio button. Add any IPs, Subnets, or Domains you wish to block to the list.
    2. To deny all systems access the SEPM website by default, choose the Denied Access radio button. With this option all computers you wish to communicate with the SEPM MUST be added to the list.
    8. Restart the Symantec Endpoint Protection Manager Service.


  • 10.  RE: Cannot login to SEP Manager - Failed to connect to server

    Posted May 07, 2009 01:36 PM
    Guys, it is not worth giving all generic suggestions you are posting... if Rudolf wants our help it is better if he posts the logs.



  • 11.  RE: Cannot login to SEP Manager - Failed to connect to server

    Posted May 28, 2009 03:30 PM
    I have the exact same issue that Rudy does.

    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.

    If you don't mind me jumping in on this post I would like to share my logs.
    I am using a Windows XP sp3 in a VMWARE
    I have tried all these suggestions here and nothing is working.
    I go into the ODBC and reset the password and test the connection and it is successful.
    When I try to login I get the same thing. Failed to connect to the server, and I am on the server!
    I am using the embedded database just like in the default install procedures.

    Here is my Catalina.out file that Giuseppe was looking for.

    May 28, 2009 2:56:50 PM org.apache.coyote.http11.Http11BaseProtocol init
    INFO: Initializing Coyote HTTP/1.1 on http-9090
    May 28, 2009 2:56:51 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 C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\etc\license
    May 28, 2009 2:56:52 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: ================== Server Environment ===================
    May 28, 2009 2:56:52 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: os.name = Windows XP
    May 28, 2009 2:56:52 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: os.version = 5.1
    May 28, 2009 2:56:52 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: os.arch = x86
    May 28, 2009 2:56:52 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: java.version = 1.5.0_15
    May 28, 2009 2:56:52 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: java.vendor = Sun Microsystems Inc.
    May 28, 2009 2:56:52 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: java.vm.name = Java HotSpot(TM) Server VM
    May 28, 2009 2:56:52 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: java.vm.version = 1.5.0_15-b04
    May 28, 2009 2:56:52 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: java.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\jdk\jre
    May 28, 2009 2:56:52 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: catalina.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat
    May 28, 2009 2:56:52 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: java.user = null
    May 28, 2009 2:56:52 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: user.language = en
    May 28, 2009 2:56:52 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: user.country = US
    May 28, 2009 2:56:52 PM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: scm.server.version = 11.0.4014.26


    Here is scm-server-0.log

    2009-05-28 14:56:52.546 SEVERE: ================== Server Environment ===================
    2009-05-28 14:56:52.546 SEVERE: os.name = Windows XP
    2009-05-28 14:56:52.546 SEVERE: os.version = 5.1
    2009-05-28 14:56:52.546 SEVERE: os.arch = x86
    2009-05-28 14:56:52.546 SEVERE: java.version = 1.5.0_15
    2009-05-28 14:56:52.546 SEVERE: java.vendor = Sun Microsystems Inc.
    2009-05-28 14:56:52.546 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
    2009-05-28 14:56:52.546 SEVERE: java.vm.version = 1.5.0_15-b04
    2009-05-28 14:56:52.546 SEVERE: java.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\jdk\jre
    2009-05-28 14:56:52.546 SEVERE: catalina.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat
    2009-05-28 14:56:52.546 SEVERE: java.user = null
    2009-05-28 14:56:52.546 SEVERE: user.language = en
    2009-05-28 14:56:52.546 SEVERE: user.country = US
    2009-05-28 14:56:52.546 SEVERE: scm.server.version = 11.0.4014.26
    2009-05-28 14:56:56.031 SEVERE: ================== StartClientTransport ===================
    2009-05-28 14:56:56.343 SEVERE: Unknown Exception in: com.sygate.scm.server.servlet.StartupServlet
    java.lang.Exception: HTTP 500 Server Error, 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)



  • 12.  RE: Cannot login to SEP Manager - Failed to connect to server

    Posted May 28, 2009 05:43 PM

    Guys..thanks for the response...and sorry for the delay.  Away on other projects for some time.

    Ok.  I see the following:

    Application log on the Windows 2003 machine shows: 
    Event ID: 4096
    Source: semsrv
    The Java Virtual Machine has exited with a code of -1, the service is being stopped.

    I also see that Symantec Endpoint Protection Manager stops immediately even if manually started.

    I've checked a working server and installed the same version of Java VM - no luck.

    I've gone through Grant's recommendations and ESS & Breas suggestions - no go.

    Logs below:
    SCM-server-0.log
    2009-05-28 14:33:26.724 SEVERE: ================== Server Environment ===================
    2009-05-28 14:33:26.724 SEVERE: os.name = Windows 2003
    2009-05-28 14:33:26.724 SEVERE: os.version = 5.2
    2009-05-28 14:33:26.724 SEVERE: os.arch = x86
    2009-05-28 14:33:26.724 SEVERE: java.version = 1.5.0_15
    2009-05-28 14:33:26.724 SEVERE: java.vendor = Sun Microsystems Inc.
    2009-05-28 14:33:26.724 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
    2009-05-28 14:33:26.724 SEVERE: java.vm.version = 1.5.0_15-b04
    2009-05-28 14:33:26.724 SEVERE: java.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\jdk\jre
    2009-05-28 14:33:26.724 SEVERE: catalina.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat
    2009-05-28 14:33:26.724 SEVERE: java.user = null
    2009-05-28 14:33:26.724 SEVERE: user.language = en
    2009-05-28 14:33:26.724 SEVERE: user.country = US
    2009-05-28 14:33:26.724 SEVERE: scm.server.version = 11.0.4014.26
    2009-05-28 14:33:29.253 SEVERE: ================== StartClientTransport ===================
    2009-05-28 14:33:29.363 SEVERE: Unknown Exception in: com.sygate.scm.server.servlet.StartupServlet
    java.lang.Exception: HTTP 403 Forbidden, 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)

    Thanks,
    Rudy
     



  • 13.  RE: Cannot login to SEP Manager - Failed to connect to server

    Posted May 28, 2009 05:43 PM

    Guys..thanks for the response...and sorry for the delay.  Away on other projects for some time.

    Ok.  I see the following:

    Application log on the Windows 2003 machine shows: 
    Event ID: 4096
    Source: semsrv
    The Java Virtual Machine has exited with a code of -1, the service is being stopped.

    I also see that Symantec Endpoint Protection Manager stops immediately even if manually started.

    I've checked a working server and installed the same version of Java VM - no luck.

    I've gone through Grant's recommendations and ESS & Breas suggestions - no go.

    Logs below:
    SCM-server-0.log
    2009-05-28 14:33:26.724 SEVERE: ================== Server Environment ===================
    2009-05-28 14:33:26.724 SEVERE: os.name = Windows 2003
    2009-05-28 14:33:26.724 SEVERE: os.version = 5.2
    2009-05-28 14:33:26.724 SEVERE: os.arch = x86
    2009-05-28 14:33:26.724 SEVERE: java.version = 1.5.0_15
    2009-05-28 14:33:26.724 SEVERE: java.vendor = Sun Microsystems Inc.
    2009-05-28 14:33:26.724 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
    2009-05-28 14:33:26.724 SEVERE: java.vm.version = 1.5.0_15-b04
    2009-05-28 14:33:26.724 SEVERE: java.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\jdk\jre
    2009-05-28 14:33:26.724 SEVERE: catalina.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat
    2009-05-28 14:33:26.724 SEVERE: java.user = null
    2009-05-28 14:33:26.724 SEVERE: user.language = en
    2009-05-28 14:33:26.724 SEVERE: user.country = US
    2009-05-28 14:33:26.724 SEVERE: scm.server.version = 11.0.4014.26
    2009-05-28 14:33:29.253 SEVERE: ================== StartClientTransport ===================
    2009-05-28 14:33:29.363 SEVERE: Unknown Exception in: com.sygate.scm.server.servlet.StartupServlet
    java.lang.Exception: HTTP 403 Forbidden, 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)

    Thanks,
    Rudy
     



  • 14.  RE: Cannot login to SEP Manager - Failed to connect to server

    Posted May 28, 2009 09:41 PM
    Have you test the ODBC DSN link?


  • 15.  RE: Cannot login to SEP Manager - Failed to connect to server

    Posted May 28, 2009 10:09 PM
    On mine, yes I tested it and it was successful. Although when my problems start the username and password et blown out and I need to put back in the username (DBA) and password (same as login password) then it tests successful but I still cannot login to the management console. I don't get it.


  • 16.  RE: Cannot login to SEP Manager - Failed to connect to server

    Posted May 28, 2009 10:58 PM
    Please post LOgs

    C:\Program files\Symantec\SEPM\Tomcat\log\scm-server-0.log
    C:\Program files\Symantec\SEPM\Tomcat\log\catalina.out.




  • 17.  RE: Cannot login to SEP Manager - Failed to connect to server

    Posted May 29, 2009 12:39 AM
    I'm having what seems to be the same problem...  Here are a few logs that looked interesting, possibly relevant.  This server is at Java 6 13.  Another server I maintain is at Java 6 and works.  Last week I found that newer Java releases break Cisco's firewall management tools, ASDM.

    catalina.out

    May 27, 2009 7:56:43 AM org.apache.coyote.http11.Http11BaseProtocol init
    INFO: Initializing Coyote HTTP/1.1 on http-9090
    May 27, 2009 7:56:44 AM 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 C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\etc\license
    May 27, 2009 7:56:45 AM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: ================== Server Environment ===================
    May 27, 2009 7:56:45 AM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: os.name = Windows 2003
    May 27, 2009 7:56:45 AM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: os.version = 5.2
    May 27, 2009 7:56:45 AM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: os.arch = x86
    May 27, 2009 7:56:45 AM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: java.version = 1.5.0_14
    May 27, 2009 7:56:45 AM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: java.vendor = Sun Microsystems Inc.
    May 27, 2009 7:56:45 AM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: java.vm.name = Java HotSpot(TM) Server VM
    May 27, 2009 7:56:45 AM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: java.vm.version = 1.5.0_14-b03
    May 27, 2009 7:56:45 AM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: java.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\jdk\jre
    May 27, 2009 7:56:45 AM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: catalina.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat
    May 27, 2009 7:56:45 AM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: java.user = null
    May 27, 2009 7:56:45 AM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: user.language = en
    May 27, 2009 7:56:45 AM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: user.country = US
    May 27, 2009 7:56:45 AM com.sygate.scm.server.util.ServerLogger writeHeader
    SEVERE: scm.server.version = 11.0.2000.1567


    dbvalidator.log

    2009-05-18 22:51:19.953 INFO: *********************************************
    2009-05-18 22:51:19.953 INFO: Following ids are not present in the database.
    2009-05-18 22:51:19.969 INFO: *********************************************
    2009-05-18 22:51:19.969 INFO: Link is broken for [1] target ids :
    2009-05-18 22:51:19.969 INFO: TargetId:[1E06185CC0A8010201AB7626851D5C0E] TargetType:
    [FwFirewallPolicy] ObjectTypeName:[ObjReference] ParentObjectTypeName :[SuspendedItem]
    Parent's TopLevelObject's GUID:[1CBD3151C0A80102014E3BB0043CEDD5]
    2009-05-18 22:51:19.969 INFO: *********************************************
    2009-05-18 22:51:19.969 INFO: Link is broken for [0] physical file ids :
    2009-05-18 22:51:19.969 INFO: *********************************************
    2009-05-18 22:51:19.985 INFO: Database validation failed.
    2009-05-18 22:51:19.985 INFO: Finished.

    httperr118.log

    2009-05-29 02:44:13 127.0.0.1 30626 127.0.0.1 8443 HTTP/0.0 Invalid - 400 - Verb -


    Main-0.log

    2009-05-18 22:51:02.641 SEVERE: ================== Server Environment ===================
    2009-05-18 22:51:02.641 SEVERE: os.name = Windows 2003
    2009-05-18 22:51:02.641 SEVERE: os.version = 5.2
    2009-05-18 22:51:02.641 SEVERE: os.arch = x86
    2009-05-18 22:51:02.641 SEVERE: java.version = 1.5.0_14
    2009-05-18 22:51:02.641 SEVERE: java.vendor = Sun Microsystems Inc.
    2009-05-18 22:51:02.641 SEVERE: java.vm.name = Java HotSpot(TM) Client VM
    2009-05-18 22:51:02.641 SEVERE: java.vm.version = 1.5.0_14-b03
    2009-05-18 22:51:02.641 SEVERE: java.home = C:\Program Files\Symantec\Symantec Endpoint
    Protection Manager\jdk\jre
    2009-05-18 22:51:02.641 SEVERE: catalina.home = C:\Program Files\Symantec\Symantec
    Endpoint Protection Manager\Tools\..\tomcat
    2009-05-18 22:51:02.641 SEVERE: java.user = null
    2009-05-18 22:51:02.641 SEVERE: user.language = en
    2009-05-18 22:51:02.641 SEVERE: user.country = US
    2009-05-18 22:51:02.641 SEVERE: scm.server.version = 11.0.2000.1567

    scm-server-1.log


    2009-05-27 07:56:45.910 SEVERE: ================== Server Environment ===================
    2009-05-27 07:56:45.910 SEVERE: os.name = Windows 2003
    2009-05-27 07:56:45.910 SEVERE: os.version = 5.2
    2009-05-27 07:56:45.910 SEVERE: os.arch = x86
    2009-05-27 07:56:45.910 SEVERE: java.version = 1.5.0_14
    2009-05-27 07:56:45.910 SEVERE: java.vendor = Sun Microsystems Inc.
    2009-05-27 07:56:45.910 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
    2009-05-27 07:56:45.910 SEVERE: java.vm.version = 1.5.0_14-b03
    2009-05-27 07:56:45.910 SEVERE: java.home = C:\Program Files\Symantec\Symantec Endpoint
    Protection Manager\jdk\jre
    2009-05-27 07:56:45.910 SEVERE: catalina.home = C:\Program Files\Symantec\Symantec
    Endpoint Protection Manager\tomcat
    2009-05-27 07:56:45.910 SEVERE: java.user = null
    2009-05-27 07:56:45.910 SEVERE: user.language = en
    2009-05-27 07:56:45.910 SEVERE: user.country = US
    2009-05-27 07:56:45.910 SEVERE: scm.server.version = 11.0.2000.1567
    2009-05-27 07:56:48.972 SEVERE: ================== StartClientTransport
    ===================
    2009-05-27 07:56:49.066 SEVERE: Unknown Exception in:
    com.sygate.scm.server.servlet.StartupServlet
    java.lang.Exception: HTTP 400 Bad Request, URL: http://localhost/secars/secars.dll?
    action=34
    at com.sygate.scm.common.communicate.Communicator.getRequestInputStream
    (Communicator.java:548)
    at com.sygate.scm.server.util.ClientTransportHelper.startClientTransport
    (ClientTransportHelper.java:72)
    at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:99)
    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:569)
    at com.sygate.scm.server.util.ClientTransportHelper.startClientTransport
    (ClientTransportHelper.java:72)
    at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:99)
    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)


  • 18.  RE: Cannot login to SEP Manager - Failed to connect to server

    Posted May 29, 2009 01:08 AM
    2009-05-18 22:51:19.985 INFO: Database validation failed.

    If database validation is failing then i think i am getting out of ideas.that too if its Embedded database.
    If possible try re-install.

    HTTP 400 Bad Request, URL: http://localhost/secars/secars.dll?
    Before that try un-installing the latest Java update and repair SEPM.


  • 19.  RE: Cannot login to SEP Manager - Failed to connect to server

    Posted May 29, 2009 01:10 AM
    HTTP 403 Forbidden, URL: http://localhost:8014/secars/secars.dll?action=34

    This is just an permission issue so following the JAVA -1 documents should resolve your issue however if you can enable IIS Logging on Secars and port the IIS log that would be more helpful.


  • 20.  RE: Cannot login to SEP Manager - Failed to connect to server

    Posted May 29, 2009 02:32 AM
    The SEP Manager service dies within seconds of starting it.  This is the message in the Event Viewer:

    "The Java Virtual Machine has exited with a code of -1, the service is being stopped."



  • 21.  RE: Cannot login to SEP Manager - Failed to connect to server

    Posted May 29, 2009 04:58 AM
    Hi Larry,

    If in scm-server-0.log you have HTT P 400 than you can try  the following link

    Troubleshooting for Symantec Endpoint Protection Manager (SEPM) 11.x error "HTTP 400 - bad request"
    http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008041811532648

    And in case of HTTP 403 try doing a repair on SEPM console and check the status of Symantec endpoint protection manager service. In case it is again stopping please check the scm-server-0.log and paste it in here


  • 22.  RE: Cannot login to SEP Manager - Failed to connect to server

    Posted May 29, 2009 05:24 AM
    What's the size of the CATALINA.OUT file?

    Is it OVER 3 KB?




  • 23.  RE: Cannot login to SEP Manager - Failed to connect to server

    Posted May 29, 2009 10:17 AM
    catalina.out log file size:

    File properties reports...

    Size: 2.22 KB (2,283 bytes)
    Size on disk: 4.00 KB (4,096 bytes)


  • 24.  RE: Cannot login to SEP Manager - Failed to connect to server

    Posted May 29, 2009 10:48 AM
    Can you please paste catalina.out log file.

    ...Barkha


  • 25.  RE: Cannot login to SEP Manager - Failed to connect to server
    Best Answer

    Posted May 29, 2009 11:50 AM
    I completely removed SEPM and reinstalled it.  I can login now.

    Thanks for the help!

    The catalina.out logfile was cleared by the reinstall or I would post it....



  • 26.  RE: Cannot login to SEP Manager - Failed to connect to server

    Posted Aug 25, 2009 11:23 AM
    I ended up reinstalling the Operating System.  Everything went through fine after that.  Not sure what could have been amiss with the first OS install.
    Thanks for everyone's input.
    Regards,
    Rudy


  • 27.  RE: Cannot login to SEP Manager - Failed to connect to server

    Posted Feb 14, 2010 12:59 AM
    I need to get these working on the same server

    I have a sbs 2003 server running with exchange configured.

    I had purchased a new server to run the Blackberry professional server and symantec enterprise on

    I have the problem above.... how can I get them to play nice with each other, is there no way of adding another instance of JAVA or something
    Maybe force them to share, change something ????




  • 28.  RE: Cannot login to SEP Manager - Failed to connect to server

    Posted Feb 15, 2010 01:09 AM
    Pls create a separate thread for your problem.Sine this is an old post most of the people will ignore it. 


  • 29.  RE: Cannot login to SEP Manager - Failed to connect to server

    Posted Feb 15, 2010 03:35 AM
    IS this really a solution ?????
    This issue would have been ressolved with troubleshooting, there was no point of uninstalling and re-installing it.


  • 30.  RE: Cannot login to SEP Manager - Failed to connect to server

    Posted Feb 19, 2010 08:25 AM

    I suffered through nearly 3 weeks of trying to install Symantec Endpoint Protection Manager and trying every possible "solution" to be found.
    I finally found the solution to be an issue with security permissions.
    Make the following changes below and you should be able to proceed without any problems.

    Add the following user accounts with the following permissions to the C:\Program Files\Symantec directory
     * Authenticated Users - FULL CONTROL
     * IUSR_<Servername> - Read Execute
     * IWAM_<Servername> - Read Execute
    Reference: http://www.symantec.com/connect/forums/java-virtual-machine-has-exited-code-1-service-being-stopped


    Remove the IUSR_<Servername> from the Guests Account Group and add it to the Users Group
    Reference: http://www.symantec.com/connect/forums/failed-connect-server-3