Troubleshooting Installation Problems

Contents
casp941
Contents
Installation Media Does Not Contain Installation Information
Symptom:
The following message appears:
The <sp> installation media does not contain the installation information for this platform.
Solution:
This message appears when you do not have the correct installation media for the host platform. Use the
installation media of the platform on which you are installing.
Incorrect Text Displays on the Screen
Valid on Solaris
Symptom:
The screen displays inverted text, partially missing text, or other improper text.
Solution:
Ensure that you are using the latest drivers for your video card.
<index file name> Cannot Be Found
Symptom:
I received the following error:
Error: <index file name> not found!
Solution:
One of the following conditions caused this error:
  • Extraction of the Installation record from the distribution medium was incomplete.
  • The Installation record files were improperly removed or modified before the installation.
Retry the installation. If the failure persists, contact Technical Support.
Received a Landscape Handle Error
Symptom:
The following message appears:
** Error during Set Landscape Handle
Solution:
The installation is unable to set the
SpectroSERVER
landscape handle value, which is a serious problem. Contact Technical Support.
Received an InvocationTargetException Error
Symptom:
The following message appears:
Invocation of this Java Application has caused an InvocationTargetException. This application will now exit. (LAX) Stack Trace: java.awt.HeadlessException: No X11 DISPLAY variable was set, but this program performed an operation which requires it. at java.awt.GraphicsEnvironment.checkHeadless (GraphicsEnvironment.java:159) at java.awt.Window.<init>(Window.java:317) at java.awt.Frame.<init>(Frame.java:419) at java.awt.Frame.<init>(Frame.java:384) at javax.swing.JFrame.<init>(JFrame.java:150) at com.zerog.ia.installer.LifeCycleManager.f(DashoA8113) at com.zerog.ia.installer.LifeCycleManager.g(DashoA8113) at com.zerog.ia.installer.LifeCycleManager.a(DashoA8113) at com.zerog.ia.installer.Main.main(DashoA8113) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.zerog.lax.LAX.launch(DashoA8113) at com.zerog.lax.LAX.main(DashoA8113) This Application has Unexpectedly Quit: Invocation of this Java Application has caused an InvocationTargetException. This application will now exit. (LAX)
Solution:
Your DISPLAY environment variable is not set to the host name of the system on which you are running the installation software. Set the environment variable correctly.
Received a Database Initialization Error
Symptom:
I received the following message:
** Error during Database Initialization
Solution:
The installation is unable to create the
SpectroSERVER
database, which is a serious problem. Contact Technical Support.
Received a Database Saving Error
Symptom:
The following message appears:
** Error during Database save as db_<extension>
Solution:
The installation is unable to save the existing
SpectroSERVER
database. The most likely cause is that the
SpectroSERVER
database is write-protected or does not exist (for example, the database was deleted).
To make the
SpectroSERVER
database writable, use the chmod utility. Then, reinstall
. If this procedure does not work, contact Technical Support.
Received a VNMRC File Processing Error
Symptom:
The following message appears:
** Error during Processing of vnmrc file
Solution:
The installation is unable to set values properly in the
SpectroSERVER
defaults file, SS/.vnmrc. This problem cannot be resolved at the installation site. Contact Technical Support.
Server Configuration Problems
Valid on Solaris and Linux
Symptom:
The following message appears:
Unable to Connect to Location Server
Solution:
Follow these steps:
  1. Verify connectivity by pinging the <
    CA Spectrum host
    >.
  2. Verify name resolution.
  3. Verify that the installation host is in the .hostrc file on <
    CA Spectrum host
    >.
  4. Verify that the main location server is running on <
    CA Spectrum host
    >.
  5. Verify that the location server ports are correct.
Installation Owner User Problems
Valid on Linux and Solaris
Symptom:
I have installation owner user problems.
Solution:
Follow these steps:
  1. Verify the name resolution (without the domain name) to the <
    CA Spectrum host
    >.
  2. Select Users from the Control menu in the
    Control Panel and verify that the installation owner appears in the Users dialog.
  3. Verify that the same version of
    is installed on the computers where OneClick and the
    SpectroSERVER
    are installed.
OneClick Web Server Error Message
Symptom:
The resource at http://<
server
>/spectrum/index.jsp was not found. Authorization could not be completed.
Solution:
You could have another Web services application running on the same port Apache Tomcat is attempting to use. Stop (and disable, if necessary) the other application and associated services and restart the Apache Tomcat service.
OneClick Web Server Shuts Down
Symptom:
I upgraded to VMware 2.0 and it runs an Apache Tomcat server of its own. After I install the OneClick web server, the OneClick web server shuts down when it attempts to bind to port 8005. Then, I receive the following error message:
- StandardServer.await: create[8005]: java.net.BindException: Address already in use: JVM_Bind
Solution:
By default, Apache Tomcat uses port 80 on Windows platforms and port 8080 on Linux and Solaris platforms. If SSL is configured, Apache Tomcat uses port 443. Apache Tomcat also uses the default server shutdown port 8005. When installing the OneClick web server, be sure that other applications on the same computer do not use these ports. Or, you can change the ports on the instance of Apache Tomcat that
uses.
We recommend that you do
not
install the OneClick web server on a computer where an instance of Apache Tomcat is already running.