| Event Id | 1040 |
| Source | TSM cluster |
| Description | TSM cluster scheduler generic service resource failover . |
| Event Information | According to IBM Support : Solution : The Event ID 1040 error message can occur in cases where the TSM scheduler service name is not configured identically on both machines of the cluster. For example, the following names used in the dsmcutil install command on node1 and node2 of a cluster called CLUSTER1: NODE1 -> dsmcutil install /name:"TSM Scheduler service: group A" /node:clusternode1 /password:xxxxxxx /startnow:no /autostart:no /clustername:yes /clusternode:cluster1 NODE2 -> dsmcutil install /name:"TSM Scheduler service : group A" /node:clusternode1 /password:xxxxxxx /startnow:no /autostart:no /clustername:yes /clusternode:cluster1 While the syntax of the TSM scheduler service name may look identical in the above commands, there is a very slight difference in the names (an extra space before the : in the dsmcutil command taken on NODE2 exists). This can lead to the above error condition when the TSM scheduler service generic service resource is created within Microsoft Cluster Administrator and tested for failover functionality. Correct the TSM scheduler service name by uninstalling the service (via DSMCUTIL REMOVE) and reinstalling the service (via DSMCUTIL INSTALL). |
| Reference Links | Event ID 1040 from Source TSM cluster |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.