Symantec Endpoint Protection Manager Service starts then stops, with Java error in Event Viewer

Here is the output from Catalina.out:

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

I just disabled SSL on the default web site (and all related sites) as well, and now the Symantec Endpoint Protection Manager service seems to be working properly.

I have been a hardcore Symantec Enterprise/Corporate software fan for many years, too, but Symante Endpoint really does suck.  I think that it's sad that they had to take a great product and mangle it as badly as they have...

Yes. I was a die hard symantec corporate edition up to 10.x. Then came SEP11. What a disaster. I followed the Syamtec documentation to the letter and it blew out my client's network. The solution they offered was a patch whch basicaly downgraded SEP 11 to 10.x functionality. Thats just the beginning. I began referring to their product on their forums as their paid-beta. It was clear they did little testing. And any solution they offered after that...just as little testing. It's now fairly stable except for the odd IIS outages about once or twice a month (much less frequent the more aspects I disable of SEP11). Bottom line... Symantec all but says the only solution to their screwup is another AV vendor. Enter Eset. Love it. moving to it. Eset.com. Check it out. Kiss Symancrap goodbye.

I found two issues different from above that solved it for me
IIS Folder Permissions on the EPP Web site was set to Basic only, adding Inntergrated permissions fixed the issue
Also control panel ODBC, the username and password for the database where black, the default user name seems to be DBA and password is what you enter on install

Can you specify how you corrected the EPP permissions?  Is it the SECARS and the SECREG pages under the default web site?  Also specifically what did you change?  Sorry, but this has been frustrating me for months now, and Symantec has been no help.

OK we were having the same issue.  We tracked it down to a conflict of port allocation by TomCat.

Found that the service - Symantec Endpoint Protection Manager - would stop about 20 seconds after starting and an error in the event log as listed in this thread.

Searched through the logs at:
Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs

looked at catalina.out and found the message below:
StandardServer.await: create[8005]: java.net.BindException: Address already in use: JVM_Bind

Following advise from a Symantec KB:

http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/e77298b64281e447ca25736800837709?OpenDocument

This stated to:

Cause:
This error, along with any similar error referencing a different port, indicates that another application or process has already been bound to this port. For errors relating to port 8005 or 9090, the conflict is probably the result of another application running it's own Tomcat server on the same machine. Some products that use Symantec Endpoint Protection 11.0 Ports: IM Manager - Port 9090; Sonicwall ViewPoint - Port 8005; Symantec BrightMail AntiSpam 6.0.x Control Center - Port 8005; Symantec Mail Security for SMTP 5.0 Control Center - Port 8005.

Solution:
In order to resolve this issue, you must either change the port that the conflicting application runs on, or alter the Tomcat port.

To alter the Tomcat port, following these steps:

Ensure that the Symantec Endpoint Protection Manager service is stopped.
Right-click the server.xml file and click Edit to modify the file:
C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\conf\server.xml)

For conflicts with port 8005, change the port to another unused port:
port="8005"

For conflicts with port 9090, change the port to another unused port:
port="9090"

Save the changes to the "server.xml" file.
Start the Symantec Endpoint Protection Manager service.
Attempt to login to the Symantec Endpoint Protection Manager.

Restarted the service and was able to logon.

Changing the SEP website permissions to integrated and basic also solved it for me.

I tried all the suggestions, but Scablifter's port change on the server.xml worked for me.  I just increased each by one.  This was on version 11 mr4 mp2.

It appears that installations of VMware may actually also conflict. Definitely try following the incrementing ports (8005 and 9090) instructions above if you're running a VMWare server on the same machine!

We had this exact same problem on our server. SEPM was using the embedded database and was installed on a DC (Bad Ju-Ju I know, but we told the boss that and she said to do it anyways). We went through all the different steps INCLUDING a reinstall of SEPM and it didn't fix it.  Then we restarted the server. Problem fixed.  The problem had something to do with some internal security issues. Restarting the server renewed whatever security certificates were needed for the server to talk to itself. I do know that the MS Firewall Client for ISA we were running had a part in it.  A third party service provider performs firewall, outlook web access, and other network services for us and the problem didn't start until they made some changes to their network.

The Tomcat server ports were the problem for me, having VMWare installed as well as SEPM.  Changing ports in the XML file to 8006 and 9091 solved my issue.

God, this site is great. Disable SSL worked for me! I'm not a fan of all these web based software products these days. Still very buggy and hard to troubleshoot!