A. Certain cluster-aware applications register dynamic link libraries on the cluster nodes to enable specific functionality. When you add additional nodes to a cluster, a check is performed to make sure all registered DLLs exist on the new node. If any are missing, an error is shown.
The node was added successfully, but the 'Host' resource type could not be installed on it. Unable to find 'wtclusres.dll' on any of the cluster nodes. The node was added successfully, but the 'WTDisk' resource type could not be installed on it. Unable to find 'wtclusres.dll' on any of the cluster nodes.
The problem is that if a resource was moved to this new node of the type displayed in the warning, the required DLL's would be missing, and therefore the resource would fail to function. The solution is to make sure you install the additional software on the new node in the cluster. In my example above, I had installed a cluster-aware iSCSI target on one of the nodes prior to adding the new node.
The error doesn't stop you from adding the node, and other resources that don't require the special DLLs will function with no problems.
Related Reading:
- Q. Does the Windows Storage Server (WSS) iSCSI Target support Cluster Shared Volumes (CSV)?
- Q. I'm seeing a big performance difference with my live migration operations when I use Cluster Shared Volumes (CSV), is this normal?
- Q. I'm using the Microsoft iSCSI Target on my Windows Storage Server 2008 implementation. Can I install the iSCSI Target in standalone mode if the WSS is clustered?
- Q. Should I disable NetBIOS over TCP/IP on my Windows Server 2008 R2 Cluster Shared Volume (CSV) cluster networks?
Check out hundreds more useful Q&As like this in John Savill's FAQ for Windows. Also, watch instructional videos made by John at ITTV.net.
