Open topic with navigation

TIBCO iProcess® Engine 11.10.0

# Errors Occur on Validating the Installation

## Problem Description

The installer displays one or more error messages when it attempts to validate that the installation has succeeded (see Installing TIBCO iProcess Engine in Console Mode, step 7). For example:

``ERROR: process information unobtainable.``

## Affected Database

Oracle, DB2

## What To Do

To resolve this problem, locate the error message in the following table and follow the instructions there.

Error Message | What to Do...
`Process information unobtainable.` | The installer cannot access the `process_config` table in the database schema (using the `$SWDIR``/util/swadm show_processes` command), which appears to be incomplete or corrupt. To resolve this problem: Remove iProcess Engine (see Uninstalling iProcess Engine) or, if you were upgrading, restore the original version (see Restoring Your Original System if an Upgrade Fails). Reinstall iProcess Engine.
`Sentinel service port (`portNumber`) already used, in state `state`` | Another application appears to be using the portNumber service port selected for use by the indicated Sentinel (either `Watcher` or `Worker`) Process Sentinel process. To resolve this error: Restart the UNIX system and check if these ports are still in use. (You can use the system `netstat` utilities to check which ports are in use.) If the problem persists, assign different port numbers to be used by the iProcess Engine watcher and worker process sentinels by editing the relevant entries in the`/etc/services` file. The entries are:
          nodename_worker nnn/tcp
          nodename_watcher mmm/tcp
where:
| — | node_name is the nodename of this iProcess Engine.
| — | nnn and mmm must be unique numbers in the `services` file depending on what port numbers are already being used on the server.
For example:
          staffw_nod1_watcher 1500/tcp
          staffw_nod1_worker 1501/tcp
`Failed to find Sentinel entry for this node in the /etc/services file.` | The installer has been unable to update the `/etc/services` file with the port number to be used by the indicated Sentinel (either `Watcher` or `Worker`) Process Sentinel process. This is not a fatal error, as the iProcess Engine can still run without these entries. However, TIBCO recommends that you manually add the port numbers used by the iProcess Engine watcher and worker process sentinels to the `/etc/services` file before starting the iProcess Engine. See the entry above for details of the `/etc/services` file entries you need to add.
`RPC Number <`RPCNum`> is already registered with the system's portmapper.` | The RPCNum RPC service number selected for iProcess Workspaces to use to communicate with this iProcess Engine appears to be in use by another application. To resolve this problem: Restart the UNIX system and check if the indicated RPCNum is still in use. (You can use the system `rpcinfo` utility to see which numbers are registered with the portmapper.) If the problem persists, change the RPCNum used by the iProcess Engine by editing line 11 of the `$SWDIR``/swdefs` file. See TIBCO iProcess Engine Administrator’s Guide for more information about the `$SWDIR``/swdefs` file.
`Failed to get nodename from Database.` | The installer cannot read the iProcess Engine nodename from the `nodes` table in the database (using the `$SWDIR``/util/plist -n` command). To resolve this problem: Check that the database is running. Check that the iProcess Engine database users (see iProcess Engine DB Schema Owner Name) have been created, and that these users can successfully connect to the database using the login credentials given during the installation process. (See Changing Database Connection Passwords for more information about how to change the passwords used by these users to connect to the database.)
`Nodenames from Database (`nodeName1`) and swdefs file (`nodeName`) do not match.` | To resolve this problem: Uninstall the iProcess Engine (see Uninstalling iProcess Engine), or, if you were upgrading, restore the original version (see Restoring Your Original System if an Upgrade Fails). Reinstall the iProcess Engine.

Note | If the procedures described above do not resolve the problem, contact TIBCO Support for assistance.

## Changing Database Connection Passwords

If you need to change the passwords that the iProcess Engine DB Schema Owner Name account or the iProcess Engine DB User Name account use to connect to the database, follow this procedure:

| 1. | Log in as the iProcess Engine Administration User Name.

| 2. | Enter the following command:

`$SWDIR``\util\swconfig -u`

The following prompt is displayed:

`Please enter a new Background User Password, ('Q' to quit):`

| 3. | Enter the new password for the iProcess Engine DB Schema Owner Name account. The following prompt is displayed:

    Please enter a new Foreground User Password, ('Q' to quit):

| 4. | Enter the new password for the iProcess Engine DB User Name account.

The `swconfig` utility terminates and displays the following message:

    Now log onto the Database and change the passwords.

| 5. | Change the corresponding Oracle (for Oracle users) or UNIX (for DB2 users) passwords for these users. See your Oracle or UNIX documentation for more information about how to do this.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO iProcess® Engine

Copyright © 1994-2025. Cloud Software Group, Inc. All Rights Reserved.