I have just created a Windows 2012 Failover cluster, and I am unable to add a Fileserver role. I attempted to do so today, and received the following errors (along with the status of failed on the role itself):

Event IDs:  1205, 1069, 1096, 1212.  I am most concerned about the last of the four event ID errors, included below:

Cluster network name resource 'fileserver' cannot be brought online. Attempt to locate a writeable domain controller (in domain unspecified domain) in order to create or update a computer object associated with the resource failed for the following reason:

The RPC Server is unavailable.

The error code was '1722'. Ensure that a writeable domain controller is accessible to this node within the configured domain. Also ensure that the DNS server is running in order to resolve the name of the domain controller.

Log  Name: System

Source: Microsoft-Windows-FailoverClustering

Event ID: 1212

Level: Error

User: SYSTEM

OpCode: Info

Logged: 2/12/2013 3:51:05PM

Task Category: Network Name Resource

Keywords:

Node:   CL-01.xxxx.nt.pitt.edu

It appears that I cannot write to the domain controller, yet earlier this same afternoon, I was able to write the actual cluster name to AD using the same DC. I can verify that the DC is up and running.

The DC is in a DMZ, firewalled from the Secure Server zone where the cluster nodes CL-01 and CL-02 are (this was a decision by our campus IT, and nothing I have control over). However, it was also the case when I created the cluster about two hours ago. And I was able to write the cluster into AD at that time, so nothing has changed in the meantime.

So what would possible cause the resource to not be created?  I tried pre-creating the computer object "fileserver" in AD, in the OU that was specified by the wizard, but that simply causes an error where the object already exists, and the wizard cannot continue.

A few minutes later, another 1212 error record appeared, similar to the one above but with one interesting difference:

"Cluster network name resource 'fileserver' cannot be brought online. Attempt to locate a writeable domain controller (in domain \\DC.xxxx.nt.pitt.edu) in order to create or update a computer object associated with the resource failed for the following reason"

Where DC is the name of my domain controller.

Is there a firewall rule that I'm still missing, but if so, why could I create the cluster (and hence, write the cluster computer object to AD?) and yet not be able to do this?

Final note:  I am logged into the two nodes as a cluster service account that is a domain admin and DOES have the right to add computer objects to the domain (hence the cluster was created inthe first place).

is there a way to upgrade a failover cluster (non HyperV) from 2008R2 to 2012?  We have a cluster that hosts a HA file share that we'd like to get to 2012.

Thanks

I am having an issues with my Exchange 2010 servers. I have two servers that have HUB/CAS/MAILBOX installed on them. They are configured to use DAG failover cluster.

I expereienced an issue recently where the DNS entry for the DAG and the MAIL01 server where missing from DNS on the Domain Controllers. I read online that a way to fix the issue was to recreate the DAG DNS and make sure it has special permissions so that the two mail servers can update the DNS entry. That didn't work. I also recreated the DNS entry for the MAIL01 server.

I can't remember the cluster . res command that I founs online that lists the clusters but when I ran the command it listed the cluster DAG twice.

On the Active Node of the Cluster I get the following events:

Log Name:      System
Source:        Microsoft-Windows-FailoverClustering
Date:          2/12/2013 9:09:03 AM
Event ID:      1196
Task Category: Network Name Resource
Level:         Error
Keywords:     
User:          SYSTEM
Computer:      MAIL01.domain.local
Description:
Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name(s) for the following reason:
DNS operation refused.
.

Ensure that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.
Event Xml:

Log Name:      System
Source:        Microsoft-Windows-FailoverClustering
Date:          2/12/2013 9:09:03 AM
Event ID:      1579
Task Category: Network Name Resource
Level:         Warning
Keywords:     
User:          SYSTEM
Computer:      MAIL01.domain.local
Description:
Cluster network name resource 'Cluster Name' failed to update the DNS record for name 'DAG.domain.local' over adapter 'MAPI'. The error code was 'DNS operation refused. (9005)'. Ensure that a DNS server is accessible from this cluster node and contact your DNS server administrator to verify the cluster identity can update the DNS record 'DAG.domain.local'.

I need some help with this issue and any suggestions would be wonderful.

Hi

Since cluster.exe is deprecated I'm searching for an equivalent powershell command.
Of course I can get the resource using get-resource or set any property of that resource, but I didn't found anything which immediately re-registers the Network Name.

Since I didn't find an answer inhttp://technet.microsoft.com/library/ee619744(v=WS.10).aspx nor in http://blogs.technet.com/b/josebda/archive/2010/09/24/mapping-cluster-exe-commands-to-windows-powershell-cmdlets-for-failover-clusters-extended-edition.aspx I hope I get an answer from this forum

Best regards

Pirmin

Hi,

i need study material for clustering services.Please any one help into this.

regards

mukilan.g

Hi All,

Running into this very odd issue with my Failover Cluster.

I'm running two Server 2012 (Node A and Node B) machines on the same domain (DC is virtual on a separate Server 2012 box) utilising a VM providing iSCSI storage on one of the Host Machines (Node A).

The Cluster Validation test passes with warnings on SCSI 3 Reservations and Network adapters not in use, allows to me to create the cluster fine. But the issue comes down to one way Live Migration Node A to Node B, flawless, Node B to node A "fail". Quick Migration Node B to Node A, flawless.

The error comes up stating that the connection was actively refused, which lead me to this article on Shared Nothing Live Migrations

http://blogs.technet.com/b/roplatforms/archive/2012/10/16/shared-nothing-migration-fails-0x8007274c.aspx

Which pointed out that Live Migrations happen over Port 6600 and recommended using a "netstat -a" to view what ports are actively in use.

Port 6600 comes up on node B but not node A. Thus explaining the one way live migration.

I tried restarting the Hyper V Virtualisation Management Services in Services, tried setting Hyper V Management Service to Automatic Delayed, Destroyed and remade the cluster, Uninstalled  and reinstalled Failover Cluster Manager, Uninstalled both Failover Cluster Manager and Hyper V reinstalled and nothing. For nothing will this port "Open". Tried manually setting a rule in Windows Firewall to open Port 6600 and nothing.

What the devil is going on here?

When I open the NIC Teaming gui on windows 2012 - the server host is showing as unmanageable.  Also the 4 NIC's are showing as "can not be added to team".  But the 4 nic's are not part of any other team.  Currently I do not have any teams configured. 

The NIC's have ip addresses and seem to be working properly other then the fact that I can not team them which I will need to do.  Can anyone figure this one out?

We're needing to upgrade our NIC's between iSCSI SAN and our 2008 R2 cluster nodes.  Current SAN network is using onboard 1GB NIC, but we're utilizing about 90% of the bandwidth during peak business.

What steps do we need to take to move the SAN network to the 10GB NIC's?  Is it as simple as removing the IP information from the existing NIC, disabling it, adding the same IP info to the 10GB NIC, then perform a graceful failover?

Hi all

I have a client who has a Windows 2008R2 functional level domain. They have Windows 2012 licences, but we don't want to upgrade to 2012 DC, etc just now. However, we want to convert their VMWare farm to HyperV 2012. The problem we have is that we cannot manage a 2012 cluster form 2008R2 server. Is there any way to get 2008 R2 to manage a Windows 2012 cluster? We would really rather leave the operational servers on 2008R2 now as many software vendors who have applications at this site are refusing to support the client if they upgrade to 2012.

We have rolled out several Hyper-V 2012 solutions now and we don't want to install HyperV 2008 R2 for obvious reasons.

Mark Dutton

Regards
Mark Dutton
Datamerge

Hello!

Organization use Exchange 2007 SP3 mailbox servers in SCC.
There are 4 active and 1 passive node in cluster.
All OS are Windows server 2008 Ent SP2.
All domain controllers OS Windows server 2008 Std SP2.
Cluster and domain controllers placed in the same AD site.
On all active nodes every day occures an error, registered in "System" journal:
____________________________________
Log Name:      System
Source:        Microsoft-Windows-FailoverClustering
Date:          2/5/2013 8:33:34 PM
Event ID:      1207
Task Category: Network Name Resource
Level:         Error
Keywords:     
User:          SYSTEM
Computer:      node1.domainname.com
Description:
Cluster network name resource 'Network Name (App1)' cannot be brought online. The computer object associated with the resource could not be updated in domain 'domainname.com' for the following reason:
Unable to update password for computer account.

The text for the associated error code is: Access is denied.
 
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.
____________________________________

And on 3 active nodes periodical occurs event, registered in "FailoverClustering/Operational" journal:
____________________________________
Log Name:      Microsoft-Windows-FailoverClustering/Operational
Source:        Microsoft-Windows-FailoverClustering
Date:          2/5/2013 2:27:54 PM
Event ID:      1201
Task Category: Resource Control Manager
Level:         Information
Keywords:     
User:          SYSTEM
Computer:      node1.domainname.com
Description:
The Cluster service successfully brought the clustered service or application 'App1' online.
____________________________________

I don't understand - why contradictory events occurs on cluster nodes.

I looked for some articles to resolve problem and find these:
http://technet.microsoft.com/en-us/library/cc773451(v=ws.10).aspx
http://support.microsoft.com/kb/947049?wa=wsignin1.0
..and a lot of forums, same topics....

All cluster accounts, include CNO, computers (nodes), applications (services), placed in default location - "Computers" container.

I check permissions for container and for accounts:
____
For container "Computers"
 - CNO "Cluster$" have permissions "Full Control" - this object only.
____
For all accounts (CNO, computers, applications)
 - CNO "Cluster$" have special permissions: list contents + read all attributes + change password
____

Now cluster and application run correct. I moved applications between nodes, and all also working correct. But..
I can't find information how to "Check that the domain-wide quota for creating computer objects (by default, 10) has not been reached"
I think, that the error may be related with incorrect permissions for cluster accounts.

The problem I have is that I can't to make change in permissions (and other any changes), before argues the correct solution.
Also, I can't experiment in prodaction environment, and I haven't got a test environment to emulate same errors and trying resolve them.
And I must guarantee, that after I make changes - cluster will continue working properly, and I must argue the solution.

Someone have any expirience with successfull resolve this error?
Maybe there are reasons that I missed?
Please help me to fix this issue.
Thanks!

I'm currently working on a test of a Windows Failover Cluster.  I've got two machines (physical boxes, not VMs), and I've installed Server 2012 on both.  The intent is to use these for an HPC Head Node Failover Cluster.  All the validation tests pass, with the exception of shared storage, and this is where I'm having some difficulty wrapping my head around what I need.

Would I just need shared storage for the HPC database?  Or for a witness disk or other things?  We do not have a SAN, so I don't have any iSCSI or FCoE options.  These aren't VMs, so it doesn't look like I can use this new SMB 3 thing recently introduced(?).  What other options do I have?

My apologies; I'm very new to all of this and of course this needed to be done yesterday, as most things do...

Thank you!

I have a 6 node Server 2012 Hyper-V cluster. Each node was a fresh install with all local drives formatted and repartitioned during OS install.

The first 5 nodes went great, but the 6th node is causing me some problems.

On the 6th node, Im able to connect to the iSCSI LUNs with no issues. Everything looks great until I add this node to the cluster.

When I add it, the add succeeds, but none of the LUNs are mounted to the c:\ClusterStorage folder correctly.

Instead of showing up in ClusterStorage as a mountpoint for each LUN (6 LUNs in total) they show as folders, and are not accessible. In the Windows Event Logs, for FailoverCluster, Diagnostic it shows the following:

Log Name:      Microsoft-Windows-FailoverClustering/Diagnostic
Source:        Microsoft-Windows-FailoverClustering
Event ID:      2051
[DCM] failed to set volume mount point, source \\?\C:\ClusterStorage\Volume4\ target \\?\Volume{89454e8c-4832-4ad8-a43e-75c4ecab253c}\ error 87

It does this for each of the 6 Luns.

I've tried removing this node from the cluster and reinserting it. Reboots while a member of the cluster, and not the cluster. All Windows updates are applied. Full format and wipe of the server, reinstall of OS and try again, etc. I tried looking on Technet and found some references to this error code but they appeared to be related to driver builds using windows API to use mount points. I haven't written any special drivers or anything unique at all for this cluster. Everything is out of the box Microsoft native drivers.

The server is a Dell PowerEdge R710, same as one of the other nodes in the cluster which is working fine. The other 4 are Dell PE 1950s. The first 5 are working great, its just this sixth one. All 6 servers were reloaded over the course of about a week, using the same checklist, same media, etc. I currently have 72 VMs running on this cluster with 5 nodes, and really looking forward to joining #6.

Anyone have any ideas before I call Microsoft support?

Thanks

Sean Greenbaum

Hi guys,

We are configuring and using Cluster Aware Updating to patch our server 2012 clusters. We triggered the run and it managed to patch the servers but failed to restart them. The error is Failed to restart "server": (ClusterUpdateException) Failed to restart "Server": (Win32Exception) Access is denied

==> (Win32Exception) access is denied.

Any one can help us?

Thank you

Hi,

My CSVs (iSCSI SAN volumes) are filling up, but I can't see what is taking the space.  I have a server 2012 cluster with 4x 3TB CSVs on an iSCSI SAN.  One of the CSVs has only 250GB free according to the properties of the disk in Cluster manager, however the total amount of disk used by my VMs is 1.8TB, so I have almost a TB of space being used but I can't see what by.

I backup the VMs using DPM 2012 SP1 so I think VSS may be to blame (no VSS hardware providers install, using the Microsoft VSS provider), but running a vssadmin list shadowstorage doesn't return any info about whats in use by VSS

vssadmin list shadowstorage
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2012 Microsoft Corp.

No items found that satisfy the query.

Are there any other things I can do to see what is eating the space and to recover it?

Cheers,

James

I attempted to failover my Exchange 2003 Cluster on a Windows 2003 cluster and when I "Move Group" the resources go offline then come back online to Node 1.  I checked the System Event Log and no errors show for not failing over to Node 2. Is there something specific I should be looking for in the cluster.log file?

Environment:  Windows 2003 Active/Passive 2-node cluster

I have setup a Windows Server 2012 MSCS cluster on one node.  The file services was setup as a cluster resource and shares configured on it. Locally, I can see the shares with the UNC path and access the folders. Across the network, I can see the shares across the network but not access the folders. It acts like there are no permissions. 

Shares configured on the server vice the cluster node are accessible.

The Computer Shogun

Hi

We have a Windows 2008 R2 Failover Cluster with sql 2008 R2.

Now have one node "the passive node" for moment problem with 2 of its hard disk. it has only 2 ( raid 1) one disk is failed and the other disk have bad blocks warning.  . We have lost the Raid Configuration, but the passive node is up and running , but we have get new hardware from dell (2 disk and 1 raid controller) 

So we need to reinstall that server.

What is the best way to solve that !!

We have run the sql server setup on the passive node and run "remove node from sql server failover cluster".

what's the next step , evict  ? or just wait to reinstall the new server and add node in sql ??

Thanks for advice