By webshesh on Nov 09, 2008
OpenSSO configuration is highly sensitive when it comes to domain name and host resolution. After installation (deployment of the WAR file on the container), once you start the custom configuration, sometimes the default OpenDS (embedded config store) port is displayed as "-1". If the port shows up as "-1" -- you can be pretty sure your configuration will not go through; even if you change the port to 50389 or any other available port.
This is caused due to a missing FQDN entry for the host in the hosts file or a missing DNS entry for the host.
If you have installed OpenSSO on a host - "shesh.sun.com", make sure you lauch the configurator using a FQDN in the URL and also make sure that the OpenDS host during configuration has the fully qualified host (shesh.sun.com) and also make sure that the host name can be resolved.
The ill-informing error simply states that the "OpenDS instance cannot be started" when the configuration is aborted. There will be no "install.log" under the instance root and to get you even more confused, the OpenDS log will say "Directory Server Successfully starter" :-)