Hi,

I have two servers running Server 2016 Data Center and I am trying to set up a high-availability fail-over environment using Storage Spaces Direct (S2D) for a bunch of Hyper-V VMs that will be running on the two servers.

I have created the cluster, enabled storage spaces direct, created the S2D storage pool, created two virtual disk from the storage pool (formatted as ReFS) and then created a Volume in each Virtual Disk. There is a file share witness configured on a local server. Cluster Validation is all passes (except for an unsigned driver for logmein display mirror, and a complaint that one of the servers is on a slightly different version of the windows defender definitions).

On both servers, I can see that I have c:\clusterstorage\volume1\ and c:\custerstorage\volume2\

However, when I shut one of the servers down, the other server looses visibility of one of the c:\custerstorage\volumeX\ folders.

When I have VMs stored in c:\custerstorage\volume1\ and ..\volume2\ and both nodes are up, everything is fine and I can do live migrations between hosts. But when one of the servers is shut down the live migration happens but then when the other server looses sight of one of the c:\custerstorage\volumeX\ folders the VM locks up and stops working (not surprisingly).

It's my first time using S2D so, does this sound correct? I would have thought that even if I take one of the nodes down, the other node should still retain visibility of both its c:\custerstorage\volume1\ and ..\volume2\ folders thanks to the magic of S2D.

Is there any trouble-shooting I can do to figure out why this isn't working?

Possibly relevant: I am building this system in my lab for a client. The client has a single SBS2011 server on their LAN at a different site. I have created a site to site VPN from my lab LAN to the customer's LAN. All NICs on the servers (excluding the 2 x 10 GbE NICs used for SMB/S2D/etc) have their DNS settings pointing to the customer's DC over the site-to-site VPN. The hyper-v hosts are connected to the customer's domain in this way.

Does Microsoft support configuring 2012 R2 failover cluster using nfs mounts?

I'm having trouble creating active directory detached cluster. From log I can see there is problem with authentication, but both users are the local admin accounts with same password. Here is log file extract:

Excerpt from log file:

00001488.0000046c::2017/02/06-09:41:10.610 INFO  [ACCEPT] 0.0.0.0:~3343~: Accepted inbound connection from remote endpoint 10.32.6.201:~58602~.
00001488.00001890::2017/02/06-09:41:10.610 INFO  [SV] New real route: local (10.32.6.200:~3343~) to remote  (10.32.6.201:~58602~).
00001488.00001890::2017/02/06-09:41:10.610 INFO  [SV] Got a new incoming stream from 10.32.6.201:~58602~
00001488.00001890::2017/02/06-09:41:10.610 ERR   [SM] Sponsor: Setting package MSG_AUTH_PACKAGE::KerberosAuth failed with status 2148074254
00001488.00001890::2017/02/06-09:41:10.610 WARN  mscs::ListenerWorker::operator (): (-2146893042)' because of 'Status'
00001488.00001890::2017/02/06-09:41:13.892 INFO  [NM] Received request from client address PLSD001.
00001488.00001890::2017/02/06-09:41:13.892 WARN  [VER] Could not read version data from database for node PLSD002 (id 2).
00001488.00001890::2017/02/06-09:41:13.892 WARN  [VER] Could not read version data from database for node PLSD002 (id 2).

There is no Active Directory present and no DNS server.

Can someone tell me what am I doing wrong?

Tnx, Robert.

Hi All,

I have setup a NLB Cluster with following options.

1. Cluster operation mode: Multicast
2. Port Rule:

Range:80/443

Protocol:TCP

Filtering mode:Multiple host

Affinity: None

Following diagram illustrates my current cluster configuration.

NLB is working just fine from out side of the Cluster. That is, WIN-CLNT-01 can access the web service using both NLB Cluster IP (Virtual IP) and its URL (https://portal.service.com)

Also ping test among the hosts is fine. Ping to Cluster IP on each cluster hosts is fine too.

The problem is when I try to open the same URL from one of Nodes inside of the NLB Cluster.

For example, if I shut down the service on WIN-NODE 2, I can't open the URL on NODE-2 machine. Tried on WIN-NODE1 and Win-NODE3, but the result was same, I couldn't. 

Is there any settings or something I need to change? Or is it by design?

Thanks in advance!

==========================

Background of this question.

My web service supports multiple instances across the NLB Cluster.

Installing the very first service should be OK, as the user should indicate that this is the first installation within the NLB Cluster. For additional installation of the service, the installer needs to make a REST API call to the existing services to register itself to the service system. However, this API call always fails because it can't access the service via the Custer IP or its URL. If I detach the host from the cluster, I can install the service app, but it is not what I wait ;-)

I found an article that has same issue that I have.

https://social.technet.microsoft.com/Forums/en-US/4e5194c5-24c3-4dd9-b34b-7b6598ba245d/nlb-from-host-inside-the-cluster?forum=winserverClustering

Dears

I have two servers 2012 servers hyper-v clustered. One server got crashed. I need to reinstall the server and join to current cluster. What is the best procedure for reinstalling and rebuilding the cluster.......

Thanks in Advance

Muhammad Faheem

Hi There,

When i configure Failover cluster, it should display all the available disks in “Disks” under “storage”. But in our case it is not showing any Disks. When I ran “validate Cluster” Wizard, I noticed below error.

“If the disk that you want to add does not appear at all in Disk Management (on any node), there might be an issue with the storage configuration that is preventing the operating system from recognizing or mounting the disk. Note that disks currently in use by the cluster will appear in Disk Management on one node only (the node that is the current owner of that disk). If the disk that you want to add appears in Disk Management but does not appear after you click Add a disk, confirm that the disk is configured as a basic disk, not a dynamic disk. Only basic disks can be used in a failover cluster.”

 Thanks and regards

Venkat

Hi,

I'm getting the below error in every 15 minutes on Windows 2012 R2 SQL cluster.

event id  1069

Cluster resource 'Cluster Disk 4' of type 'Physical Disk' 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.

Event 1558

The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data

Server OS: Windows 2012 R2 Datacenter Edition

Cluster: SQL 2012 R2 failover Cluster

Platform: VMware

Cluster: Cluster across host.

Regards,

Hakim. B

Hakim.B Sr.System Administrator

Hi Team,

We have 3 node windows failover cluster running SQL Server. we have cluster disk as quorum. Since it is going to be a AG , 3rd node in DR is part of WSFC but doesn't have vote. Node 1 and node 2 in primary has shared storage between them. node 3 in DR has independent storage.

We are seeing an issues where node 3 in DR site goes down and even after trying multiple things it never comes online again (reboot, network enable disable, ipv6 disable etc. etc.). When we do cluster validation, validation gets failed every time with network communication between node 3 to node 1 and node 2 in primary.

Very odd behavior is that that if we evict and rejoin node 3 again to the cluster and do cluster validation while joining the node, communication established successfully based on the validation report. We have tried it couple of time evict and rejoin and it successful everytime. We are getting a hard time understanding this behavior that why node 3 start communication when we evict it from the cluster and then rejoins also otherwise as a down node it was showing communication failure on port udp 3343 everytime.

Just want to check if anyone has seen this and have some pointers to resolve it or where should we look ? Now we have everything enabled between nodes i.e. firewall any  to any, AV is removed from all nodes...what else we need to look?

Any pointers will be appreciated . Thanks

Regards,

Hi Team,

We need to evict and remove 1 node from windows failover cluster , could anyone pls .point me or share any step by step article or document or steps to follow?

Basically we want to evict and introduce new node to the existing windows failover cluster. Its a 3 node cluster (2 nodes in primary and 1 node in DR site), we want to evict node 3 from DR site and replace it with new node. All nodes are VMWare VMs. Thanks.

While adding nodes in High Availability Server 2016 workstation error message is coming "failover cluster node cannot be contacted " anyone suggest possible solutions.

for no apparent reason I have a s2d virtual disk which has an operationalstatus of "no redundancy" and healthstatus "unhealthy". Running repair-virtualdisk gives this response:

PS C:\Users\administrator.PAO2K> get-virtualdisk "volume3" | repair-virtualdisk
repair-virtualdisk : There is not enough redundancy remaining to repair the virtual disk.
Activity ID: {a366982d-b602-4deb-8f6d-c8ec59c12217}
At line:1 char:29+ get-virtualdisk "volume3" | repair-virtualdisk+                             ~~~~~~~~~~~~~~~~~~+ CategoryInfo          : NotSpecified: (StorageWMI:ROOT/Microsoft/...SFT_VirtualDisk) [Repair-VirtualDisk], CimEx
   ception+ FullyQualifiedErrorId : StorageWMI 50001,Repair-VirtualDisk

PS C:\Users\administrator.PAO2K>

so how to fix? this virtual disk is tiered with triple mirror performance tier and double parity capacity tier, and is an ReFS volume.

Hello,

So, Im in a situation with a Failover Cluster 2016 with 2 hosts, where I want to change ip from :

cluster ip : 10.11.12.20

host1 ip : 10.11.12.21

host2 ip : 10.11.12.22

to

cluster ip : 10.40.12.20

host1 ip : 10.40.12.21

host2 ip : 10.40.12.22

How should I do this?

I've looked through these articles : 

https://blogs.technet.microsoft.com/chrad/2011/09/16/changing-hyper-v-cluster-virtual-ip-address-vip-after-layer-3-changes/

https://social.technet.microsoft.com/Forums/windowsserver/en-US/a640a75b-52e1-43c1-a1fb-acbc142c614a/how-to-change-hyperv-cluster-ip-address?forum=winserverClustering

http://bartvanvugt.blogspot.com/2012/01/change-ip-address-hyper-v-cluster.html

But havent found the entire solution yet - so hopefully, someone in here can help me :)

Hello

We have several Hyper-converged einvoronments based on HP ProLiant DL360/DL380.
We have 3 Node and 2 Node Clusters, running with Windows 2016 and actual patches, Firmware Updates done, Witness configured.

The following issue occurs with at least one 3 Node and one 2 Node cluster:
When we put one node into maintenance mode (correctly as described in microsoft docs and checked everything is fine) and reboot that node, it can happen, that one of the Cluster Virtual Disks goes offline. It is always the Disk Performance with the SSD only storage in each environment. The issue occurs only sometimes and not always. So sometimes I can reboot the nodes one after the other several times in a row and everything is fine, but sometimes the Disk "Performance" goes offline. I can not bring this disk back online until the rebooted node comes back online. After the node which was down during maintenance is back online the Virtual Disk can be taken online without any issues.

We have created 3 Cluster Virtual Disks & CSV Volumes on these clusters:
1x Volume with only SSD Storage, called Performance
1x Volume with Mixed Storage (SSD, HDD), called Mixed
1x Volume with Capacity Storage (HDD only), called Capacity

Disk Setup for Storage Spaces Direct (per Host):
- P440ar Raid Controller
- 2 x HP 800 GB NVME (803200-B21)
- 2 x HP 1.6 TB 6G SATA SSD (804631-B21)
- 4 x HP 2 TB 12G SAS HDD (765466-B21)
- No spare Disks
- Network Adapter for Storage: HP 10 GBit/s 546FLR-SFP+ (2 storage networks for redundancy)
- 3 Node Cluster Storage Network Switch: HPE FlexFabric 5700 40XG 2QSFP+ (JG896A), 2 Node Cluster directly connected with each other

Cluster Events Log is showing the following errors when the issue occurs:

Error 1069 FailoverClustering
Cluster resource 'Cluster Virtual Disk (Performance)' of type 'Physical Disk' in clustered role '6ca63b55-1a16-4bb2-ac53-2b23619e258a' 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.

Warning 5120 FailoverClustering
Cluster Shared Volume 'Performance' ('Cluster Virtual Disk (Performance)') has entered a paused state because of 'STATUS_NO_SUCH_DEVICE(c000000e)'. All I/O will temporarily be queued until a path to the volume is reestablished.

Error 5150 FailoverClustering
Cluster physical disk resource 'Cluster Virtual Disk (Performance)' failed.  The Cluster Shared Volume was put in failed state with the following error: 'Failed to get the volume number for \\?\GLOBALROOT\Device\Harddisk10\ClusterPartition2\ (error 2)'

Error 1205 FailoverClustering
The Cluster service failed to bring clustered role '6ca63b55-1a16-4bb2-ac53-2b23619e258a' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered role.

Error 1254 FailoverClustering
Clustered role '6ca63b55-1a16-4bb2-ac53-2b23619e258a' 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.

Error 5142 FailoverClustering
Cluster Shared Volume 'Performance' ('Cluster Virtual Disk (Performance)') is no longer accessible from this cluster node because of error '(1460)'. Please troubleshoot this node's connectivity to the storage device and network connectivity.

Any hints / inputs appreciated. Had someone something similar?

Thanks in advance

Philippe

Hi Experts,

we are in the process of implementing SQL server 2016 2-node (Node1 and Node2) traditional fail-over cluster on Hyper-V guest VMs with Clustered shared volume and Quorum with Disk witness.

• Each VM we have two Disks C:\ and D:\
• We have cluster shared Volume (Cluster Disk)  of 250 GB like I:\ and J:\ for SQL server files
• We have one cluster shared Volume (Cluster Disk)  of 25 Gb for Quorum as Q:\
• All the local disks, Cluster volumes I:\ and Q:\ are carved out from the same 4 TB Data store available at Esxi hos

Now we are Testing Disk performance and Results are showing bad performance on clustered shared volumes compared to local dedicated volumes.

What could be the problem and are there any ways to improved the cluster shared volumes performance.

Ramesh M

Gents,

I've upgraded 3-node Hyper-V cluster from Windows Server 2012 R2 to Windows Server 2016.

And a bit confused a new interface of the "Validate Cluster" wizard.

I don't see any choice of the disk for Disk's cluster tests as it was in Windows Server 2012 R2.

In Win 2012 I can choose "Run all test" and wizard will ask you which disk you will use for failover testing. I don't see the same in Win 2016.

Can any one explain if I choose "Run all tests" in Win 2016, will be there disruption ?

I don't see any explanation in the help. All articles are about Win 2012.

Thanks

mcse^4

Hi

I have a problem with failover clustering and iSCSI target in Windows Server 2016.

I often demo the configuration of Failover Clustering for students and customers. And for that I have built a small lab consisting of a Domain Controller and three servers functioning as my cluster nodes.

All Servers run Windows Server 2016 (1607) and have been fully updated with the latest patches. All servers are virtual machines running in Hyper-V on Windows 10 v1709/1803.

The Domain Controller functions as Domain Controller and I have also added the iSCSI role service on that as well. And yes, I know that is not the way to do but this is only a test/demo environment. I have created two iSCSI disk, one for the Witness (1 GB) and one for Shared Storage (100 GB).

My three nodes also run Windows Server 2016 (1607) and is configured with two network cards, one for management (LAN) and one for cluster traffic. I have installed the Failover Clustering feature on these servers and are using the built-in iSCSI initiator to connect to the shared storage published by my iSCSI target running on the Domain Controller. And this is where I run into the first problem.

In order to give the nodes (servers) access to the storage they need to be added to theInitiators list from within Server Manger ->File and Storage Services -> iSCSI. If I choose theQuery initiator computer for ID options and then click Browse (in order to browse for the names of the nodes) Server Manager crashes and I get a window stating that Server Manager has stopped working. If I look in the Event Viewer I see the following events:

Log Name:     Application

Source:       .NET Runtime

Date:         04-06-2018 17:36:52

Event ID:     1026

Task Category: None

Level:        Error

Keywords:     Classic

User:         N/A

Computer:     cph-dc-01.ad.petzfeed.com

Description:

Application: ServerManager.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Application: ServerManager.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.ArgumentException

  at Microsoft.FileServer.Management.Plugin.Dialogues.BrowseDSObjectsNativeMethods+IDsObjectPicker.Initialize(DSOP_INIT_INFO ByRef)

  at Microsoft.FileServer.Management.Plugin.Dialogues.BrowseDSObjectsDialog.ShowDialog(System.Windows.Forms.IWin32Window, PickerTypes, Boolean, StartScope, ProviderTypes, System.String, System.Security.SecureString)

  at Microsoft.FileServer.Management.Plugin.Services.DialogService.ShowPickDialog(PickerTypes, Microsoft.FileServer.Management.Framework.ComputerName, StartScope, ReturnSourceTypes, System.String ByRef)

  at Microsoft.FileServer.Management.Plugin.Services.DialogService.ShowPickComputerDialog(Microsoft.FileServer.Management.Framework.ComputerName, Microsoft.FileServer.Management.Framework.ComputerName ByRef)

  at Microsoft.FileServer.Management.Plugin.Dialogues.AddInitiatorIdSectionDescriptor+<>c__DisplayClass41_0.<.ctor>b__0()

  at MS.Internal.Commands.CommandHelpers.CriticalExecuteCommandSource(System.Windows.Input.ICommandSource, Boolean)

  at System.Windows.Controls.Primitives.ButtonBase.OnClick()

  at System.Windows.Controls.Button.OnClick()

  at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(System.Windows.Input.MouseButtonEventArgs)

  at System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object)

  at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs)

  at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)

  at System.Windows.UIElement.ReRaiseEventAs(System.Windows.DependencyObject, System.Windows.RoutedEventArgs, System.Windows.RoutedEvent)

  at System.Windows.UIElement.OnMouseUpThunk(System.Object, System.Windows.Input.MouseButtonEventArgs)

  at System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object)

  at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs)

  at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)

  at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs)

  at System.Windows.UIElement.RaiseTrustedEvent(System.Windows.RoutedEventArgs)

  at System.Windows.Input.InputManager.ProcessStagingArea()

  at System.Windows.Input.InputManager.ProcessInput(System.Windows.Input.InputEventArgs)

  at System.Windows.Input.InputProviderSite.ReportInput(System.Windows.Input.InputReport)

  at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr, System.Windows.Input.InputMode, Int32, System.Windows.Input.RawMouseActions, Int32, Int32, Int32)

  at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr, MS.Internal.Interop.WindowMessage, IntPtr, IntPtr, Boolean ByRef)

  at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)

  at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)

  at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)

  at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)

  at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)

  at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)

  at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)

  at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)

  at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)

  at System.Windows.Window.ShowHelper(System.Object)

  at System.Windows.Window.ShowDialog()

  at Microsoft.FileServer.Management.Plugin.Services.DialogService.ShowAddInitiatorIdDialog(Microsoft.FileServer.Management.Framework.ComputerName, Microsoft.FileServer.Management.Plugin.Model.InitiatorId ByRef)

  at Microsoft.FileServer.Management.Plugin.PropertyPages.IscsiTargetInitiatorsPropertySectionDescriptor.<.ctor>b__4_0()

  at MS.Internal.Commands.CommandHelpers.CriticalExecuteCommandSource(System.Windows.Input.ICommandSource, Boolean)

  at System.Windows.Controls.Primitives.ButtonBase.OnClick()

  at System.Windows.Controls.Button.OnClick()

  at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(System.Windows.Input.MouseButtonEventArgs)

  at System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object)

  at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs)

  at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)

  at System.Windows.UIElement.ReRaiseEventAs(System.Windows.DependencyObject, System.Windows.RoutedEventArgs, System.Windows.RoutedEvent)

  at System.Windows.UIElement.OnMouseUpThunk(System.Object, System.Windows.Input.MouseButtonEventArgs)

  at System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object)

  at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs)

  at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)

  at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs)

  at System.Windows.UIElement.RaiseTrustedEvent(System.Windows.RoutedEventArgs)

  at System.Windows.Input.InputManager.ProcessStagingArea()

  at System.Windows.Input.InputManager.ProcessInput(System.Windows.Input.InputEventArgs)

  at System.Windows.Input.InputProviderSite.ReportInput(System.Windows.Input.InputReport)

  at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr, System.Windows.Input.InputMode, Int32, System.Windows.Input.RawMouseActions, Int32, Int32, Int32)

  at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr, MS.Internal.Interop.WindowMessage, IntPtr, IntPtr, Boolean ByRef)

  at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)

  at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)

  at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)

  at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)

  at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)

  at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)

  at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)

  at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)

  at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)

  at System.Windows.Application.RunDispatcher(System.Object)

  at System.Windows.Application.RunInternal(System.Windows.Window)

  at Microsoft.Windows.ServerManager.SingleInstanceAppLauncher.StartApplication(Microsoft.Windows.ServerManager.Common.ArgumentsProcessor)

  at Microsoft.Windows.ServerManager.MainApplication.Main(System.String[])

And this error as well:

Faulting application name: ServerManager.exe, version: 10.0.14393.1358, time stamp: 0x593272e2

Faulting module name: KERNELBASE.dll, version: 10.0.14393.1532, time stamp: 0x5965ac8c

Exception code: 0xe0434352

Fault offset: 0x0000000000033c58

Faulting process id: 0xf2c

Faulting application start time: 0x01d3fc19440b98b8

Faulting application path: C:\Windows\system32\ServerManager.exe

Faulting module path: C:\Windows\System32\KERNELBASE.dll

Report Id: a9a4656c-453c-4ef6-8d83-165ee783cbfd

Faulting package full name:

Faulting package-relative application ID:

If I choose theEnter a value for the selected type and select DNS and browse for the machine name the same thing happens – Server Manager crashes and the same events is reported in Event Viewer.

However, I can work around this issue by using the IP addresses of my three nodes instead and add them to the Initiators list. When all that is done my three nodes have no problem connecting to the iSCSI storage.

The real problem comes when I try to run the Validate a Configuration Wizard (Cluster wizard) from within the Failover Cluster Manager. When I clickBrowse (in order to search for the servers, I want to validate) the wizard closes without any visible errors. In the Event Viewer the following error is reported:

Log Name:     Microsoft-Windows-FailoverClustering-Manager/Admin

Source:       Microsoft-Windows-FailoverClustering-Manager

Date:         04-06-2018 18:12:52

Event ID:     4709

Task Category: MMC Snapin

Level:        Error

Keywords:     

User:         AD\mbucadmin

Computer:     cph-hv-01.ad.petzfeed.com

Description:

Failover Cluster Manager encountered a fatal error.

System.ApplicationException: Unable to browse for computer objects. ---> System.ArgumentException: Value does not fall within the expected range.

  at MS.Internal.ServerClusters.NativeMethods.IDsObjectPicker.Initialize(DSOP_INIT_INFO& pInitInfo)

  at MS.Internal.ServerClusters.BrowseDSObjectsDialog.ShowDialog(IWin32Window owner, PickerTypes pickerType, Boolean multipleSelect)

  at MS.Internal.ServerClusters.BrowseDSObjectsDialog.ShowPickComputerDialog(IWin32Window owner, Boolean multipleSelect)

  --- End of inner exception stack trace ---

  at MS.Internal.ServerClusters.BrowseDSObjectsDialog.ShowPickComputerDialog(IWin32Window owner, Boolean multipleSelect)

  at MS.Internal.ServerClusters.Wizards.SelectItemsPage.OnBrowseClicked(Object sender, EventArgs e)

  at System.Windows.Forms.Control.OnClick(EventArgs e)

  at System.Windows.Forms.Button.OnClick(EventArgs e)

  at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)

  at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

  at System.Windows.Forms.Control.WndProc(Message& m)

  at System.Windows.Forms.ButtonBase.WndProc(Message& m)

  at System.Windows.Forms.Button.WndProc(Message& m)

  at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

System.ArgumentException: Value does not fall within the expected range.

  at MS.Internal.ServerClusters.NativeMethods.IDsObjectPicker.Initialize(DSOP_INIT_INFO& pInitInfo)

  at MS.Internal.ServerClusters.BrowseDSObjectsDialog.ShowDialog(IWin32Window owner, PickerTypes pickerType, Boolean multipleSelect)

  at MS.Internal.ServerClusters.BrowseDSObjectsDialog.ShowPickComputerDialog(IWin32Window owner, Boolean multipleSelect)

Again, I can work around this by typing the name of my nodes and adding them one at time by clickingAdd. Then the validation begins and the List Disk to Be Validated test fails every time with the following error:

* Failed while verifying removal of any Persistent Reservation on physical disk {24dea968-82e9-4dbf-aacd-a0fe00236632} at node cph-hv-01.ad.petzfeed.com.

 * Failed while verifying removal of any Persistent Reservation on physical disk {24dea968-82e9-4dbf-aacd-a0fe00236632} at node cph-hv-01.ad.petzfeed.com.

If I just ignore the error and create the cluster anyway, it doesn´t function properly and complains about access to the storage.

Here is what I have tried:

• Recreating the virtual machines using different installation media but that makes no difference.
• Tried using three different Windows 10 machines when running the virtual machines but that doesn´t help either.
• Using two different Synology boxes as iSCSI target but it is the same.
• Tried using both Gen 1 and Gen 2 virtual machines with or without Secure boot enabled.

But the real funny part is that if I use the Windows Server 2016 RTM media (1607) and choose not to patch (update) the nodes everything works as expected. If I apply the updates after the cluster is up and running it seems to work okay. If I update the servers before I setup the cluster I run in to the issues described above. If I setup the same environment using Windows Server 2012 R2 it just works.

Are anyone out there able to reproduce what I am seeing or maybe someone has seen this problem before.

Hi,

We implemented 2 servers with cluster and has different roles in this cluster. and under each role, we will have some resources.

Now we find a issue because our frontend service are always up before DB resource online. that means actually some of the web service is in fake up status and only can be used after a restart.

I know that we have dependencies setup inside one roles. But can we setup dependencies as well in between different Roles. eg:

Role A startup - Role B startup - Role C startup. so that all the resources and services can be up and running in a right sequence.

or if we have any scripts to judgement and control automatically.