Video Screencast Help

Symantec Endpoint Protection Manager service stops with a Java -1 error in the event log

Created: 18 Feb 2008 • Updated: 21 May 2010 | 19 comments
Im trying to install Symantec Endpoint Protection Manager on a windows 2003 R2 SP2 box with ISA 2006 and Symantec Mail Security for SMTP currently on it.
 
Now after installing protection manager with a embedded database the service keeps stopping with "

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

I've tried the following

  • Changed the ports to 5555 (something random that nothing else is using)
  • Its not running Java 1.6
  • Checked IIS and made sure all the settings were correct as to their guide
  • Opened up ODBC and made sure connection successful comes up when clicking test connection

Has anyone else come up with this problem and solved it?

Hope someone can help

Thanks

 

Comments 19 CommentsJump to latest comment

Paulm17781's picture

I'm having the same issue. I've tried on two seperate servers (same domain) and neither work.

here is catalina.out

********************************************catalina.out****************************************************
19-Feb-2008 13:31:54 org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-9090
19-Feb-2008 13:31:55 org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8443
Starting service SCM
Apache Tomcat/4.1.31
Has valid SAV license
Info>> No SNAC license file in C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\etc\license
19-Feb-2008 13:31:56 com.sygate.scm.server.util.ServerLogger writeHeader
SEVERE: ================== Server Environment ===================
19-Feb-2008 13:31:56 com.sygate.scm.server.util.ServerLogger writeHeader
SEVERE: os.name = Windows 2003
19-Feb-2008 13:31:56 com.sygate.scm.server.util.ServerLogger writeHeader
SEVERE: os.version = 5.2
19-Feb-2008 13:31:56 com.sygate.scm.server.util.ServerLogger writeHeader
SEVERE: os.arch = x86
19-Feb-2008 13:31:56 com.sygate.scm.server.util.ServerLogger writeHeader
SEVERE: java.version = 1.5.0_14
19-Feb-2008 13:31:56 com.sygate.scm.server.util.ServerLogger writeHeader
SEVERE: java.vendor = Sun Microsystems Inc.
19-Feb-2008 13:31:56 com.sygate.scm.server.util.ServerLogger writeHeader
SEVERE: java.vm.name = Java HotSpot(TM) Server VM
19-Feb-2008 13:31:56 com.sygate.scm.server.util.ServerLogger writeHeader
SEVERE: java.vm.version = 1.5.0_14-b03
19-Feb-2008 13:31:56 com.sygate.scm.server.util.ServerLogger writeHeader
SEVERE: java.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\jdk\jre
19-Feb-2008 13:31:56 com.sygate.scm.server.util.ServerLogger writeHeader
SEVERE: catalina.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat
19-Feb-2008 13:31:56 com.sygate.scm.server.util.ServerLogger writeHeader
SEVERE: java.user = null
19-Feb-2008 13:31:56 com.sygate.scm.server.util.ServerLogger writeHeader
SEVERE: user.language = en
19-Feb-2008 13:31:56 com.sygate.scm.server.util.ServerLogger writeHeader
SEVERE: user.country = IE
19-Feb-2008 13:31:56 com.sygate.scm.server.util.ServerLogger writeHeader
SEVERE: scm.server.version = 11.0.1000.1375
**********************************************************************************************

and here is scm-server-0.log

************************************scm-server-0.log******************************************

2008-02-19 13:31:56.468 SEVERE: ================== Server Environment ===================
2008-02-19 13:31:56.468 SEVERE: os.name = Windows 2003
2008-02-19 13:31:56.468 SEVERE: os.version = 5.2
2008-02-19 13:31:56.468 SEVERE: os.arch = x86
2008-02-19 13:31:56.468 SEVERE: java.version = 1.5.0_14
2008-02-19 13:31:56.468 SEVERE: java.vendor = Sun Microsystems Inc.
2008-02-19 13:31:56.468 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
2008-02-19 13:31:56.484 SEVERE: java.vm.version = 1.5.0_14-b03
2008-02-19 13:31:56.484 SEVERE: java.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\jdk\jre
2008-02-19 13:31:56.484 SEVERE: catalina.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat
2008-02-19 13:31:56.484 SEVERE: java.user = null
2008-02-19 13:31:56.484 SEVERE: user.language = en
2008-02-19 13:31:56.484 SEVERE: user.country = IE
2008-02-19 13:31:56.484 SEVERE: scm.server.version = 11.0.1000.1375
2008-02-19 13:31:56.515 INFO: Server startup
2008-02-19 13:31:58.765 SEVERE: ================== StartClientTransport ===================
2008-02-19 13:31:58.859 SEVERE: Unknown Exception in: com.sygate.scm.server.servlet.StartupServlet
java.lang.Exception: HTTP 500 Internal Server Error, URL: http://localhost/secars/secars.dll?action=34
    at com.sygate.scm.common.communicate.Communicator.getRequestInputStreamEx(Communicator.java:513)
    at com.sygate.scm.common.communicate.Communicator.getRequestInputStream(Communicator.java:479)
    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:888)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:776)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3363)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:3586)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1141)
    at org.apache.catalina.core.StandardHost.start(StandardHost.java:707)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1141)
    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:316)
    at org.apache.catalina.core.StandardService.start(StandardService.java:450)
    at org.apache.catalina.core.StandardServer.start(StandardServer.java:2143)
    at org.apache.catalina.startup.Catalina.start(Catalina.java:463)
    at org.apache.catalina.startup.Catalina.execute(Catalina.java:350)
    at org.apache.catalina.startup.Catalina.process(Catalina.java:129)
    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:156)
com.sygate.scm.common.communicate.CommunicationException: Unexpected server error. ErrorCode: 0x10010000
    at com.sygate.scm.common.communicate.Communicator.getRequestInputStreamEx(Communicator.java:532)
    at com.sygate.scm.common.communicate.Communicator.getRequestInputStream(Communicator.java:479)
    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:888)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:776)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3363)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:3586)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1141)
    at org.apache.catalina.core.StandardHost.start(StandardHost.java:707)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1141)
    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:316)
    at org.apache.catalina.core.StandardService.start(StandardService.java:450)
    at org.apache.catalina.core.StandardServer.start(StandardServer.java:2143)
    at org.apache.catalina.startup.Catalina.start(Catalina.java:463)
    at org.apache.catalina.startup.Catalina.execute(Catalina.java:350)
    at org.apache.catalina.startup.Catalina.process(Catalina.java:129)
    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:156)

*********************************************************************************************************

Please help.

Thanks,
Paul

Mike T's picture
Look in the forums .. many have had this issue.  You may find a nugget or two to help you. For me, it took 40 hours of tweaking, several emails with symantec support, and then finally giving up and rebuilding the machine from scratch.  It worked then.  Others have had luck with changing the ports and uninstalling Java (which you already tried .. but make sure another version of Java isn't buried in your machione somewhere).  Another person made it work by switching some options in SQL express.
 
It is frustrating that the installer program doesn't do a better job of checking that everything it needs is there. 
 
Paulm17781's picture

Hi Mike,

thanks for the reply. I've done a couple of rebuilds. Tried several suggestions here and nothing is working.

It is frustrating that the program doesn't seem to work well at all. I used to like Symanted but since NAV 2006 I had gone off them. I had reservations using this product and it would seem I am right.

I would expect someone from Symantec would actually post something.


Mike T's picture
Yea, I am still in test mode after 30+ days.   My rebuild was like this: fdisk, XPSP2, full install of IIS, all service packs, the SEPM using internal database.  Then it worked.  Since then I have added more to the machine, and so far, it still lets me log in.  Of course, I have many other issues, but the login works.  :)
 
Mike T's picture
And when you rebuilt the machine (as I said above, fdisk then OS), you installed SEPM before anything else (other than OS patches)?
Rob374's picture
Paulm17781  im gald someone else has the same problem
 
What else do you have on your server? 
 
I tried a clean windows 2003 test server and it installs / logs on fine - grrrrrr - so it must be something on that server causing my problem :( - So wonder what is it?!
 
 



Message Edited by Rob374 on 02-19-2008 11:53 AM

Paulm17781's picture

Hi Rob,

I've tried it on two servers, one is my PDC and one is my Excahgne server. It fails with the same error on both.

Not a peep from Symantec as yet. I think I will have to start actively campaigning AGAINST using Symantec products again.

I've tried everything I can see here to fix it, nothing. What sort of reputable company releases software that people consistantly have trouble with?

Paul

Rob374's picture
Paulm are you trying MR1? I gave it a go today and ive still got the same problem - the SEPM service still stops a few seconds after starting it :S
Paulm17781's picture

Hi Rob,

I got mine working. I disabled the Exchange web page, gave Symantec the custom one and re-enabled the excahgne page. The software is still pretty bad, I put it on my PDC where it blocked the DHCP clients...

Anyway, with no help from Symantec and a lot of hair pulling, it can be installed.

KalmerK's picture

Manager won't stay started and only the dbsrv9.exe is listening to 2638

It's worth checking the secars, secreg and Reporting properties if the Default Web Site is used in IIS.

Directory Security / Authentication and ...  - should be set to enable Anonymous Access
Directory Security / Secure Communications - uncheck SSL use (if this is not required by you)

After changing these values I could start Symantec Endpoint Protection Manager service and  ports 8005, 8443, 9090 showed up listening with

netstat -ao | find /i "listening"

and I was finally able to use SEPM Manager

Amir Mahook's picture

Hi all,

 

This is “IIS problem” if you check under application pools you will find the service are disable and if you enable it, it will re-disable.

 

You can keep it up If you change the application pool identity to be local service not network service. Try…. Then try to reinstall Symantec and see

 

But again if you solve network service problem with IIS then SEPM will work with you

 

ByteGeek's picture
I am posting in hopes that others might find this information useful.
 
I am running Server 2003 R2 x64 on a small Dell PESC430. Had the problem installing and then the service exiting with the Java VM error. After looking at several threads this is what I did.
 
Uninstalled SEPM, all Java Runtime versions, and IIS. I didn't have any other sites configured in IIS, so it was convenient for me to do so.
 
Reinstalled IIS, Java 1.6 update 4, SEPM with the embedded database and all defaults except installation location. ( The files for this install are huge, so I installed to a large data partition rather than my OS location. I also recommend moving your IIS logs off of your OS partition and compressing them as they grow quickly once SEPM is running.)
 
I was about to reload the machine before trying this, but it is all working well now. Hope this helps save someone else some time.
 
 
stully's picture
Rob,
 
Did you get this to work?  I too have an ISA 2006 (and  a ISA 2004), have installed it so many times, I've lost count.  Even worked with Symantec tech support, still not working.  Would really appreciate it if you found the secret to installing it on a ISA 2006.
 
Thanks
etsai714's picture
Good find.  I had the same issue of the SEPM service stopping upon start.  I am running Windows 2003 SBS.  The root cause was that I had the default web site configured to require SSL certificates (for Exchange) - and when I used  the default web site for SEPM, the websites were configured that way as well.  So turning off SSL requirement for all the Symantec components allwoed the SEPM service to start, and consequently the console to run.  I believe if you disable the requirement at the default web site would do the trick as well (or rebuilding IIS)
 
 
Regards,
Ed
 
 
 
Paulm17781's picture

I still say it is atrocious that the software doesn't even check these things while installing. How hard would it be to print a list of potential problems during install.

I'm having more problems with Brightmail now but Symantec don't even seem to support that!

stully's picture
Thanks Ed, but disabling SSL didn't do it either.  But I'd be very interested hearing any other special things you did to get it to run on your SBS server, especially if your version is using ISA 2004 or 2006
Comperiotech's picture
SBS 2003 R2 (No ISA Server, everything else installed and patched).
SEP 11.0 MR2
 
I installed SEPM using the default website and a custom location (F:\Symantec\Symantec Endpoint Protection Manager). The installation succeeded, but the server configuration/deployment wizard failed.
 
When trying to connect to SEPM, the SEPM server would fail with a red dot in the Application log regarding Java -1.
 
Step 1: I enabled logging (scm.log.loglevel=fine in F:\Symantec\Symantec Endpoint Protection Manager\tomcat\etc\conf.properties) on the SEPM and found the "HTTP 401 Unauthorized" error from the Tomcat server in the log file F:\Symantec\Symantec Endpoint Protection Manager\tomcat\logs\scm-server-0.log.
 
Step 2: I checked the permissions for the folder F:\Symantec. I added the Builtin Group "Users" (not "Domain Users") with Read & Execute, List Folder Contents, and Read permissions. (Clicked on advanced and selected "Replace permissions.." and clicked OK). (I recommend adding this folder and setting the permissions before installation).
 
Step 3: I then checked the port status (see this link for steps). Nothing was blocking.
 
Step 4: I then went through and checked the setup of IIS.
4a. Made sure under the Properties for the Default website, the IP address was listed as "All Unassigned"
4b. Five Symantec Applications were installed under the Default website. They are: Client Packages, Content, Reporting, secars, and secreg. For each of the Applications, I checked the following (under Properties, Directory Security)
4b1. Authentication and Access Control: Enable Anonymous Access was checked and the IUSR_(servername) was selected for each. (Some posts have claimed you need to remove all authentication types except anonymous, but mine is working with it.
 
4b2. IP Address and Domain name restrictions: Selected "By default, all computers will be granted access". Then removed all of the exceptions. This is what got me.
 
4b3. Secure communications: made sure Require SSL was not checked.
 
Step 5: Restarted IIS (Start->Run->CMD. At the command prompt type IISRESET <ENTER>. After the restart, restart the SEPM service).
 
I was then able to run the server configuration wizard.
 
(Be sure to undo the logging in Step 1)
 
Hope this helps.

 



Message Edited by Comperiotech on 05-06-2008 11:15 AM

mschumacher69's picture

Mike T, you said "Another person made it work by switching some options in SQL express"

I started having this java -1 error and http 500 internal server error after I installed sql express 2005! What options should i switch in sql express to fix my problem??

 

Thanks