I found an old thread titled "The Java Virtual Machine has exited with a code of -1, the service is being stopped." but it was closed and locked. So I'm posting this new info.
Using SEP 12.1.2015.2015 on XP x32 and 7 x64 clients; SEPM server is running 2008 R2 standard x64; and logging to an external SQL 2012 server.
This morning I found that my SEP clients and server had no green dot, and that I could not launch my local Java SEPM console. The SEPM console would error with "The application failed to launch" or "Failed to connect to server". Checked the server services and found the Symantec Endpoint Protection Manager service was stopped. I started it, but about a minute later it would stop and the Application Event Log said "The Java Virtual Machine has exited with a code of -1, the service is being stopped" with a source of "semsrv", Event ID "4096". Starting the service again and reboots of the server did not help.
The issue was: the SQL log files were full.
The resolution: I had my SQL Administrator truncate the SQL logs for SEP and expand them. After that, the service started and kept running OK.
Regards, Tom.
I just wanted to post something because I too read alot of articles on this issue and we had the SAME problem. SEPM service would NOT start. It started but then 5 seconds later would stop on its own. Event viewer logs showed the java -exit error as above but our catalina.out log for tomcat showed something about (Access is denied). We tried a repair of the SEP software and reran the SEP configuration wizard. It worked for a few days but the same thing happened again. We thought it was port network related due to some of the errors we saw in the client management logs. However networking showed no issues. Low and behold we found what worked for us which is why I'm posting just in case it helps someone out there. I came across a thread related to the sem5.log being corrupt. Well we could not find a sem5.log but did have a sem5.db. So kept reading. In that post someone mentioned make sure "Authenticated Users" has both Read and Write access to the c:\programfiles86\symantec\symantecendpointprotectionmanager........folder and let the rights fully propogate. Restart the SEPM service. YAY!! It worked for us. Keep an eye on the event viewer logs to make sure the error does not reappear and check to make sure the service is still running after 10min. or so. Hope this helps someone else not have to go through days of troubleshooting with no resolution. Woohoo!!!
Regards,
Vivek.K
S N tech,
INDIA
Hi,
Good info !!!