The IBM Workload Scheduler for user service (batchup) fails to start

The IBM Workload Scheduler for <˂TWS_user>> service (sometimes also called batchup) does not start when the other IBM Workload Scheduler processes (for example, mailman and batchman) start on workstations running Windows™ 2000 and 2003 Server. This problem occurs on a fault-tolerant agent, either after a conman start command or after a domain manager switch. The Tivoli® Token service and netman services are unaffected.

This problem does not impact scheduling, but can result in misleading status data.

Cause and solution:

The problem is probably caused either because the <˂TWS_user>> has changed password, or because the name of the service does not match that expected by IBM Workload Scheduler. This could be because a change in the configuration of the workstation has impacted the name of the service.

To resolve the problem temporarily, start the service manually using the Windows™ Services panel (under Administrative Tools. The service starts and runs correctly. However, the problem could reoccur unless you correct the root cause.

To resolve the problem permanently, follow these steps:
  1. If the <˂TWS_user>> has changed password, ensure that the service has been changed to reflect the new password, as described in IBM® Workload Scheduler: Administration Guide.
  2. Look at the Windows™ Event Viewer to see if the information there explains why the service did not start. Resolve any problem that you find.
  3. If the failure of the service to start is referred to the following reason, there is a mismatch between the name of the installed service and the name of the service that the mailman process calls when it starts: 
    System error code 1060: 
        The specified service does not exist as an installed service
    The normal reason for this is that the user ID of the <˂TWS_user>> has changed. The <˂TWS_user>> cannot normally be changed by you, so this implies some change that has been imposed externally. A typical example of this is if you have promoted the workstation from member server to domain controller. When this happens, the local <˂TWS_user>> is converted automatically to a domain user, which means that the domain name is prefixed to the user ID, as follows: <domain_name>\<TWS_user>.

    The problem occurs because of the way IBM Workload Scheduler installs the service. If the workstation is not a domain controller the installation names the service: tws_maestro_<TWS_user>. If the workstation is a domain controller the installation names the service: tws_maestro_<domain_name>_<TWS_user>.

    When batchman starts up it discovers that the <˂TWS_user>> is a domain user. Batchman tries to use the domain user service name to start the batchup service. The action fails because the service on the workstation has the local user service name.

    To resolve this problem you must change the name of this service, and to do this you are recommended to uninstall the IBM Workload Scheduler instance and install it again.

    An alternative, but deprecated, method is to change the name of the service in the Windows™ registry.

    Attention: Making changes to the Windows™ Registry can make the operating system unusable. You are strongly advised to back up the Registry before you start.
    If you decide to use this method you must edit the following keys: 
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\tws_maestro_<˂TWS_user>> 
                HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\tws_maestro_<˂TWS_user>> 
                HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\tws_maestro_<˂TWS_user>>
    and change them as follows: 
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\tws_maestro_<domain_name>_<˂TWS_user>> 
                HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\tws_maestro_<domain_name>_<˂TWS_user>> 
                HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\tws_maestro_<domain_name>_<˂TWS_user>>

    If you have changed the name of the service in the registry, you must ensure that the logon is correct. Open the Log On tab of the service in the Windows™ Services panel and change the account name, if necessary, to <domain_name>\<˂TWS_user>>. You must also enter the password and confirm it.