Process Sentinels Do Not Start Due to Logon Failure

Problem Description

When you try to start the iProcess Engine for the first time, the iProcess nodeName Process Sentinels service fails to start and displays the following error message (system error 1069):

The service did not start due to a logon failure.

Note	See TIBCO iProcess Engine Administrator’s Guide for more information about how to start the iProcess Engine.

When you install the iProcess Engine, the installer assigns the Log on as a service right to the user account you have chosen to use to run the iProcess nodeName Process Sentinels service (the IPESERVICE user). The right is assigned on the computer where you have installed the iProcess Engine.

However, a conflict can occur if:

•

you have installed the iProcess Engine in a domain, using domain users, and

•

the domain uses a group policy for the Log on as a service right, but the policy does not include the IPESERVICE user.

The domain controller propagates the group policy to the member machines in the domain at regular intervals (by default, every 90 minutes). When this happens, the IPESERVICE user’s locally-assigned right will be overwritten by the group policy. The account therefore loses the Log on as a service right, and so cannot start the iProcess nodeName Process Sentinels service.

What to Do

To resolve this problem:

1.

Change the group policy on the domain controller for the Log on as a service right to include the IPESERVICE user.

Warning

You must have access to an account that has Domain Administrator privileges to be able to change the group policy.

2.

On the computer running the iProcess Engine, either wait for the domain controller to refresh the group policy, or use the Microsoft gpupdate tool to update the policy immediately.

3.

Start the iProcess Engine. The iProcess nodeName Process Sentinels service should start correctly.

See Also

See your Microsoft documentation for more information about group policies, how to change them, and the gpupdate tool.