| Event Id | 1070 |
| Source | ClusSvc |
| Description | Description 2: Cluster node attempted to join the cluster but failed with error 5052. Description 2: The node failed to begin the process of joining the server cluster. The error code was 1726. |
| Event Information | According to Microsoft: CAUSE: This problem occurs when there are many resources on a cluster. Cluster resources are maintained in the cluster hive. When a node joins a cluster, the complete cluster hive is saved to the hard disk. If the cluster hive is large, this process may take longer than the node join time-out period. RESOLUTION: A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. WORKAROUND: To work around this problem, remove some of the resources to reduce the size of the cluster hive so that it is under 10 megabytes. To determine the size of the cluster hive, follow these steps on the cluster node: 1. Click Start, click Run, type Explorer, and then click OK. 2. Locate the Clusdb file in the %systemroot%\Cluster folder, and then examine the Size column . Problem: The cluster node attempted to join an existing cluster but was unable to complete the process. This problem may occur if the node was previously evicted from the cluster. Solution: If the node was previously evicted from the cluster, you must remove and reinstall MSCS on the affected server. |
| Reference Links | Subsequent nodes cannot join a cluster, and events 1070 and 1009 are logged with Windows Server 2003 Description of the standard terminology that is used to describe Microsoft software updates |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.