Good day,

I am trying to log into a SEP Manager Console on a WIndows 2008 Server. This fails. I can see in 'Services' that the SEP Manager Service is not running.

I can start the service, but the service stops as soon as I want to login wit the Console.

This Event is written into the Event Log:

Log Name:      Application
Source:        semsrv
Date:          2-1-2014 15:38:39
Event ID:      4098
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      TBMFS02S.ka.tijdsbeeldmedia.nl
Description:
The semsrv service failed to start.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="semsrv" />
    <EventID Qualifiers="49152">4098</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-01-02T14:38:39.000Z" />
    <EventRecordID>736843</EventRecordID>
    <Channel>Application</Channel>
    <Computer>TBMFS02S.ka.tijdsbeeldmedia.nl</Computer>
    <Security />
  </System>
  <EventData>
    <Data>semsrv</Data>
  </EventData>
</Event>

Below is what I see in the scm.server.log:

2014-01-02 15:31:20.851 SEVERE: ================== Server Environment ===================
2014-01-02 15:31:20.851 SEVERE: os.name = Windows Server 2008
2014-01-02 15:31:20.851 SEVERE: os.version = 6.0
2014-01-02 15:31:20.851 SEVERE: os.arch = x86
2014-01-02 15:31:20.851 SEVERE: java.version = 1.6.0_14
2014-01-02 15:31:20.851 SEVERE: java.vendor = Sun Microsystems Inc.
2014-01-02 15:31:20.867 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
2014-01-02 15:31:20.867 SEVERE: java.vm.version = 14.0-b16
2014-01-02 15:31:20.867 SEVERE: java.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\jdk\jre
2014-01-02 15:31:20.867 SEVERE: catalina.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat
2014-01-02 15:31:20.867 SEVERE: java.user = null
2014-01-02 15:31:20.867 SEVERE: user.language = en
2014-01-02 15:31:20.867 SEVERE: user.country = US
2014-01-02 15:31:20.867 SEVERE: scm.server.version = 11.0.6005.562
2014-01-02 15:31:26.639 SEVERE: ================== StartClientTransport ===================
2014-01-02 15:31:27.700 SEVERE: 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.SocksSocketImpl.connect(SocksSocketImpl.java:366)
    at java.net.Socket.connect(Socket.java:519)
    at java.net.Socket.connect(Socket.java:469)
    at sun.net.NetworkClient.doConnect(NetworkClient.java:163)
    at sun.net.www.http.HttpClient.openServer(HttpClient.java:394)
    at sun.net.www.http.HttpClient.openServer(HttpClient.java:529)
    at sun.net.www.http.HttpClient.<init>(HttpClient.java:233)
    at sun.net.www.http.HttpClient.New(HttpClient.java:306)
    at sun.net.www.http.HttpClient.New(HttpClient.java:323)
    at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:852)
    at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:793)
    at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:718)
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1041)
    at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:373)
    at com.sygate.scm.common.communicate.Communicator.getRequestInputStream(Communicator.java:612)
    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: 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:645)
    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)
 

Anyone with any Ideas what could be the issue here?

I have done a repair of the Console, without any succes.I haven't rebooted the server (I cannot do that during production hours).

Regards, Marvin

Try this

"Failed to connect to the server" error when logging on to the Symantec Endpoint Protection Manager.

Have a look at the solution provided in this thread:

https://www-secure.symantec.com/connect/forums/sepm-failed-connect-server-service-starts-then-stops

...and then as well the following KB:

Symantec Endpoint Protection Manager 11.x Communication Troubleshooting

Did you try by recongure management server wizard? If no, try once.....

Hello,

Check this Thread with similar issue: https://www-secure.symantec.com/connect/forums/sepm-will-not-login

Hope that helps!!

have you checked the odbc connection?

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

is SEPM installed on custom website

check the port in IIS and also in conf.properties file, if its on custom you need to add

scm.iis.http.port=Your custom port

since you are running 11.0.6XXX a recent update to java might cause this issue as well

were you able to login to console earlier?

are you using SQL as DB?

Found error code

Experiencing network issues, contact your system administrator. ErrorCode: 0x80020000

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

https://www-secure.symantec.com/connect/forums/failed-connect-server-errorcode-0x80020000

Hi,

Please check above comments,If comments not help please follow Disaster Recovery process or first you can contact symantec support for more help.

Symantec Endpoint Protection 11.x: Best Practices for Disaster Recovery with the Symantec Endpoint Protection Manager

Symantec Endpoint Protection 12.1: Best Practices for Disaster Recovery with the Symantec Endpoint Protection Manager

Hello,

before doing drastic things like a Disaster Recovery, please attach (see the option at the end of the page) the file catalina.out to this thread or have a call with Tech Support for a deeper investigation. Maybe it is just a port conflict.

Are you sure the SEPM service does not stop even before you try to log in to the console? Hit F5 to confirm it, please.

I haven't rebooted the server (I cannot do that during production hours).

Are you then running other critical applications on that same server such as web servers, databases, etc.?

Hi Pete,

Yes, the console used to work before all this started. Symentec Uses SQL Server 2005 as the database.

Regards, Marvin

Thanks all for helping me out! I hav not yet found a solution to this problem.

To answer Beppe's question: This server is also an Exchange Server 2010 and a BackupExec Server 2010.

I also found out that the SEPM service quits immediately after being started (so my starting the console has nothing to do with the SEPM service).

I have included the contents of catalina.out:

Jan 8, 2014 2:41:17 PM org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-9090
Jan 8, 2014 2:41:18 PM org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8443
Starting service SCM
Apache Tomcat/4.1.39
Catalina.start: LifecycleException:  Context startup failed due to previous errors
LifecycleException:  Context startup failed due to previous errors
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:3701)
    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)
Stopping service SCM
Catalina.stop: LifecycleException:  Coyote connector has not been started
LifecycleException:  Coyote connector has not been started
    at org.apache.coyote.tomcat4.CoyoteConnector.stop(CoyoteConnector.java:1382)
    at org.apache.catalina.core.StandardService.stop(StandardService.java:499)
    at org.apache.catalina.core.StandardServer.stop(StandardServer.java:2248)
    at org.apache.catalina.startup.Catalina.start(Catalina.java:515)
    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)
 

Hi,

Can you post catalina.out log ?

Log available here

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

Hi,

Thank you for posting in Symantec community.

I would be glad to answer your query.

1) Check if  ODBC is missing in Administrative Tools? Configure the ODBC connection with the correct database password,

2) Restart IIS service

Repair the SEPM with the help of original setup files if you have or can directly repair through add/remove programs.

If these steps couldn't help then please attach scm-server-0.log and catalina.out log file. These logs provides fruitful information to troubleshoot SEPM login issue.

I would also say that disaster recovery can be a last option.

Hello,

it is time to contact the phone support.

Hello Chetan,

Ik will check this and get back to you.

Regards,

Hi Beppe,

I will first try Chetan's suggestion, if that doesn't lead to a solution I will contact Tech Support.

Regards,

if it stops immediately it should be port issue , Did you check the netstat-ano

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

Is there any update?

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you

Good day all,

Apologies for the long delay! The solution for this issue has not been found yet, but may be a moot issue because of licensing issues. We may be forced to install a different version of the BackupExec application (Small Business in stead of Enterprise).

I will therefore close this call. Thanks to all for your time and contributions!

Regards, Marvin.