Hi all,
I am trying to create a 2 node cluster on two x64 Windows Server 2008 Enterprise edition servers. I am running the setup from the failover cluster MMC and it seems to run ok right up to the point where the snap-in says creating cluster. Then it seems to hang on "forming cluster" and a message pops up saying "The operation is taking longer than expected". A counter comes up and when it hits 2 minutes the wizard cancels and another message comes up "Unable to sucessfully cleanup".
The validation runs successfully before I start trying to create the cluster. The hardware involved is a HP EVA 6000, two Dell 2950's
I have included the report generated by the create cluster wizard below and the error from the event log on one of the machines (the error is the same on both machines).
Is there anything I can do to give me a better indication of what is happening, so I can resolve this issue or does anyone have any suggestions for me?
Thanks in advance.
Anthony
Create Cluster Log
==================
Beginning to configure the cluster <cluster>.
Initializing Cluster <cluster>.
Validating cluster state on node <Node1>
Searching the domain for computer object 'cluster'.
Creating a new computer object for 'cluster' in the domain.
Configuring computer object 'cluster' as cluster name object.
Validating installation of the Network FT Driver on node <Node1>
Validating installation of the Cluster Disk Driver on node <Node1>
Configuring Cluster Service on node <Node1>
Validating installation of the Network FT Driver on node <Node2>
Validating installation of the Cluster Disk Driver on node <Node2>
Configuring Cluster Service on node <Node2>
Waiting for notification that Cluster service on node <Node2>
Forming cluster '<cluster>'.
Unable to successfully cleanup.
To troubleshoot cluster creation problems, run the Validate a Configuration wizard on the servers you want to cluster.
Event Log
=========
Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: 29/08/2008 19:43:14
Event ID: 1570
Task Category: None
Level: Critical
Keywords:
User: SYSTEM
Computer: <NODE 2>
Description:
Node 'NODE2' failed to establish a communication session while joining the cluster. This was due to an authentication failure. Please verify that the nodes are running compatible versions of the cluster service software.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-FailoverClustering" Guid="{baf908ea-3421-4ca9-9b84-6689b8c6f85f}" />
<EventID>1570</EventID>
<Version>0</Version>
<Level>1</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2008-08-29T18:43:14.294Z" />
<EventRecordID>4481</EventRecordID>
<Correlation />
<Execution ProcessID="2412" ThreadID="3416" />
<Channel>System</Channel>
<Computer>NODE2</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="NodeName">node2</Data>
</EventData>
</Event>
====
I have also since tried creating the cluster with the firewall and no success.
I have tried creating the node from the other cluster and this did not work either
I tried creating a cluster with just a single node and this did create a cluster. I could not join the other node and the network name resource did not come online either. The below is from the event logs.
Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: 01/09/2008 12:42:44
Event ID: 1207
Task Category: Network Name Resource
Level: Error
Keywords:
User: SYSTEM
Computer: Node1.Domain
Description:
Cluster network name resource 'Cluster Name' cannot be brought online. The computer object associated with the resource could not be updated in domain 'Domain' for the following reason:
Unable to obtain the Primary Cluster Name Identity token.
The text for the associated error code is: An attempt has been made to operate on an impersonation token by a thread that is not currently impersonating a client.
The cluster identity 'CLUSTER$' may lack permissions required to update the object. Please work with your domain administrator to ensure that the cluster identity can update computer objects in the domain.