Endpoint Protection

Using the disaster recovery with database procedure to migrate from a Windows 2003 R2 x64 to a Windows 2008 R2 u may receive the following error after the server reconfiguration: 

In the event viewer is logged the following error: "The Java Virtual Machine has exited with a code of 2, the service is being stopped." and in SEPM:

2010-12-24 11:38:59.891 GRAVE: Unknown Exception in: com.sygate.scm.server.consolemanager.RequestHandler
com.sygate.scm.server.util.ScmServerError: Can't read local server from database!.....

2010-12-24 11:38:59.922 GRAVE: Shuting down server ...

Try reconfiguring the management server replacing the hostname with IP address, in my case it solves the issue.

There r no kb regarding this problem... This is the easiest way.

Bye bye by Fargy

>> Try reconfiguring the management server replacing the hostname with IP address, in my case it solves the issue.

Are you sure you gave your server's name correctly? Please mind that Java is case-sensitive. Also, can you machine resolve it own name?

follow the URL, this should help to know the server name while reconfiguring the server

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

OK, now we know the reason: the field hostname is case sensitive...

Windows is case insensitive but Java is... :(

were you able to configure and login into SEPM?

Now I can, but I need to use IP address or hostname (matching the correct case).

its windows which was not able to resolve the name 

Repair SEPM

https://www-secure.symantec.com/connect/forums/java-virtual-machine-has-exited-code-2-service-being-stopped

yes, you need to use the same host name and IP , else client will not be able to communicate.

the server name can be found

select * from identity_map where type = 'semserver'
 

So can you confirm it has been solved by putting the correct hostname? As I said Java is case sensitive and SEPM is written in Java...