Hi all,

I am wondering if you will be able to help me with an issue making CAU work for my Hyper-V cluster

Here is the message I get when testing it

PS C:\Windows\system32> Test-CauSetup

WARNING: Cannot find the Windows PowerShell data file 'ClusterAwareUpdating.psd1' in directory 'C:\Windows\System32\BestPractice
s\v1.0\Models\Microsoft\Windows\ClusterAwareUpdating\en-GB\', or in any parent culture directories.
WARNING: Exception calling "WriteRuleStart" with "3" argument(s): "Rule title cannot be empty.
Parameter name: title"
WARNING: Exception calling "WriteRuleResult" with "6" argument(s): "Rule title cannot be empty.
Parameter name: title"
WARNING: Exception calling "WriteRuleStart" with "3" argument(s): "Rule title cannot be empty.
Parameter name: title"
WARNING: Exception calling "WriteRuleResult" with "6" argument(s): "Rule title cannot be empty.
Parameter name: title"
WARNING: Exception calling "WriteRuleStart" with "3" argument(s): "Rule title cannot be empty.
Parameter name: title"
WARNING: Exception calling "WriteRuleResult" with "6" argument(s): "Rule title cannot be empty.
Parameter name: title"
WARNING: Exception calling "WriteRuleStart" with "3" argument(s): "Rule title cannot be empty.
Parameter name: title"
WARNING: Exception calling "WriteRuleResult" with "6" argument(s): "Rule title cannot be empty.
Parameter name: title"
WARNING: Exception calling "WriteRuleStart" with "3" argument(s): "Rule title cannot be empty.
Parameter name: title"
WARNING: Exception calling "WriteRuleResult" with "6" argument(s): "Rule title cannot be empty.
Parameter name: title"
WARNING: Exception calling "WriteRuleStart" with "3" argument(s): "Rule title cannot be empty.
Parameter name: title"
WARNING: Exception calling "WriteRuleResult" with "6" argument(s): "Rule title cannot be empty.
Parameter name: title"
WARNING: Exception calling "WriteRuleStart" with "3" argument(s): "Rule title cannot be empty.
Parameter name: title"
WARNING: Exception calling "WriteRuleResult" with "6" argument(s): "Rule title cannot be empty.
Parameter name: title"
WARNING: Exception calling "WriteRuleStart" with "3" argument(s): "Rule title cannot be empty.
Parameter name: title"
WARNING: Exception calling "WriteRuleResult" with "6" argument(s): "Rule title cannot be empty.
Parameter name: title"
WARNING: Exception calling "WriteRuleStart" with "3" argument(s): "Rule title cannot be empty.
Parameter name: title"
WARNING: Exception calling "WriteRuleResult" with "6" argument(s): "Rule title cannot be empty.
Parameter name: title"
WARNING: The variable '$_system_translations' cannot be retrieved because it has not been set.
WARNING: Exception calling "WriteRuleStart" with "3" argument(s): "Rule title cannot be empty.
Parameter name: title"
WARNING: Exception calling "WriteRuleResult" with "6" argument(s): "Rule title cannot be empty.
Parameter name: title"
WARNING: The variable '$_system_translations' cannot be retrieved because it has not been set.
WARNING: Exception calling "WriteRuleStart" with "3" argument(s): "Rule title cannot be empty.
Parameter name: title"
WARNING: Exception calling "WriteRuleResult" with "6" argument(s): "Rule title cannot be empty.
Parameter name: title"WARNING: Cannot find the Windows PowerShell data file 'ClusterAwareUpdating.psd1' in directory 'C:\Windows\System32\BestPractice
s\v1.0\Models\Microsoft\Windows\ClusterAwareUpdating\en-GB\', or in any parent culture directories.WARNING: The EngineReport.xml and Result.xml files were not generated successfully.
Please validate if the discovery, schematron & the schema files are authored correctly and try again.


ModelId           : Microsoft/Windows/ClusterAwareUpdating
SubModelId        :
Success           : False
ScanTime          : 01/12/2016 13:05:07
ScanTimeUtcOffset : 00:00:00
Detail            : {HV2A, HV2A}

Running GUI based Analyze says:

There was an error analyzing cluster updating readiness.

I have remove CAU role multiple times and put it back with no luck.

Event ID 4657 is logged saying

Failover Cluster PowerShell cmdlet Get-ClusterParameter: The private property 'CauResourceName' does not exist.

Automatic Windows Updates are blocked on all cluster nodes too.

Regards, Ilkin

Hi,

We have a planned power outage in one of the data centers and we need to gracefully shutdown our services then power it up back again after some time.

We have:

1. EMC storage

2. Two-nodes Windows Server 2012 R2 Hyper-V Cluster: Guests VMs are two domain controllers, four exchange 2013 VMs, File server and some other services...

My plan is the below:

Downtime:

1. Shutdown all non-domain controllers VMs like Exchange, file servers, etc...

2. Shutdown Hyper-V node #2

3. While the two DCs are still running, shutdown Hyper-V node #1 (this makes sure the two DCs will be up when powering up later Hyper-V node #1)

4. Shutdown EMC storage

5. Shutdown network devices (routers, switches)

Power Up:

1. Power up network devices

2. Power up EMC storage

3. Power up Hyper-V node #1 (make sure login to domain and clustering is working as DCs should be up as well on that node)

4. Power up Hyper-V node #2

5. Power up all non-domain controllers VMs like Exchange, file servers, etc...

Do you think this is a valid approach? Please amend\update if necessary.

Hi,

I've seen a few other threads with this error but no solutions which seem applicable to our environment.

We have a 2 node Windows 2008 R2 cluster.

All resources running fine on one node.  But when we try to fail resources over to the second node the cluster disks won't come online.

Eventlog just says "Cluster resource 'Cluster Disk 19' in clustered service or application 'x' failed."

ValidateStorage log shows the following error:

CprepDiskOnline: Failed to get volume name for device \\?\GLOBALROOT\device\Harddisk19\Partition1\, status 3.

Cluster log shows the following error:

WARN [RES] Physical disk <Cluster disk 19>: OnlineThread: Failed to get volume guid for device \\?\GLOBALROOT\device\Harddisk19\Partition1\. Error 3.

I'm not sure what to do with this.  It's like one node can't read the disk correctly.  All the disks are showing in disk management OK.

Any advice would be appreciated.

Thanks,

Steve

Hello,

I'm having problems setting up two Cluster Shared Volumes on a 3-node Server 2012 R2 cluster.  I have a separate 3-node cluster in a different domain that appears to be setup identically (although there must be some difference that I haven't found) and it's working fine.  In both cases, the volumes are hosted on an EqualLogic array and are accessed via iSCSI/MPIO.

I was able to successfully create the two Cluster Shared Volumes, and I can bring them online and failover between all 3 nodes.  However, when I try to access either volume from any of the 3 nodes (e.g. browse via Windows Explorer), I get the following error:

"C:\ClusterStorage\Volume 1 is not accessible.  Arithmetic result exceeded 32 bits."

There are many of the following Cluster Events that are generated from the Cluster Authentication Manager:

"Cluster service failed to create a cluster identity token for Cluster Shared Volumes. The error code was '-1073741675'. Ensure the domain controller is accessible and check for connectivity issues. Until connection to the domain controller is recovered, some operations on this node against the Cluster Shared Volumes might fail."

I verified that the domain controllers are accessible.

I validated both clusters.  The cluster where I'm having these issues has one warning that is not present on the other cluster.  Under "Validate CSV Settings", the following warning is shown:

"Failed to validate Server Message Block (SMB) share access through the IP address of the fault tolerant network driver for failover clustering (NetFT). The connection was attempted with the Cluster Shared Volumes test user account, from node C to the share on node A. The specified procedure could not be found."

So this test failed from node C to node A, but it was successful from node A to node B and from node B to node C.  I verified that SMB 2.0 (and hence 3.0) is enabled on all 3 nodes.

Some other things I checked:  The File Server feature is installed on all cluster nodes.  The Server service is running on all nodes.  Windows Firewall has been disabled on all nodes.  All nodes can access \\<machine name>\c$ on the other nodes.

I appreciate any suggestions.  Thank you!

Hello,

I have a WSFC with allwayson.

2nodes are in same region and 1 in a different one.

In top of that i have a SQLServer with allwayson.

On region1 the resources can failover between the 2 nodes.

In case of DR sql server will failover (via allwayson) to region2.

In order to do some tests we have broke the communication between regions.

After, in region 2 we have forced cluster online without quorum. (In region 1 we kept everything working) 

The sql allwayon went online and all tests were done sucessefully.

After all the tests we have (in region 2) shutdown cluster and remove the vote from the DR node. We also have stopped all sql server resrouces (Avaiability groups and  listener).

Once all was down we have resume the communication between the 2 sites. NOW the problems appear.

The Cluster dns name as well as the SQL AO listener names have been removed from the primary and secondary dns.

When i try to add a listener to a new instance i get

The DNS from the cluster resrouce also has desapear.

Can anyone help?

Regards,

Arestas

I have a 2008R2 file server cluster that is extremely critical.  It is actually running 2008R2 Storage server with SIS and Microsoft recommends re-inflating the volumes before moving to a new cluster.  The current cluster has one node that is so corrupted that we have disabled the cluster service on it, and the shared storage also has enough latency that it causes the other node to occasionally have problems when we try the sisadmin commands or sometimes just fails a datastore as offline.  We are thinking that because of these cluster issues with one bad node+bad performing storage that we are probably better to simplify everything and destroy the cluster and go back down to a single node and hopefully it will handle the storage concerns better.  Then we can focus on getting the data re-inflated and migrated to a new 2012R2 cluster.  That sounds a lot simpler than hoping the cluster becomes more stable when messing with cluster timeouts, etc.

I have never done this, but I am thinking that I just destroy the cluster, delete the cluster computer account, rename the current working node to the cluster name and use the cluster vip, and recreate the shares that it should work fine.  Most of our ownership on the datastores are set to the default 500 account and I am thinking that data should come across with all the same ACLS, etc.  Does anyone see any concerns with this plan or have any other advice?

Thanks,

Dave

The target cluster are running the final RTM MSDN bits of Nano server datacenter, with latest *.321.* windows update packages, and the member nodes have a mixture of NVMe and SATA storage. The -verbose output of enable-clusters2d shows the text at the bottom of this posting, up to the hang...

The log files on the cluster members show no useful information. The "cannotpoolreason" for the NVMe devices shows text similar to "waiting for verification", after the hang..

I've removed the cluster several times, cleaned the systems, and reinitiated the cluster create and enable s2d with same effect.

How may I further diagnose my problem?

---

VERBOSE: vms-c: 2016/10/16-16:25:56.110 Setting default fault domain awareness on clustered storage subsystem
VERBOSE: vms-c: 2016/10/16-16:25:56.751 Waiting until physical disks are claimed
VERBOSE: vms-c: 2016/10/16-16:25:59.767 Number of claimed disks on node 'VMS-1': 6/2
VERBOSE: vms-c: 2016/10/16-16:25:59.783 Number of claimed disks on node 'VMS-2': 6/2
VERBOSE: vms-c: 2016/10/16-16:25:59.798 Node 'VMS-1': Waiting until cache reaches desired state (HDD:'ReadWrite'
SSD:'WriteOnly')
VERBOSE: vms-c: 2016/10/16-16:25:59.798 SBL disks initialized in cache on node 'VMS-1': 6 (6 on all nodes)
VERBOSE: vms-c: 2016/10/16-16:25:59.814 SBL disks initialized in cache on node 'VMS-2': 6 (12 on all nodes)
VERBOSE: vms-c: 2016/10/16-16:25:59.814 Cache reached desired state on VMS-1
VERBOSE: vms-c: 2016/10/16-16:25:59.829 Node 'VMS-2': Waiting until cache reaches desired state (HDD:'ReadWrite'
SSD:'WriteOnly')
VERBOSE: vms-c: 2016/10/16-16:25:59.845 Cache reached desired state on VMS-2
VERBOSE: vms-c: 2016/10/16-16:25:59.845 Waiting until SBL disks are surfaced
VERBOSE: vms-c: 2016/10/16-16:26:03.267 Disks surfaced on node 'VMS-1': 12/12
VERBOSE: vms-c: 2016/10/16-16:26:03.298 Disks surfaced on node 'VMS-2': 12/12
VERBOSE: vms-c: 2016/10/16-16:26:06.945 Waiting until all physical disks are reported by clustered storage subsystem
VERBOSE: vms-c: 2016/10/16-16:26:10.188 Physical disks in clustered storage subsystem: 0

Hi,

We are getting following error in cluster enviorment.My sql erver instance role failed and moved to different node

Please help

Cluster resource 'SQL Server (cluster instance)' (resource type '', DLL 'sqsrvres.dll') either crashed or deadlocked

Hello Folks,

We have configured file services on the Windows Storage server 2012 R2 cluster. Team has recently restarted both nodes at the same time and after that my cluster went down. I am not able to open cluster as cluster service is not stable. It is continuously restarting due to loss of quorum disk. When i checked disk management on both nodes, I found that all cluster disks are reserved. I tried to remove reservation with the help of following...

1. Clear-clusterreservation: Command executed sucessfully but still disk is showing reserverd.

2. Cluster node Server name /clear

3. Tried to remove attacheddisk registry settings...after server reboot that entry is coming automatically. 

Please help me to remove cluster disk reservation. 

Thanks, Chinmay.

Hello.

I’m hoping to get some help with a cluster issue I’m having using Windows Storage Server 2012.

When the cluster is created my Cluster Core Resources are all happy and online.

I can more the Cluster Name using “move Core Cluster Resources” between the two nodes without any problems.

If I select ‘Simulate Failure’ on the IP Address resource, it works the first time

If I do it again shortly after it fails and I get an Event ID 1254, 1205 and 1069.

Event ID 1254

Clustered role 'Cluster Group' has exceeded its failover threshold. It has exhausted the configured number of failover attempts within the failover period of time allotted to it and will be left in a failed state. No additional attempts will be made to bring the role online or fail it over to another node in the cluster. Please check the events associated with the failure.  After the issues causing the failure are resolved the role can be brought online manually or the cluster may attempt to bring it online again after the restart delay period.

Event ID 1205

The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.

Event ID 1069

Cluster resource 'Cluster IP Address' of type 'IP Address' in clustered role 'Cluster Group' failed.

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.

Basically I’m trying to simulate a network failure to make sure the failover kicks in.

If I click on it and ‘Bring Online’ it comes up fine.

Where do I find this Threshold Policy and set it to initiate failover if the IP Address resources fails?

Thank you in advance for your help.

In my organization we stood up a test SQL failover cluster.  We began with the typical 2 node architecture where node1 holds the SQL role and node2 is configured as an additional node on standby in the SQL cluster.  When we write big blocks of data into the test data base and pull the plug on node1 the cluster gracefully hands the SQL role to node2 and the data being written continues to write.  Great - that's what we want!

Next - we decided to get fancy.  Instead of installing the SQL role on one server and then adding the other node to the SQL server failover cluster, we installed a new SQL Server failover on both nodes.  Next we ran the SQL installer and added node1 to node2's sql instance and vise versa for node2.  Now we have two SQL server roles - with a preferred owner for both:

• SQLROLE1 -- preferred owner is node1
• SQLROLE2 -- preferred owner is node2

We can successfully run both roles off of one node - however when failing over the database write is interrupted (which basically defeats the purpose of the failover cluster)...Anyone have some thoughts on how we can get the same write performance we were having before with an A B config versus the A A (Multi-Instance) config?

Thanks,

Justin

Justin Carlton

Hi,

Can anyone explain me cluster log file location in 2008R2 /2012 

Hope we need to check the log file during troubleshooting the cluster issue

Hi,

Please explain important commands used for cluster administration in 2008 / 2012 OS.

We had a consultant in today looking at various things on our system.

Unrelatedly he commented that use FC fileserver used a full additional server licence, as would a FC DHCP role.

Is this true?  I certainly can't find any documentation on the subject anywhere.  It seems kind of ridiculous if true, because each of those services could be installed on FC OS freely, as they're licenced with the OS already.

Sivakumar Thayumanavan

We have a Typical issue wherein we have set of 16 Exchange 2016 servers with about 60k users. We have about 8 GC/DC in site,6 GC/DC out of site. Every morning for about 10-20 minutes, the users face performance issues wherin, outlook freezes,owa login is slow, sending emails is slow. When we look at the Exchange and domain controller resource performance (CPU,DISK,MEMORY), it is quite normal and under 50 %. However, the issue still happens. On the DCs, we get a lot of ATQ alerts and get deep LDAP queries for various objects, etc. We are currently unsure what is causing this. Any inputs is very much appreciated.

Had 1x 2012 R2 machine (call it A) set up as a cluster with another 2012 R2 machine used for shared storage. Finally got a second machine (call it B) to add to the cluster, added the machine, passed, showed up in the cluster, but I cannot live or quick migrate machines, or create VMs on A from B or B from A.

Live migrations (going from B to A) fail with:

Live migration of 'Virtual Machine TESTVM' failed.
Virtual machine migration operation for 'TESTVM' failed at migration destination 'HOST-A'. (Virtual machine ID 0D1A3F2C-7623-4D26-A5B9-71F88599BE1C)

User 'NT AUTHORITY\SYSTEM' failed to create external configuration store at '\\SHAREDSTORAGE\vms\TESTVM': General access denied error. (0x80070005)

Failed to set security info for '\\SHAREDSTORAGE\vms\TESTVM\Virtual Machines': 'General access denied error'('0x80070005').

When I try and create a VM on A from B or B from A I get:

The operation failed.

Failed to create external configuration store at '\\SHAREDSTORAGE\vms\TESTVM': General access denied error. (0x80070005)

User ‘DOMAIN\Administrator’ failed to create external configuration store at '\\SHAREDSTORAGE\vms\TESTVM': General access denied error. (0x80070005)

Went so far as to set the share permissions on \\SHAREDSTORAGE\vms to Everyone full control and Everyone full control on the NFTS permissions. No change.

If I am on A and create a VM on A in either Failover Cluster Manager or Hyper-V manager it works just fine. I can go to \\SHAREDSTORAGE\vms from either machine and create files\folders\etc no issue.

Dear all!

I've faced up with error while creating HA VM in WS 2016 Hyper-V Failover cluster with configuration listed below:

8-Node Hyper-V Failover Cluster on Windows Server 2016 Datacenter with all last updates.

I can create an non-HA VM on any host without problem, but when I try to make it HA, using Failover Cluster Management console and High Availability Wizard, I receive an error on step "Select Virtual Machine":



Also in "FailoverClustering-Manager" event log I've found an error: 

Failover Cluster Manager failed while managing one or more cluster. The error was 'An item with the same key has already been added.'. For more information see the Failover Cluster Manager Diagnostic channel.

In FailoverClustering-Manager Diagnostic log two errors:

Exception occurred in background operation - System.ArgumentException: An item with the same key has already been added.
   at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
   at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
   at System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](IEnumerable`1 source, Func`2 keySelector, Func`2 elementSelector, IEqualityComparer`1 comparer)
   at MS.Internal.ServerClusters.Configuration.HAViridianVirtualMachine.GetClusteredVirtualMachinesResourceOfType(Cluster cluster, String resourceType)
   at MS.Internal.ServerClusters.Configuration.HAViridianVirtualMachine.GetClusterableVirtualMachines(Cluster cluster)
   at MS.Internal.ServerClusters.Wizards.SelectVirtualMachinePage.LoadVirtualMachines(BackgroundOperationStatus status, Object parameter)
   at MS.Internal.ServerClusters.BackgroundOperation`2.BackgroundOperationProc(Object state)

and

Could You please help me with this issue?

Thanks in advance!

Dear All,

I want build a SQL Server 2008 R2  Ent (64bit) and SQL Server 2012 Ent (64bit) 2 node fail-over cluster(Active/Passive) on Windows Server 2012 R2without RDM.(want on Shared disk)

Please share guide lines or links which can help us to Build the A/P cluster.

Thanks in advance.

SNIVAS