|
Possible Cause |
Solution |
|---|---|
|
You are starting ConsoleOne on a Windows computer that doesn't have the required drive mapping or Novell client software. |
Make sure you have the system requirements and drive mappings specified for Windows. |
|
You are starting ConsoleOne on a NetWare® server that doesn't have NJCL 2 installed properly. |
Remove the \NJCLV2 folder from SYS:JAVA on your server and reinstall ConsoleOne. This installs a new copy of NJCL 2 on your server so that ConsoleOne will work. |
|
You are starting ConsoleOne on a Linux or Solaris computer that doesn't have the correct Java runtime environment (JRE). |
If you chose not to install the JRE during installation of ConsoleOne and your existing JRE is not the one noted in System Requirements for Linux or System Requirements for Solaris, you might want to add the bundled JRE to your ConsoleOne installation (type c1-install -c jre at the system prompt, applicable to Consoleone 1.3.6f or lower). For Consoleone 1.3.6h or higher, type
If you are sure you want to run with a different JRE, then set the JRE_HOME or C1_JRE_HOME environment variable to the location of that JRE. ConsoleOne determines which JRE to use as follows:
|
|
You are starting ConsoleOne remotely through an X terminal session on a computer that doesn't have an X windowing subsystem. |
If ConsoleOne is installed on a Linux or Solaris computer and you are trying to run it remotely through an X terminal session, the computer where you are running the terminal session must have an X windowing subsystem installed or it won't work. The X terminal session must be configured to permit transmissions from the remote host and to use the local X windowing subsystem for display. |