iProcess Engine Processes Do Not Start

Problem Description

When you try to start iProcess Engine for the first time, the iProcess nodeName Process Sentinels service starts but the remaining iProcess server processes do not appear.

Note 

See TIBCO iProcess Engine Administrator’s Guide for more information about how to start the iProcess Engine and the processes that should appear when you start it.

iProcess Engine processes communicate by publishing and subscribing to events. When the iProcess Engine starts, a START event is issued. The Process Sentinels subscribe to that event, which causes them to start the necessary iProcess Engine server processes.

The iProcess Events64 COM+ application provides event handling functionality for the iProcess Engine. If there is a problem with this application, events cannot be processed, so the Process Sentinels do not receive the START event and therefore do not start the iProcess Engine server processes.

The iProcess Events64 application runs using the IPESERVICE Windows account. When the application starts up, it authenticates the IPESERVICE user, either:

• on the local machine, if local accounts are being used, or
• on the appropriate domain controller, if domain or trusted domain accounts are being used, or if the iProcess Engine is installed in an Active Directory environment.

If authentication fails, the iProcess Events64 COM+ application fails to start. Possible reasons for authentication failure are:

• The application cannot contact the domain controller for some reason - for example, transient network problems.
• Incorrect username, the wrong IPESERVICE user is being used.
• Incorrect password for the IPESERVICE user. This can occur if the IPESERVICE user account has been deleted and recreated for any reason. An encrypted identifier is associated with each instance of a username/password combination. Although the recreated username and password are the same, this identifier is different, so authentication fails. The password must be manually re-entered.

What to Do

To try and correct any problems with the iProcess Events64 application:

1. Open the Control Panel window, click Administrative Tools, and then click Component Services. The Component Services console is displayed.
2. In the left pane, select Component Services > Computers > My Computer > COM+ Applications.
3. Right-click COM+ Applications and select View > Status View. The right-hand pane shows whether or not the iProcess Events64 application is currently running.
4. Right-click iProcess Events64 and select Properties from the pop-up menu.
5. On the Identity tab (which specifies the account that the iProcess Events64 application runs under):

Select the This user radio button, and make sure that the specified User is the correct IPESERVICE user for this installation.

Enter the password for this user again in both the Password and Confirm Password fields.

6. Click the OK button.
7. If the iProcess Events64 application is currently running, right-click it and shut it down.
8. Right-click the iProcess Events64 application and start it. Make sure that the application is running.

You should now be able to start iProcess Engine server processes. To do this:

 

  1. Log in as the IPEADMIN user.

  2. Make sure that the iProcess nodeName Process Sentinels service is running.

  3. Use the command:

    SWDIR\bin\swstart

  4. Check that the appropriate server processes start (using either SWDIR\util\swadm or Task Manager).