Troubleshooting

If you encounter problems with installation, make sure that your system meets all prerequisites. Next, check the installer log file for potential problems.

Installer Log File

The installer log file, tibco_universal_installer.timestamp.username_install.log is available in the following locations.
  • Windows - Documents and Settings\username\.TIBCO\install_timestamp. If you are using Windows 7 and above - Users\username\.TIBCO\install_timestamp.
  • Linux - user_home_dir\.TIBCO\install_timestamp.
The installer log file captures the following information:
  • Installation home details such as the user that invoked the installer, hostname, Java home in the installation home, operating system details, and so on
  • List of assemblies installed
  • Information related to the Ant scripts that are executed by the installer
To change the location of the installer log file, specify the option -V logFile="myLogFile" when you run the installer.

TIBCO_JRE Error Message During Upgrade

Problem
When you perform an upgrade, the installer sometimes displays an error that states TIBCO_JRE files are locked, even if JRE is not running and the installer is not using TIBCO_JRE.
Workaround
Reboot the system on which the installer is running.

CONFIGURE_FAILED Message in Single Machine Setup

Problem
During development, you install all components on a single machine. After the Administrator server configuration, select TIBCO Adapter Implementation Type App Template from the list of application templates to deploy on the default node. A CONFIGURE_FAILED message results.
Workaround
Installation instructions clearly state not to select this option. Because the TIBCO Hawk Agent workflow is not run at this time, deployment of this component results in a startup failure with a CONFIGURE_FAILED message.

Installing ActiveMatrix Using a Non-default Administrator Account

Scenario
This is a scenario on Windows 2008 or Windows 7 when the product is installed using a non-default Administrator user. Assume you have two accounts: Administrator, which was created at the operation system setup, and tibco, which was created afterwards and added to Administrator group. As a result, tibco is considered as a non-default Administrator. With a non-default Administrator, there are some issues you might encounter:
Problem Resolution
The file, machine.xmi, is locked when you create TIBCO ActiveMatrix Administrator Server using TIBCO Configuration Tool. Start TIBCO ConfigurationTool.exe with the Run As Administrator option.
Access is denied while starting or stopping TIBCO Host from the command-prompt. Start the command prompt using the Run as Administrator option.

ActiveMatrix Administrator Not Starting Due to Database Connection Failure

Problem
The ActiveMatrix Administrator server is not starting, or you are unable to login due to database connection failure.
Workaround
Perform the following procedure to update database configuration:
  1. Start the SystemNode and tibcohost, if stopped, even if the ActiveMatrix Administrator is not working.
  2. In your database server, unlock the user account. When several failed attempts are made at entering a password, ActiveMatrix locks an account. This is often encountered while using ActiveMatrix Administrator with Oracle, especially if an expired password has been changed.
    Note: For Oracle, you can unlock a user account by executing the following command in sqlplus as a DBA: 
    SQL> alter user <username> account unlock;
  3. Launch TIBCO Configuration Tool, update the database configuration for the core ActiveMatrix Administrator as follows:
    1. Select Edit TIBCO ActiveMatrix Administrator Server Configuration .
    2. From the Select Server Configuration drop-down list, select the enterprise name and server name.
    3. Check Edit Database Settings.
    4. If the users or groups are defined in the Administrator database and not in an LDAP server, select Edit Authentication Realm Settings .
    5. Click Test Connection to verify the settings.
    6. Click Configure to apply the changes. When the update is complete, TIBCO Configuration Tool restarts the system node.
    7. Wait for a few minutes for the system node to become available.
  4. Login to ActiveMatrix Administrator UI, and perform the following steps:
    1. Navigate to Shared Objects > Resource Templates, and select TIBCO ActiveMatrix Governance JDBC Resource.
      Note: Select GovernanceJDBCSharedResource if you upgraded from a prior version. If you do not see this resource template, it means monitoring services were not deployed, and hence you can skip this step.
    2. In the details section of this resource template, make corrective changes to the configuration, if needed and save the changes.
    3. Reinstall resource instances and restart applications.
    4. From the Resource Instances tab of the details section, verify that the resource instance is successfully installed and is in the Running state. There will be multiple resource instances if you have a replicated Administrator.
  5. Repeat step 4 for the Resource Templates - TIBCO ActiveMatrix LogService JDBC Resource and TIBCO ActiveMatrix PayloadService JDBC Resource.
    Note: If you upgraded from prior releases, the names will be cl_logservice_jdbc and payloadJdbcSharedResource. If you do not see these resource templates, it means common logging services were not deployed, and hence you can skip this step.
  6. Restart the SystemNode one more time using the following tibcohost commands:
    1. To stop tibcohost (.exe): stopNodes -nodeName SystemNode. Wait for a few minutes for a graceful shutdown.
    2. To start tibcohost (.exe): startNodes -nodeName SystemNode. Wait for a few minutes for the SystemNode to come up.
    After the restart, the new database settings are fully in effect.
Contents
Search Results