System error 1460 has occurred (0x000005b4). when trying to create two-node cluster in R2

Question

I'm trying to create a brand new two node Windows 2008 R2 Enterprise 64bit cluster.  When I try with the GUI I get the following:
An error occurred while creating the cluster.
An error occurred creating cluster 'printcluster'.
This operation returned because the timeout period expired
When I try via command prompt using the following command:
cluster /cluster:PrintServices /create /nodes:"node1 node2" /ipaddr:10.9.11.194/255.255.255.0
I get the following:
  4% Initializing Cluster PrintServices.
  9% Validating cluster state on node <node1>.
 13% Searching the domain for computer object PrintServices
 18% Creating a new computer object for PrintServices in the domain
 22% Configuring computer object PrintServices as cluster name object
 27% Validating installation of the Microsoft Failover Cluster Virtual Adapter on node <node1>.
 31% Validating installation of the Cluster Disk Driver on node <node1>.
 36% Configuring Cluster Service on node <node1>.
 40% Validating installation of the Microsoft Failover Cluster Virtual Adapter on node <node2>.
 45% Validating installation of the Cluster Disk Driver on node <node2>.
 50% Configuring Cluster Service on node <node2>.
 54% Starting Cluster Service on node <node1>.
 54% Starting Cluster Service on node <node2>.
 59% Forming cluster PrintServices.This phase has failed for Cluster object 'PrintServices' with an error status of 1460 (0x000005B4).
Cleaning up <node1>.
Cleaning up <node2>.
Cleaning up PrintServices.
When I run a Cluster validation, I get 100% Green, no errors.
My disks are SAN Attached.
I have other Windows 2008 non-R2 clusters that never had this problem...  Any ideas?
-PaulPaul S

Answer 1

Hi Paul,
I suggest trying the following steps to troubleshoot this issue:
1.  Open Registry Editor. 
2.  Locate the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318} 
3.  Under this subkey, find the subkey that holds a DriverDesc string value entry whose value is "Microsoft Failover Cluster Virtual Adapter." 
4.  Under the subkey that you found in step 3, add the following string value registry entry:
Name: DatalinkAddress
Value data: 02-AA-BB-CC-DD-01
5.  Restart the computer. 
6.  Repeat step 1 through step 5 on other computers on which you experience this problem. When you do this on other computers, replace the value data of the registry with different values in order to set a unique value for each node. For example, set the value on the second node to 02-AA-BB-CC-DD-02, and set value on the third node to 02-AA-BB-CC-DD-03. If you notice this behavior on distinct clusters, make sure that you use an address for each node that is unique across all clusters. 
7.  On each computer that you want to make a cluster node, use the Server Manager console to remove the Failover Clustering feature. 
8.  Restart each computer from which you have removed the Failover Clustering feature. 
9.  Add the Failover Clustering feature on all these computers again. 
10.  Run cluster validation against these computers. 
11.  Try creating a cluster. 
If the issue persists, please let me know what errors are logged in Event Logs.
Tim Quan - MSFT