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

[Migration User]

Hi kindly advice me why I got this error on SEP and possible resolution to this problem  "The Java Virtual Machine has exited with code of -1, the service is being stopped." tnx.

[Migration User]

Java -1 is very generic error happens mainly because of port conflicts and permissions.
There can 100 reason for java -1.Could you please post the scm-server.log from program files\sepm/tomcat/logs directory.

For debugging sepm
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007090612034148

Also check these
"Java -1" error in event log and the error "Failed to connect to server" at login, with HTTP 401 in scm-server-0.log, HTTP 401 1 0 in IIS Logs
http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/d947c52b7da1384a652574e30049221e?OpenDocument

Symantec Endpoint Protection Manager service stops with a Java -1 error in the event log
http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/86368136366e1ad78025734e004734d9?OpenDocument

Event ID 4096 - "Java -1" error in event log and the error "Failed to connect to server" at login, with HTTP 503 in scm-server-0.log on a Windows 2008 Small Business Server 64-bit Edition
http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/0bd5121b20ac1258652575ec0062f4d6?OpenDocument

If  it is a 64 bit server then you might need to change your iis to 64 bit mode
Java -1 Errors and HTTP 500 errors when connecting to the Symantec Endpoint Protection Manager on a Windows Server 2003 64 bit
http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/387a93f58eb98c39882573ed007b50f3?OpenDocument

[Migration User]

Vikram has provided almost everything that you  need.
I would just like to add that what could have caused this issue if it was running fine earlier:

1. Insufficent space on the drive where SEPM in installed
2. A java Update
3. If you are uisng SQL then the the Transcation logs would have filled.
4. A windows update
5. Change in the GPO in respect with permssion

[Ramji Iyyer]

Above errors comes once in three months.

Vikram has given the solution..

I dont want to repeat again..

Regards...
Ramji Iyyer

[mikhael47]

I found this issue when I installed SEP to a machine that had VMware Virtual Center installed on it.  Virtual Center uses the embedded database too and I needed to re-install everything then tell SEP to use port 8006 for connections.  Instructions can be found in Vikram's post.

[Migration User]

 @mikhael-- there was a very easy way to do that you just had to edit the server.xml file and change the port number from 8005 to 8006 over there..

Easiet way to check if there is conflict with port 8005..open taskmanager ..processes--sort by name--and if you find any tomcat.exe or tomcat(1-9).exe..its definitely port 8005 problem..

[Migration User]

Hi -

We had this same error previously, and it had to do with Java HeapSpace issues (memory management, and competing for RAM with SQL server).

Unfortunately, even setting the Java HeapSpace to the maximum possible on our servers (32bit OSs, Windows Server 2003, with 4G RAM),   did not resolve the problem.


Our problems went away after we migrated up to SEP 11 MR4 MP2.    We are still "right on the edge" with respect to RAM, but better efficiencies in the way SEP MR4MP2 uses SQL and Java must be the difference.


Our next plan is to migrate the database off the SEPM itself over to another SQL database purpsed server.

Doug

[Migration User]

Hi Vikmar,

I'll check all the links above and give it a try. Update you later with the results and hope one of it will work. thanks so much!

[Peterpan]

try to reinstall your IIS, I have encountered this before hope it will help you also

[Migration User]

Hi Vikram,

Thanks for the link given.

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

regards,

[Migration User]

Had the same error and changing the tomcat port worked for me

Thanks