Share via

The Computer (name) does not have the failover clustering feature installed.

  • Article

Question

Tuesday, February 5, 2013 5:02 PM

Have 2 servers running Server 2008 R2 service pack 1.  Both have failover cluster feature installed.  When I go to validate a configurations, I try to add the other server and it always replies with the same error. 

Event id 4631.

Failover cluster manager detected a parameter that was not in the expected range: the computer (name) does not have the failover clustering feature installed.

But both have the feature installed.  They can ping each other, on the same domain, same hardware and software setup.  Ive tried removing the feature and re-adding it and rebooting, but nothing seems to correct the issue.

Any help would be great.

THank you

All replies (6)

Wednesday, February 6, 2013 3:36 PM ✅Answered

Sorry to say none of the suggestions worked.  I did fix the issue. For now.  I reinstalled Server 2008 R2 Enterprise on both.  But this time build the cluster with only installing the Failover Feature, renaming, add to domain.  No update's and no other software installed.

For now its fixed, but as I patch and put software on I'll keep an eye on it to see if any of those things break it.

But thank you all for your help.

Matthew Anderson

Tuesday, February 5, 2013 6:20 PM

Are you sure your DNS is good?  Maybe you have an address on one of the cluster nodes that is already assigned in DNS to another node.  As a result, you may be pinging the right address, but it might be going to the wrong machine.

Try issuing the following PowerShell command to the two nodes of the cluster, then do the same to the names of the cluster nodes.  They should match.

# Get system information by IP
gwmi Win32_ComputerSystem -Computername <your ip addr>

# Get system information by DNS
gwmi Win32_ComputerSystem -Computername <Computername>

.:|:.:|:. tim

Tuesday, February 5, 2013 6:31 PM

Tried that, they all return with the correct info.  The DNS names match the IP addresses.

Wednesday, February 6, 2013 3:13 AM

If not DNS, then check WMI. Ensure WMI service is running on both nodes. Then review the following article for a list of steps you can go through to test/repair WMI:

http://blogs.msdn.com/b/clustering/archive/2010/11/23/10095621.aspx

Visit my blog about multi-site clustering

Wednesday, February 6, 2013 7:21 AM

Hi,

> Have 2 servers running Server 2008 R2 service pack 1. 

What’s the server Edition? Enterprise edition or Datacenter Edition? The failover cluster feature is not available in Windows Web Server 2008 R2 or Windows Server 2008 R2 Standard.

You may refer to following steps to troubleshoot this issue:

  1. Ensure it is not a DNS Issue
  2. Check that WMI is Running on the Node
  3. Check Firewall Settings
  4. Reboot the Node
  5. Rebuild a Corrupt WMI Repository
  6. Patch WMI for Performance Improvements

For more information please refer to following MS articles:

Trouble Connecting to Cluster Nodes? Check WMI!
http://blogs.msdn.com/b/clustering/archive/2010/11/23/10095621.aspx
What's New in Failover Clusters
http://technet.microsoft.com/en-us/library/dd443539(v=ws.10).aspx

Lawrence

TechNet Community Support

Tuesday, November 5, 2013 11:09 AM

I had this very same issue an hour ago. Even when pinging the DNS name of the machine, the IP was the correct one, it turns out that I had two A records with the same IP in the DNS server, as the machine was previously an ESX server but was rebuilt.

It worked for me after I deleted the duplicated A record.