Failover Cluster creation fails 2012R2

Create Cluster
Cluster: FailoverCluster
Node: WS2012R2-2.yottabyte.inc
Node: WS2012R2-1.yottabyte.inc
IP Address: DHCP address on 192.168.136.0/24
Started 3/31/2015 11:48:52 PM
Completed 3/31/2015 11:52:13 PM
Beginning to configure the cluster FailoverCluster.
Initializing Cluster FailoverCluster.
Validating cluster state on node WS2012R2-2.yottabyte.inc.
Find a suitable domain controller for node WS2012R2-2.yottabyte.inc.
Searching the domain for computer object 'FailoverCluster'.
Bind to domain controller \\WS2012R2-1.yottabyte.inc.
Check whether the computer object FailoverCluster for node WS2012R2-2.yottabyte.inc exists in the domain. Domain controller \\WS2012R2-1.yottabyte.inc.
Computer object for node WS2012R2-2.yottabyte.inc does not exist in the domain.
Creating a new computer account (object) for 'FailoverCluster' in the domain.
Check whether the computer object WS2012R2-2 for node WS2012R2-2.yottabyte.inc exists in the domain. Domain controller \\WS2012R2-1.yottabyte.inc.
Creating computer object in organizational unit CN=Computers,DC=yottabyte,DC=inc where node WS2012R2-2.yottabyte.inc exists.
Create computer object FailoverCluster on domain controller \\WS2012R2-1.yottabyte.inc in organizational unit CN=Computers,DC=yottabyte,DC=inc.
Check whether the computer object FailoverCluster for node WS2012R2-2.yottabyte.inc exists in the domain. Domain controller \\WS2012R2-1.yottabyte.inc.
Configuring computer object 'FailoverCluster in organizational unit CN=Computers,DC=yottabyte,DC=inc' as cluster name object.
Get GUID of computer object with FQDN: CN=FAILOVERCLUSTER,CN=Computers,DC=yottabyte,DC=inc
Validating installation of the Network FT Driver on node WS2012R2-2.yottabyte.inc.
Validating installation of the Cluster Disk Driver on node WS2012R2-2.yottabyte.inc.
Configuring Cluster Service on node WS2012R2-2.yottabyte.inc.
Validating installation of the Network FT Driver on node WS2012R2-1.yottabyte.inc.
Validating installation of the Cluster Disk Driver on node WS2012R2-1.yottabyte.inc.
Configuring Cluster Service on node WS2012R2-1.yottabyte.inc.
Waiting for notification that Cluster service on node WS2012R2-2.yottabyte.inc has started.
Forming cluster 'FailoverCluster'.
Unable to successfully cleanup.
An error occurred while creating the cluster and the nodes will be cleaned up. Please wait...
An error occurred while creating the cluster and the nodes will be cleaned up. Please wait...
There was an error cleaning up the cluster nodes. Use Clear-ClusterNode to manually clean up the nodes.
There was an error cleaning up the cluster nodes. Use Clear-ClusterNode to manually clean up the nodes.
An error occurred while creating the cluster.
An error occurred creating cluster 'FailoverCluster'.
This operation returned because the timeout period expired
To troubleshoot cluster creation problems, run the Validate a Configuration wizard on the servers you want to cluster.
While creating cluster I am getting this error? Any solution please.
Thank You

Did you follow the instruction "To troubleshoot cluster creation problems, run the Validate a Configuration wizard on the servers you want to cluster"? Any warnings/errors?
. : | : . : | : . tim

Similar Messages

Hyper-V 2012 R2 Cluster Creation Fails

I am trying to create a 2 Node Hyper-v 2012 R2 Cluster. The Cluster Validation passes with no errors or warnings but the the cluster creation fails.
The error is similar to
here .
In this case he solved it by joining the Nodes to a Windows 2012 Domain. We don't have that option in our environment.
In the System Logs Events 7024 The cluster service terminated... The cluster join operation failed, and 7031 Cluster Services Terminated unexpectedly.
Anyone have an idea?
Todd

Hi Todd,
For troubleshooting , please try to create a new OU then move cluster nodes computer to that new OU then block inheritance , restart the nodes .
After this try to use domain admin account logon the cluster nodes to build cluster again .
Best Regards,
Elton Ji
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

Failover Cluster disk failed on a VM.

Hello,
I tried to create a Failover cluster node on a VM (with a virtual disk with fixed size).
All the step are ok except disk storage Add.
When I try to Add a disk, the following error appears :
Status : Failed.
Information : Incorrect function.
Error Code : 0X80070001.
Does anyone know if it's possible to add a V-disk Hyper-V on a cluster node ?
Thanks,
Regards,

What version of Hyper-V are you running?
It sounds like you are trying to use shared vhdx. Note, the shared disk MUST be vhdx.
http://technet.microsoft.com/en-us/library/dn265980.aspx
http://technet.microsoft.com/en-us/library/dn281956.aspx
. : | : . : | : . tim

Cluster Creation Failed with Ambari AppManager

Hi,
I am getting this error when creating cluster
(cluster create --name hdp --distro HDP-1.3.2 --appManager Ambari --networkName Hadoop_NW)
serengeti>appmanager list
NAME DESCRIPTION TYPE URL
Default Default application manager Default
ambari AmbariServer Ambari http://10.6.55.239:8080
==========================
It seems that agent on the host is not able to connect to the server but the problem is the Ambari Server is not located at localhost:8080 how can i change it to ambari server's address.
Running setup agent script...
==========================
{'exitstatus': 1, 'log': "Host registration aborted. Ambari Agent host cannot reach Ambari Server 'localhost:8080'. Please check the network connectivity between the Ambari Agent host and the Ambari Server"}
Connection to node1.hadooptest.com closed.
SSH command execution finished
host=node1.hadooptest.com, exitcode=1
ERROR: Bootstrap of host node1.hadooptest.com fails because previous action finished with non-zero exit code (1)
ERROR MESSAGE: tcgetattr: Invalid argument
Connection to node1.hadooptest.com closed.
STDOUT: {'exitstatus': 1, 'log': "Host registration aborted. Ambari Agent host cannot reach Ambari Server 'localhost:8080'. Please check the network connectivity between the Ambari Agent host and the Ambari Server"}
Connection to node1.hadooptest.com closed.

Hi Qing,
Thanks for the solution its solved the earlier problem but now i got a new one. According to the error Failed to start ping port listener of:[Errno 98] Address already in use" This the only address on the lan .... what can be causing this issue ?
Mohsin
The failed nodes: 1
[NAME] hdp2-worker-0
[STATUS] VM Ready
[Error Message] ==========================
Copying common functions script...
==========================
scp /usr/lib/python2.6/site-packages/common_functions
host=node5.hadooptest.com, exitcode=0
==========================
Copying OS type check script...
==========================
scp /usr/lib/python2.6/site-packages/ambari_server/os_check_type.py
host=node5.hadooptest.com, exitcode=0
==========================
Running OS type check...
==========================
Cluster primary/cluster OS type is redhat6 and local/current OS type is redhat6
Connection to node5.hadooptest.com closed.
SSH command execution finished
host=node5.hadooptest.com, exitcode=0
==========================
Checking 'sudo' package on remote host...
==========================
sudo-1.8.6p3-12.el6.x86_64
Connection to node5.hadooptest.com closed.
SSH command execution finished
host=node5.hadooptest.com, exitcode=0
==========================
Copying repo file to 'tmp' folder...
==========================
scp /etc/yum.repos.d/ambari.repo
host=node5.hadooptest.com, exitcode=0
==========================
Moving file to repo dir...
==========================
Connection to node5.hadooptest.com closed.
SSH command execution finished
host=node5.hadooptest.com, exitcode=0
==========================
Copying setup script file...
==========================
scp /usr/lib/python2.6/site-packages/ambari_server/setupAgent.py
host=node5.hadooptest.com, exitcode=0
==========================
Running setup agent script...
==========================
Restarting ambari-agent
Verifying Python version compatibility...
Using python /usr/bin/python2.6
Found ambari-agent PID: 1682
Stopping ambari-agent
Removing PID file at /var/run/ambari-agent/ambari-agent.pid
ambari-agent successfully stopped
Verifying Python version compatibility...
Using python /usr/bin/python2.6
Checking for previously running Ambari Agent...
Starting ambari-agent
Verifying ambari-agent process status...
ERROR: ambari-agent start failed
Agent out at: /var/log/ambari-agent/ambari-agent.out
Agent log at: /var/log/ambari-agent/ambari-agent.log
('INFO 2015-04-01 06:19:59,137 HostCheckReportFileHandler.py:109 - Creating host check file at /var/lib/ambari-agent/data/hostcheck.result
INFO 2015-04-01 06:19:59,205 Controller.py:211 - No commands sent from the Server.
INFO 2015-04-01 06:20:09,207 Heartbeat.py:76 - Sending heartbeat with response id: 1 and timestamp: 1427869209207. Command(s) in progress: False. Components mapped: False
INFO 2015-04-01 06:20:09,251 Controller.py:211 - No commands sent from the Server.
INFO 2015-04-01 06:20:19,252 Heartbeat.py:76 - Sending heartbeat with response id: 2 and timestamp: 1427869219252. Command(s) in progress: False. Components mapped: False
INFO 2015-04-01 06:20:19,296 Controller.py:211 - No commands sent from the Server.
INFO 2015-04-01 06:20:29,296 Heartbeat.py:76 - Sending heartbeat with response id: 3 and timestamp: 1427869229296. Command(s) in progress: False. Components mapped: False
INFO 2015-04-01 06:20:29,340 Controller.py:211 - No commands sent from the Server.
INFO 2015-04-01 06:20:39,340 Heartbeat.py:76 - Sending heartbeat with response id: 4 and timestamp: 1427869239340. Command(s) in progress: False. Components mapped: False
INFO 2015-04-01 06:20:39,384 Controller.py:211 - No commands sent from the Server.
INFO 2015-04-01 06:20:49,384 Heartbeat.py:76 - Sending heartbeat with response id: 5 and timestamp: 1427869249384. Command(s) in progress: False. Components mapped: False
INFO 2015-04-01 06:20:49,428 Controller.py:211 - No commands sent from the Server.
INFO 2015-04-01 06:20:59,429 Heartbeat.py:76 - Sending heartbeat with response id: 6 and timestamp: 1427869259429. Command(s) in progress: False. Components mapped: False
INFO 2015-04-01 06:21:05,061 main.py:83 - loglevel=logging.INFO
INFO 2015-04-01 06:21:10,870 main.py:83 - loglevel=logging.INFO
INFO 2015-04-01 06:21:10,871 DataCleaner.py:36 - Data cleanup thread started
INFO 2015-04-01 06:21:10,875 DataCleaner.py:71 - Data cleanup started
INFO 2015-04-01 06:21:10,876 DataCleaner.py:73 - Data cleanup finished
ERROR 2015-04-01 06:21:10,877 PingPortListener.py:44 - Failed to start ping port listener of:[Errno 98] Address already in use
INFO 2015-04-01 06:21:10,877 PingPortListener.py:52 - Ping port listener killed
', None)
Connection to node5.hadooptest.com closed.
SSH command execution finished
host=node5.hadooptest.com, exitcode=255
ERROR: Bootstrap of host node5.hadooptest.com fails because previous action finished with non-zero exit code (255)
ERROR MESSAGE: tcgetattr: Invalid argument
Connection to node5.hadooptest.com closed.
STDOUT: Restarting ambari-agent
Verifying Python version compatibility...
Using python /usr/bin/python2.6
Found ambari-agent PID: 1682
Stopping ambari-agent
Removing PID file at /var/run/ambari-agent/ambari-agent.pid
ambari-agent successfully stopped
Verifying Python version compatibility...
Using python /usr/bin/python2.6
Checking for previously running Ambari Agent...
Starting ambari-agent
Verifying ambari-agent process status...
ERROR: ambari-agent start failed
Agent out at: /var/log/ambari-agent/ambari-agent.out
Agent log at: /var/log/ambari-agent/ambari-agent.log
('INFO 2015-04-01 06:19:59,137 HostCheckReportFileHandler.py:109 - Creating host check file at /var/lib/ambari-agent/data/hostcheck.result
INFO 2015-04-01 06:19:59,205 Controller.py:211 - No commands sent from the Server.
INFO 2015-04-01 06:20:09,207 Heartbeat.py:76 - Sending heartbeat with response id: 1 and timestamp: 1427869209207. Command(s) in progress: False. Components mapped: False
INFO 2015-04-01 06:20:09,251 Controller.py:211 - No commands sent from the Server.
INFO 2015-04-01 06:20:19,252 Heartbeat.py:76 - Sending heartbeat with response id: 2 and timestamp: 1427869219252. Command(s) in progress: False. Components mapped: False
INFO 2015-04-01 06:20:19,296 Controller.py:211 - No commands sent from the Server.
INFO 2015-04-01 06:20:29,296 Heartbeat.py:76 - Sending heartbeat with response id: 3 and timestamp: 1427869229296. Command(s) in progress: False. Components mapped: False
INFO 2015-04-01 06:20:29,340 Controller.py:211 - No commands sent from the Server.
INFO 2015-04-01 06:20:39,340 Heartbeat.py:76 - Sending heartbeat with response id: 4 and timestamp: 1427869239340. Command(s) in progress: False. Components mapped: False
INFO 2015-04-01 06:20:39,384 Controller.py:211 - No commands sent from the Server.
INFO 2015-04-01 06:20:49,384 Heartbeat.py:76 - Sending heartbeat with response id: 5 and timestamp: 1427869249384. Command(s) in progress: False. Components mapped: False
INFO 2015-04-01 06:20:49,428 Controller.py:211 - No commands sent from the Server.
INFO 2015-04-01 06:20:59,429 Heartbeat.py:76 - Sending heartbeat with response id: 6 and timestamp: 1427869259429. Command(s) in progress: False. Components mapped: False
INFO 2015-04-01 06:21:05,061 main.py:83 - loglevel=logging.INFO
INFO 2015-04-01 06:21:10,870 main.py:83 - loglevel=logging.INFO
INFO 2015-04-01 06:21:10,871 DataCleaner.py:36 - Data cleanup thread started
INFO 2015-04-01 06:21:10,875 DataCleaner.py:71 - Data cleanup started
INFO 2015-04-01 06:21:10,876 DataCleaner.py:73 - Data cleanup finished
ERROR 2015-04-01 06:21:10,877 PingPortListener.py:44 - Failed to start ping port listener of:[Errno 98] Address already in use
INFO 2015-04-01 06:21:10,877 PingPortListener.py:52 - Ping port listener killed
', None)
Connection to node5.hadooptest.com closed.
cluster hdp2 resume failed: Task execution failed: An exception happens when App_Manager (Ambari) creates the cluster: (hdp2). Creation fails..

Win Server 2012 Failover Cluster - Error: Failed to bring cluster disk online

Hi Technet
I'm currently running running 2 VMs Win Server 2012 and would like to test Failover Clustering for one of our FTP server
I've added on both servers an additional partition, formatted and Online
One of the drives comes Online but cannot bring the 2nd disk online from the cluster manager
Error: failed to bring resource online - clustered storage is not connected to the node
Assistance would be greatly appreciated
Thank you
Jabu

Hi jsibeko,
Since the VMware offer the MSCS shared storage solution themselves, I suggest you first ask VMware whether that shared storage is supported with your vSphere edition, I found
some VMware KB about the VMware shared storage for MSCS, may you can get more tips.
The VMware KB:
Microsoft Clustering on VMware vSphere: Guidelines for supported configurations (1037959)
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1037959
Microsoft Cluster Service (MSCS) support on ESXi/ESX (1004617)
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004617
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Failover Cluster Wizard Fails

I am trying to create a cluster with two Windows Server 2012 nodes on an existing domain where the domain controller is Windows 2003, and the wizard fails with the message:
Set password on (ClusterName). There are currently no logon servers available to service the logon request.
An error occurred while creating the cluster and the nodes will be cleaned up. Please wait..
There was an cleaning up the cluster node. Use Clear-ClusterNode to manually clean up the nodes.

I found the reason. The port 464 TCP and UDP were blocked by windows 2003 firewall. Windows server 2012 by default leaves these ports open, but you should manually open them on windows server 2003.

Failover cluster for BizTalk 2010

Hi friends,
I need to understand step by step configuration for failover for biztalk 2010.
use of failover cluster manager from windows os and how its working from biztalk.
Please do share with me the right url.
Thanks all.

Similar question was asked recently in our forum:
http://social.msdn.microsoft.com/Forums/en-US/18239da7-74f2-45a7-b984-15f1b3f27535/biztalk-clustering?forum=biztalkgeneral#4074a082-8459-420f-8e99-8bab19c8fba2
White paper from Microsoft on this context shall you with step-by-step guidance of failover cluster for BizTalk 2010.
http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=2290
Also refer this blog where authors in series of his post guides with the steps required:
Part 1: BizTalk High Availability Server Environment – Preparations
Part 2: BizTalk High Availability Server Environment–Domain Controller Installation
Part 3: BizTalk High Availability Server Environment – SQL & BizTalk Active Directory Accounts
Part 4: BizTalk High Availability Server Environment – Prepping our SQL & BizTalk Failover Clusters
Part 5: BizTalk High Availability Server Environment – SQL Server 2008r2 Failover Cluster
Part 6: BizTalk High Availability Server Environment–BizTalk 2010 Failover Cluster Creation
Part 7 – BizTalk High Availability Server Environment –BizTalk 2010 Installation, Configuration
and Clustering
Par 8 - Adding Network Load balancing to our High Availability Environment
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Failover cluster manager

Hi Guys,
I am getting below error message while validate a configuration of failover cluster manager.
I have checked services and cluster services are started. I have rebooted both the cluster server, but still getting the same error message. Any further help will be appreciated.
Thanks

Thanks Philip,
I already tried to run FCM as admin, but got same error message.
In the event viewer Failover cloustering manager below is the error that I have noted.
Log Name:      Microsoft-Windows-FailoverClustering-Manager/Admin
Source:        Microsoft-Windows-FailoverClustering-Manager
Date:          6/3/2014 6:45:53 AM
Event ID:      4683
Task Category: Failover Clusters Manager MMC Snapin
Level:         Error
Keywords:
Description:
Failover Cluster Manager failed while managing one or more cluster. The error was 'There is an error in XML document (5, 73).'. For more information see the Failover Cluster Manager Diagnostic channel.

Guest VM failover cluster on Hyper-V 2012 Cluster does not work across hosts

Hi all,
We are evaluating Hyper-V on Windows Server 2012, and I have bumped in to this problem:
I have a Exchange 2010SP2 DAG installed on 2 vms in our Hyper-V cluster (a DAG forms a failover cluster, but does not use any shared storage). As long as my vms are on the same host, all is good. However, if I live migrate or shutdown-->move-->start one
of the guest nodes on another pysical host, it loses connectivity with the cluster. "regular" network is fine across hosts, and I can ping/browse one guest node from the other. I have tried looking for guidance for Exchange on Hyper-V clusters but have not
been able to find anything.
According to the Exchange documentation this configuration is supported, so I guess I'm asking for any tips and pointers on where to troubleshoot this.
regards,
Trond

Hi All,
so some updates...
We have a ticket logged with Microsoft, more of a check box exercise to reassure the business we're doing the needful. Anyway, they had us....
Apply hotfix http://support.microsoft.com/kb/2789968?wa=wsignin1.0 to both guest DAG nodes, which seems pretty random, but they wanted to update the TCP/IP stack...
There was no change in error, move guest to another Hyper-V node, and the failover cluster, well, fails with the following event ids I the node that fails...
1564 -File share witness resource 'xxxx)' failed to arbitrate for the file share 'xxx'. Please ensure that file share '\xxx' exists and is accessible by the cluster..
1069 - Cluster resource 'File Share Witness (xxxxx)' in clustered service or application 'Cluster Group' failed
1573 - Node xxxx failed to form a cluster. This was because the witness was not accessible. Please ensure that the witness resource is online and available
The other node stays up, and the Exchange DB's mounted on that node stay up, the ones mounted on the way that fails failover to the remaining node...
So we then
Removed 3 x Nic's in one of the 4 x NIC teams, so, leaving a single NIC in the team (no change)
Removed one NIC from the LACP group on each Hyper-V host
Created new Virtual Switch using this simple trunk port NIC on each Hyper-V host
Moved the DAG nodes to this vSwitch
Failover cluster works as expected, guest VM's running on separate Hyper-V hosts, when on this vswitch with single NIC
So Microsoft were keen to close the call, as there scope was, I kid you not, to "consider this issue
resolved once we are able to find the cause of the above mentioned issue", which we have now done, as in, teaming is the cause... argh.
But after talking, they are now escalating internally.
The other thing we are doing, is building Server 2010 Guests, and installing Exchange 2010 SP3, to get a Exchange 2010 DAG running on Server 2010 and see if this has the same issue, as people indicate that this is perhaps not got the same problem.
Cheers
Ben
Name                   : Virtual Machine Network 1
Members                : {Ethernet, Ethernet 9, Ethernet 7, Ethernet 12}
TeamNics               : Virtual Machine Network 1
TeamingMode            : Lacp
LoadBalancingAlgorithm : HyperVPort
Status                 : Up
Name                   : Parent Partition
Members                : {Ethernet 8, Ethernet 6}
TeamNics               : Parent Partition
TeamingMode            : SwitchIndependent
LoadBalancingAlgorithm : TransportPorts
Status                 : Up
Name                   : Heartbeat
Members                : {Ethernet 3, Ethernet 11}
TeamNics               : Heartbeat
TeamingMode            : SwitchIndependent
LoadBalancingAlgorithm : TransportPorts
Status                 : Up
Name                   : Virtual Machine Network 2
Members                : {Ethernet 5, Ethernet 10, Ethernet 4}
TeamNics               : Virtual Machine Network 2
TeamingMode            : Lacp
LoadBalancingAlgorithm : HyperVPort
Status                 : Up
A Cloud Mechanic.

Cold failover cluster for repository ?

Hi,
We have Box A (infra and mid) and B(mid),
we want to use Box B for cold failover claster
Any suggestion on how to do this?
TIA

Similar question was asked recently in our forum:
http://social.msdn.microsoft.com/Forums/en-US/18239da7-74f2-45a7-b984-15f1b3f27535/biztalk-clustering?forum=biztalkgeneral#4074a082-8459-420f-8e99-8bab19c8fba2
White paper from Microsoft on this context shall you with step-by-step guidance of failover cluster for BizTalk 2010.
http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=2290
Also refer this blog where authors in series of his post guides with the steps required:
Part 1: BizTalk High Availability Server Environment – Preparations
Part 2: BizTalk High Availability Server Environment–Domain Controller Installation
Part 3: BizTalk High Availability Server Environment – SQL & BizTalk Active Directory Accounts
Part 4: BizTalk High Availability Server Environment – Prepping our SQL & BizTalk Failover Clusters
Part 5: BizTalk High Availability Server Environment – SQL Server 2008r2 Failover Cluster
Part 6: BizTalk High Availability Server Environment–BizTalk 2010 Failover Cluster Creation
Part 7 – BizTalk High Availability Server Environment –BizTalk 2010 Installation, Configuration
and Clustering
Par 8 - Adding Network Load balancing to our High Availability Environment
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Failover Cluster Network Name Failed and Can't be Repaired

I have an issue that seem to be a different problem than any others have encountered.
I've scoured everything I can find and nothing has fixed my problem.
The problem starts with the common problem of the cluster network name failing on my 2 node server 2012 file server cluster. The computer object was still in AD and appeared to be fine so it was not the common problem of the object
getting deleted somehow. At the time, there was no other object with that name in the recycling bin, so I don't think it was mistakenly deleted and quickly recreated to cover any tracks, so to speak.
Following one guide, I tried to find the registry key that corresponded with the GUID of the object, but neither node in the cluster had it in its registry (which may be part of the problem).
Since it was in the failed state, I tried to do the repair on the object to no avail.
We run a "locked down" DC environment so all computer objects have to be pre-provisioned. They were all pre-provisioned successfully and successfully assigned during cluster creation. The cluster was running with no issues for a month
or so before this problem came up.
When I do a repair on the object while taking diagnostic logs the following 4609 error appears:
The action 'Repair' did not complete. - System.ApplicationException: An error occurred resetting the password for 'Cluster Name'. ---> System.ComponentModel.Win32Exception: Unknown error (0x80005000)
There appears to be a corresponding 4771 error with a failure code 0x18 that comes from the security log of the DC that states there was a Kerberos pre-authentication failure for the cluster network name object (Domain\Clustername$)
I believe this is what is causing the repair failure. All the information I found related to security error 4771 was either a bad credentials given for a user account or the fix was to reconnect the computer to the domain. I can't seem to find
a way to do this with the cluster network name. If there's a way please let me know.
I've tried a number of things, like resetting the object, disabling it, deleting and creating a new object with the same name, deleting that new object and recovering the original, etc...
Can anyone shed some light on what is going on and hopefully how to fix it other than rebuilding the cluster? I'm quite close to just tearing it down and building it back up but am hesitant because this cluster in currently in production...
Any help would be appreciated

Hi,
I don’t find out the similar issue with yours, base on my experience, the 4096 error
often caused by the CSV disk issue, and the 0x80005000 error some time caused by the repetitive computer object in OU. Please check the above related part or run the validate test then post the error information.
Although I do have a CSV, there doesn't seem to be any problems with it and it was running just fine for a month or so before the problem started. I double checked and there is no duplicate computer objects, maybe I don't understand what you mean by
repetitive, could you explain further?
The cluster validates successfully with a few warnings:
Validating cluster resource Name: DT-FileCluster.
This resource is marked with a state of 'Failed' instead of
'Online'. This failed state indicates that the resource had a problem either
coming online or had a failure while it was online. The event logs and cluster
logs may have information that is helpful in identifying the cause of the
failure.
- This is because the cluster name is in the failed state
Validating the service principal names for Name:
DT-FileCluster.
The network name Name: DT-FileCluster does not have a valid
value for the read-only property 'ObjectGUID'. To validate the service principal
name the read-only private property 'ObjectGuid' must have a valid value. To
correct this issue make sure that the network name has been brought online at
least once. If this does not correct this issue you will need to delete the
network name and re-create it.
- This is definitely related to the problem and the GUID probably got removed when we attempted a fix by resetting the object and trying the repair from the failover cluster manager.
The user running validate, does not have permissions to create
computer objects in the 'ad.unlv.edu' domain.
- This is correct, we run a restricted domain. I have a delegated OU that I can pre-provision accounts in. The account was pro-provisioned successfully and was at one point setup and working just fine.
There are no other errors nor warnings.

Windows Server 2012R2 Failover Cluster error with mounted volumes

Hi all,
I've a problem with mounted volume on a WSFC build on top of Windows Server 2012R2, the situation is:
M: is the volume hosting mounting points
disk-1, disk-2, disk-3 are volume mounted on M:\SomeFolder
Theese volumes are used by a SQL Server Failover Cluster Instance, but my problem is related to WSFC. I've set dependencies so disk-1, disk-2, disk-3 depend upon H:
If I try a failover of the role "SQL Server" I observe that when the disk come online in the other node they fail with this error:
Cluster resource 'disk-1' of type 'Physical Disk' in clustered role 'SQL Server (ISQL2014A)' failed. The error code was '0xaa' ('The requested resource is in use.').
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster
Manager or the Get-ClusterResource Windows PowerShell cmdlet.
If I manually take offline H: and than bring it online and then manually take online all disk (1 to 3) they come online with no error.
I'm going crazy!

I've found the root of the problem: the servers are virtual machine on a VMware ESX 5.5 infrastructure, VMware claims that on 5.5 multipath is supported for raw device mapping disks but disabling multipath (I've set to fixed path) the Windows Server Failover
Cluster stops to get problems.
Now we have opened a support call with VMware.

The Cluster Service function call 'ClusterResourceControl' failed with error code '1008(An attempt was made to reference a token that does not exist.)' while verifying the file path. Verify that your failover cluster is configured properly.

I am experiencing this error with one of our cluster environment. Can anyone help me in this issue.
The Cluster Service function call 'ClusterResourceControl' failed with error code '1008(An attempt was made to reference a token that does not exist.)' while verifying the file path. Verify that your failover cluster is configured properly.
Thanks,
Venu S.
Venugopal S ----------------------------------------------------------- Please click the Mark as Answer button if a post solves your problem!

Hi Venu S,
Based on my research, you might encounter a known issue, please try the hotfix in this KB:
http://support.microsoft.com/kb/928385
Meanwhile since there is less information about this issue, before further investigation, please provide us the following information:
The version of Windows Server you are using
The result of SELECT @@VERSION
The scenario when you get this error
If anything is unclear, please let me know.
Regards,
Tom Li

SQL Server Agent fails to connect to DB after enabling mirror on failover cluster

Hello:
We have multiple databases running in a Failover Cluster instance: SQL 2012SP1 on Server 2008 R2 failover cluster (NOT AlwaysOn). We are trying to add a high-performance mirror in a standalone instance for DR. My understanding is that should be a perfectly
normal, supported configuration.
The mirroring is working properly; however, the clustered SQL Server agent is unable to run jobs that run in the mirrored databases.
We get the following in the job log: Unable to connect to SQL Server 'VIRTUALSERVERNAME\INSTANCE'. The step failed.
There is a partner message in the agent log: [165] ODBC Error: 0, Connecting to a mirrored SQL Server instance using the MultiSubnetFailover connection option is not supported. [SQLSTATE IMH01]
The cluster is not a mulitsubnet cluster. All hosts are connected to the same subnets and there is no storage replication. I can not find any place where I can adjust the connect string options for SQL Agent.
Any guidance or suggestions on how to resolve this would be appreciated.
~joe

SQL Team - MSFT:
Thank you for taking the time to research and provide a clear answer.
This seems very much a workaround and very unsatisfactory.
You are correct, there is an IP dependency with OR condition. Moving to an AND condition is not viable for us. The whole point is to provide network redundancy. With an AND condition, if EITHER network interface fails, the service will go offline or fail
to come online without manual intervention. This is arguably worse for uptime than having a single interface available.
We are in process of rewriting all our SQL jobs to start in tempdb before transitioning to the appropriate target database. If this works for all of our jobs, I will mark the above response as answer.
Again, thank you for the answer.
Regards,
Joe M.

Windows server 2012 failover cluster error: Cluster resource 'Virtual Machine Configuration ... of type 'Virtual machine configuration in clustered role ... failed.

I have two windows 2012 host server that are clustered using windows failover cluster feature. Each server is hosting four VMs. When migrating from Host2 to Host1, the migration failed with the following error:
Cluster resource 'Virtual Machine Configuration SCPCSQLSRV01' of type 'Virtual Machine Configuration' in clustered role 'SCPCSQLSRV01' failed. The error code was '0x569' ('Logon failure: the user has not been granted the requested logon type at this computer.').
When this happens, the VM that I was migrating can no longer be started even on the original host. The only remedy is to restart the host server.
Any suggestion on resolving this problem?
Thanks
Ikad

Thanks. The article referred to above gives the solution to my issue. There is a group policy that is applied to the OU where the host servers were placed. Doing gpupdate /force temporarily removes the problem. Unfortunately the NT Virtual Machine\Virtual
Machines account is a special account that cannot be added like other accounts and granted the log on as a service right. The thread
http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/d56f2eae-726e-409a-8813-670a406593e8 contains how it can be added which is by creating a group and running the command
Net localgroup VMTest “NT Virtual Machine\Virtual Machines” /add
to add it to a local group VMTest. VMTest is then assigned the right to log on as a service.
Ikad

Failover Cluster creation fails 2012R2

Similar Messages

Maybe you are looking for