Troubleshooting Installations

This chapter provides tips and suggestions for troubleshooting problems with CA Configuration Automation installations and upgrades.

Running Installers Remotely

You may encounter problems trying to run the installation wizards for Solaris remotely on Windows. An installation started from Windows using a remote X session can fail, display text strings incorrectly, crash and core dump, and display an error containing the following string:

An unexpected exception has been detected in native code outside the VM.

The problems can be caused by the following:

One of the following known Solaris bugs using the Java 2 SDK in the Solaris operating environment:
- An X server crash can occur when accessing TrueType or Type1 fonts. A patch is forthcoming from Sun. (Solaris Xserver bug 4215548)
- GUI services that use dgalib can crash the Xserver. Patch 107078-07 will fix this problem. This patch is currently available only with a SunSpectrum service contract. (Solaris Xserver bug 4198669)
There is a workaround that you can use until the patches become available. Set the environment variable NO_J2D_DGA to true before running the installer. If you are using C shell, reference this example:
```
% setenv NO_J2D_DGA true
```
This workaround tells the Java 2D software not to use DGA to render the graphics.
Using a Windows X server's native window manager (for example, running the installation using telnet from the Windows Run window). The suggested workaround is to use the remote server's native window manager. For more information for your specific X server, consult the documentation or the support organization within your company. You can also run the installation using console mode from the command line (for more information, see Using Console Mode).

Using Supported Path Names for Installation

On UNIX-based systems, use only alphanumeric, underscore ( _ ), and forward slash ( / ) characters for path names (no embedded blanks or other special characters).

On Windows-based systems, use only alphanumeric, underscore ( _ ), blank, and back slash ( \ ) characters for path names (no other embedded special characters).

Verifying CA Configuration Automation Server Installation

Troubleshooting CA Configuration Automation Server installation problems primarily involves checking log files for errors and verifying the contents of the configuration files created during installation. This section highlights the important log and configuration files you should review. For samples and more information about these log and configuration files, see Configuration Files and Log Files.