Netman does not start after upgrading TWS V8.5.1 to V8.6 on Windows

by Anders Soderback

If the upgrade of Tivoli Workload Scheduler V8.5.1 to V8.6 fails when it is starting the TWS instance. The output indicates that the netman service could not be started. Attempt to start TWS manually shows the following output:

System error 1075 has occurred.
The dependency service does not exist or has been marked for deletion.
The Tivoli Netman service has failed to start with the return code 2


Check the netman service dependency with the sc command.

>sc qc tws_netman_twsuser
[SC] QueryServiceConfig SUCCESS
SERVICE_NAME: tws_netman_twsuser
        TYPE               : 10  WIN32_OWN_PROCESS
        START_TYPE         : 3   DEMAND_START
        ERROR_CONTROL      : 1   NORMAL
        BINARY_PATH_NAME   : C:Program FilesIBMTWATWSbinnetman.exe
        LOAD_ORDER_GROUP   :
        TAG                : 0
        DISPLAY_NAME       : Tivoli Netman (for twsuser)
        DEPENDENCIES       : IBMWAS61Service – twsuser
        SERVICE_START_NAME : .twsuser


It shows that it has a dependency on the “IBMWAS61Service – twsuser” service. The WebSphere Application Server has been updated to V7.0 and the service for WAS 6.1 has been deleted by upgrade. Update the dependency as the following example:

C:>sc config tws_netman_twsuser depend= “IBMWAS70Service – twsuser”
[SC] ChangeServiceConfig SUCCESS


Check with the sc qc command again.

C:>sc qc tws_netman_twsuser
[SC] QueryServiceConfig SUCCESS
SERVICE_NAME: tws_netman_twsuser
        TYPE               : 10  WIN32_OWN_PROCESS
        START_TYPE         : 3   DEMAND_START
        ERROR_CONTROL      : 1   NORMAL
        BINARY_PATH_NAME   : C:Program FilesIBMTWATWSbinnetman.exe
        LOAD_ORDER_GROUP   :
        TAG                : 0
        DISPLAY_NAME       : Tivoli Netman (for twsuser)
        DEPENDENCIES       : IBMWAS70Service – twsuser
        SERVICE_START_NAME : .twsuser


Change the update step to ready and click on ‘run all’ to continue the upgrade.
by Anders Soderback