Installation FAQs and Troubleshooting


This section lists some common errors along with their causes and solutions.

Frequently Asked Questions

Where is the installation log file located?

Install and uninstall log files are created in the TIBCO_HOME\log directory.

What should I do, if JVM crashes when I run the installer?

The installer first extracts the bundled JVM into a temporary area and then uses it to launch itself. It for some reason, the JVM crashes, you could still run the installer using another JVM, preferably JVM 1.3.1 or higher. The syntax is:

 
TIB_adcom-simple_5.3.0_w32.exe -is:javahome C:\j2sdk1.4.0 

The javahome directory must contain bin/java.exe or bin/java.

The installer will use the externally supplied JRE to launch itself.

Will 5.1 installer recognize a 3.x or 4.x installation?

TIBCO products follow a three digit release numbering scheme:

Major.Minor.Maintenance

Product releases that differ in either Major or Minor numbers will be a separate installation, and will not recognize the old installation. In this case, 5.0 is a major release and hence will not recognize either 3.x or 4.x product installations.

What is uninst2 directory?

If the original uninstall directory is in use at uninstall time, it cannot be removed by the installer program. The installer then creates a second uninstall directory for the second installation. To remove the second installation, you must invoke the uninstall program from the second uninstall directory. The original uninstall directory can also be manually removed, if empty.

Speeding Up Installation

The installer for TIBCO 5.x products is Java-based and requires a Java Virtual Machine (JVM) to launch. If the installer can use a JVM already on your system, installation is faster and uses less disk space. Otherwise, the installer extracts JVM from the installation package. This section explains where the installer searches for JVM, and how you can add a different location to the search path.

Every product installer is bundled with the appropriate platform-specific JVM version. When launched, the installer first searches for the appropriate JVM version on the target system.

How the Installer Searches for JVM

The installer by default searches for an appropriate JVM version in a set of standard locations. These standard locations are platform specific and are listed in JVM Search Locations. On each platform, the installer searches for JVM 1.3.1 only.

Speeding the JVM Search

You can speed up the JVM search by taking one of these actions before you launch the installer:

Benefits of Using Available JVM over Extracting Bundled JVM

JVM Search Locations

The following tables list the search locations for the Microsoft Windows platforms.

The installer only searches for JVM version 1.3.1. If a different JVM version exists in the system, or is passed in using the environment variable or command-line option, the installer ignores that JVM and extracts the bundled JVM.

Table 4 Microsoft Windows (JVM 1.3.1)
Location
Description
Environment
Set in Control Panel, not in command prompt
JAVA_HOME  
JDKHOME  
Registry
\HKEY_LOCAL_MACHINE\SOFTWARE\    
JavaSoft\Java Runtime Environment\    
1.3\JavaHome \HKEY_LOCAL_MACHINE\SOFTWARE\   
JavaSoft\  Java DevelopmentKit\1.3\JavaHome  
Directory
\Program Files\JavaSoft\JRE\1.3.1 
\JavaSoft\JRE\1.3.1  
\Java\JRE\1.3.1  

Running Out of Disk Space

The installer calculates the disk space required in product home location, for the selected components. The calculation is done before the actual installation (copying of files to system) begins. The installer will proceed only if sufficient free disk space is available in product home location.

However, if disk space is consumed by another process while the installer is copying the files, and if the required disk space is thereby reduced, the installer may fail and will then give a failure message.

Solution

While performing installation, avoid running other processes that consume disk space in product home location.

Configuring TIBCO Hawk

Error

TIBCO Runtime Agent includes the TIBCO Hawk Agent only. If you install the full TIBCO Hawk package after installing TIBCO Runtime Agent and do not have a Java Runtime Environment (other then the TIBCO JRE) installed, the TIBCO Hawk Configuration tool is unable to determine the Java home location and the JVM executable. The TIBCO Hawk services will not start correctly and you will be unable to start the TIBCO Hawk Display.

Resolution
  1. Start the TIBCO Hawk Configuration tool. For example, on Microsoft Windows:
  2. Start>TIBCO>TIBCO Hawk>Hawk Configuration

  3. Under the General tab, click Advanced.
  4. In the Java Home Directory field, provide the path to Java. For example:
  5. C:\tibco\jre\1.4.2

  6. In the JVM Executable field, provide the JVM executable. For example:
  7. java.exe

The services will start properly and the TIBCO Hawk Display will run.


TIBCO Adapter™ for COM User’s Guide
Software Release 5.3, September 2005
Copyright © TIBCO Software Inc. All rights reserved
www.tibco.com