Clustool.exe restore operation does not complete successfully on a Windows Server 2003 or Windows 2000 SP3 cluster

When you restore a cluster configuration by using Clustool.exe, if the restore operation completes with errors, you do not receive any detailed error messages. Other symptoms include the following:

�	If you examine the status of the cluster resources in all cluster resource groups by using Cluster Administrator, you see that all network name resources (except the cluster network name resource) are in a failed state.
�	If you open the properties for each failed network name resource and then examine the Parameters tab, you see that the Name value is empty.
�	If you examine the corresponding values in the HKLM\Cluster\Resources\<guid_number_for_resource> cluster registry subkeys, you see that the values are present.

This issue occurs because Clustool.exe in Microsoft Windows 2000 Service Pack 3 (SP3) and later does not handle extra information that is provided in the cluster registry for network name resources (for example, RequireDNS, RequireKerberos, StatusDNS, StatusKerberos, and StatusNetBIOS). Windows 2000 cluster Kerberos support is increased in Windows 2000 SP3 and later.

Note Clustool.exe runs only on Microsoft Windows NT 4.0 clusters and on Windows 2000 pre-SP3 clusters. The utility is not part of the Microsoft Windows Server 2003 Resource Kit.

To resolve this issue, delete the failed network name resource and then re-create it.

Note This resolution may adversely affect some cluster resources, including Microsoft Exchange Server, Microsoft SQL Server, Microsoft Distributed Transaction Coordinator (MSDTC), spooler resources, and others. Resources where dependency on a network name resource is not required (for example, file share resources) are not negatively affected by this resolution.

To delete the failed network name resource and then re-create it, use one of the following procedures:

�

If the failed network name resource is supporting a file share resource, follow these steps: 1. Remove the dependency for the network name resource. 2. Delete the network name resource. 3. Re-create the network name resource. 4. Add the dependency again.

�

If the failed network name resource is supporting a cluster resource other than a file share resource, you must be more careful. Microsoft recommends that you follow these steps to resolve the issue: 1. Create a temporary network name resource in the same group as the one that is failed. � Make it dependent on the same IP address. � Give it a unique NetBIOS name parameter. 2. Modify the dependencies for the resource(s) that depend on the failed network name resource: � Add the resource that you created in step 1. � Remove the failed resource. � Do not bring anything online. 3. Delete the failed resource, and then immediately re-create it. 4. Follow the procedures in step 2, but this time add the re-created resource on the Dependencies tab, and then remove the temporary one. 5. After you complete the process for each group with a failed network name resource, delete the temporary network name resources, and then bring all resources back online.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base: