Desktop Manager Troubleshooting

Cannot Install

Symptom: at the end of the installation of the Java Web Console a message states that it cannot start because there are no registered applications.

Possible causes: no applications have been installed, including the Desktop Manager. .

Solution: install the Desktop Manager and then start the Java Web Console.

Connection Refused

Symptom: you try to open an appropriate URL, for example http://<hostname>.<domainname>:6789, but you receive a message that the connection is refused.

Possible causes: the Java Web Console is not running on the server.

Solution: to start the Java Web Console, become superuser and execute the following commands:

#smcwebserver status
#smcwebserver start

Cannot Log In

Symptom: the user/password combination is rejected on the login page of the Java Web Console.

Possible causes: the corresponding UNIX user account does not exist.

Solution: Check that a corresponding UNIX user name and password is configured on your system. If necessary, create a local UNIX user account for your tests.

No Desktop Manager Link

Symptom: the Java Web Console application list page does not display the Sun Desktop Manager link.

Possible causes: the Desktop Manager module is not installed.

Solution: To check if the Desktop Manager is installed in the Java Web Console, become superuser and execute the following command:

# smreg list -a

If the list does not contain the com.sun.apoc.manager_<version> application, you need to reinstall the Desktop Manager.

Null Pointer Exception, Tomcat/Java error or Blank Page

Symptom: you start the Desktop Manager but only a blank page or error messages appear.

Possible causes: if the error mentions NoClassDefFoundError: sun/tools/javac/Main, then the Java Web Console is using the wrong Java version.

Solution: the current Java Web Console Java environment can be checked by executing # smreg list -p and looking at the java.home property. This property must point to a valid Java home, and that home must be a JDK. If this value is incorrectly set, you need to execute the following command:

# smreg add -p java.home=<JAVA_HOME>

<JAVA_HOME> must point to a valid installation, for example, where javac can be found in the bin subdirectory.

You then need to restart the Java Web Console with the following command:

# smcwebserver restart

Cannot Connect to an SSL LDAP Server

Symptom: after providing the LDAP server details in the repository creation wizard, including checking the Use SSL box, pressing Next yields a message box stating the server cannot be contacted.

Possible causes: the improper port number has been provided, the LDAP server is not configured to listen to connections using SSL on that port, or the proper certificates are missing in the Java Web Console key store.

Solution: first check that the LDAP server is configured to listen to SSL connections requests on the port specified in the wizard. If this is correct, ensure that either the Certification Authority or the LDAP server certificate is present in the Java Web Console key store, which is located in /etc/opt/webconsole/keystore. The certificate can be added with the command keytool -import -file <certificate file> -keystore /etc/opt/webconsole/keystore. The default password for that key store is changeit. The Java Web Console needs to be restarted for that change to be visible by the Desktop Manager using the command smcwebserver restart.

Cannot Write to Directory

Symptom: while creating a file-based or hybrid backend, a “Cannot write to directory!” error appears.

Possible causes: noaccess user does not have the correct permissions.

Solution: assign write permissions to the noaccess user.