We have a Microsoft cluster running on 2 Server Enterprise 2008R2 Servers with the FileServices Roles (including DFS roles).  We have 3 Standalone DFS namespaces (roots) which have been up and running for a couple of months.  Users were complaining about performance so we added the DfsDnsConfig registry entry to force the FQDN format in the namespace (KB244380). 

Although it doesn't say to do so in the KB Article, I found several threads that said you also need to delete and recreate the namespaces afterwards.  This is where I got into the problem.

I deleted one of my namespaces from the Failover Cluster Manager utility.  I then recreated the namespace.  While it works, the share was empty.  This is because by default it placed the namespace in DFSRoots and we have our namespaces in DFSroot (no trailing "s").

So I am trying to delete the new namespace in DFSRoots and create it in the DFSRoot folder, but I get the error listed in the title.  This is what I've tried so far to resolve this:

1. dfsutil to remove the namespace and it fails saying the command is not supported in a cluster environment.  Fair enough.

2. I tried to delete the share (using "Share and "), but it fails saying the shared folder is a DFS namespace root.

3. I tried to find an option to add the namespace to the resource group (using "Failover Cluster Manager") but I can't find the appropriate option.  Maybe it cant be done from the "Failover Cluster Manager" unless you are created a new one, I think.

4. Of course I tried to delete the namespace (using the "DFS Management" utility) and that's where I get the error in the Title of this post.

5. I deleted the registry entry for the namespace under hklm\software\Microsoft\dfs\roots\standalone.  I did this on both Fileserver nodes in the cluster.  However then all the utilities complained that they couldn't find the namespace and I couldn't do anything with the specific namespace.  So I put the registry key back in.

At this point I don't know what else to try to delete this namespace properly.  Any assistance is appreciated.

2008 R2 Multi-Site Cluster Possible without Third Party Software?  I know it has been asked, but I haven't seen a specific answer.  We are using Dell Compellent Storage and I created several read only replicated volumes at our DR site.  I am having issues failing over to the volumes after I use cluster cli to mount the read only volumes.

Any help would be appreciated greatly!

Hi,

I have come across a confusing question

One of our customer environment is having only one Windows 2008 Domain Controller in entrire FOrest and Domain. We know that its design problem which need to be corrected on priority. But i got struct in answering some of the questions as

1) If i am running Windows 2008 Failover Cluster for SQL DB, what is the level of dependency on my Domain/Domain Controller.

2) If Single Domain Controller which is there in environment is failed due to hardware or OS problem then Failover Cluster Server will get impacted immediately or it will run some time? If it run some time and fail later then what is the stage it will get failed actually.

Pls suggest if you know any of these points, its good discussion point as well.

Regards:Mahesh

Hello,

I have a 3 node cluster that is setup as active, active, passive.  Two of the nodes report the following error when trying to connect to the cluster:

One of the active nodes is successfully able to connect the "Cluster" while the other two are not.  The objects do exists in AD and the virtual cluster name has full rights of itself.  I turned on DNS Client events logging and receive the following messages on nodes that are able to connect to the cluster:

1. DNS FQDN Query operation for the name "ClusterNodeC" and for the type 28 is completed with result 0x251D
2. DNS Cache lookup operation for the name "ClusterNodeC" and for the type 28 is completed with result 0x251D
3. DNS Cache lookup is initiated for the name"ClusterNodeC" and for the type 28 with query options 0x40026010

Any help or direction would be greatly appreciated.
Thanks,
zWindows

Hi,

We have a two node Windows Server 2008 R2 Cluster, which is experiencing issues on failover. Everything is currently running on Node 2, however we are no longer able to failover to Node 1. In the logs I see the following messages:

2014/01/27-23:24:29.840 INFO  [RES] Network Name <SQLMASTER>: DNS name SQLMASTER.here.net Registration with LSA was successful
2014/01/27-23:25:29.000 ERR   [RHS] RhsCall::DeadlockMonitor: Call ONLINERESOURCE timed out for resource 'SQLMASTER'.
2014/01/27-23:25:29.000 ERR   [RHS] Resource SQLMASTER handling deadlock. Cleaning current operation.
2014/01/27-23:25:29.000 WARN  [RCM] HandleMonitorReply: FAILURENOTIFICATION for 'SQLMASTER', gen(0) result 5018.
2014/01/27-23:25:29.000 INFO  [RCM] TransitionToState(SQLMASTER) OnlinePending-->ProcessingFailure.
2014/01/27-23:25:29.000 ERR   [RCM] rcm::RcmResource::HandleFailure: (SQLMASTER)
2014/01/27-23:25:29.000 INFO  [RCM] resource SQLMASTER: failure count: 1, restartAction: 2.

The cluster then attempts to restart the resource, brings the network name online and encounters the following errors:

2014/01/27-23:26:26.445 WARN  [RES] Network Name <SQLMASTER>: WaitForTargetToComeUp: WSA_QOS_ADMISSION_FAILURE(11010)' because of '[cxl::Pinger-"SQLMASTER"] Could not send IPv4 echo.'
2014/01/27-23:26:26.445 WARN  [RES] Network Name <SQLMASTER>: WaitForTargetToComeUp: WSA_QOS_ADMISSION_FAILURE(11010)' because of '[cxl::Pinger-"SQLMASTER"] Could not send IPv4 echo.'
2014/01/27-23:26:29.048 INFO  [RES] Network Name <SQLMASTER>: [cxl::Pinger-"SQLMASTER"] Host registered, but no records of type 23
2014/01/27-23:26:29.048 INFO  [RES] Network Name <SQLMASTER>: [cxl::Pinger-"SQLMASTER"] Host registered, but no records of type 23
2014/01/27-23:26:29.048 WARN  [RES] Network Name <SQLMASTER>: [cxl::Pinger-"SQLMASTER"] Could not find any endpoints for remote target
2014/01/27-23:26:29.048 WARN  [RES] Network Name <SQLMASTER>: [cxl::Pinger-"SQLMASTER"] Could not find any endpoints for remote target
2014/01/27-23:26:29.049 INFO  [RES] Network Name <SQLMASTER>: Setting resource specific message to <Name Resolution Not Yet Available>.

Finally the cluster attempts to start SQL Server, which fails, and the cluster fails back to Node 2 successfully.

The cluster was previously running successfully on Node 1, and to my knowledge there have been no changes to the server or cluster configuration. 

Thank you in advance for any suggestions you can provide.

-Daniel

I have created a Hyper V failover Clustering between 2 nodes. 

On both nodes in C drive it created a folder ClusterStorage where i will store the Virtual Machine on. But i get an error that the user doesnt have access to the folder. 

Also noticed that the folder ClusterStorage has the security lock on it. 

Any ideas on how to give access to the administrator user? 

I have run into a networking problem on my cluster, and I cannot figure out what changed.

I had a cluster configured and working.  Its access network is 192.168.10.0/24.  I have other networks, including a node management network on 10.29.130.0/24.  The access network is private to my lab; it's here I have my AD defined.  The management network is a 'lab' network that has a gateway available so we can access the lab from our corporate network with no issues.  In other words, the access network is only routed within my private lab, but the management network can be routed to corporate access.

But, as you know, Windows simply doesn't like creating two different networks with default gateways.  So before building the cluster, I removed the gateway from the management network, ensuring there was only a single gateway configured on each host.  Ran the validation and it came through fine (typical network warnings about non-routed networks not able to reach other networks, but that is expected and presents no problems).  Built the cluster.

I wanted to try to create an environment that would allow me to access the physical hosts through the management network, so I tried issuing a route add command specific to the management network. 

route add 10.29.130.0 mask 255.255.255.0 10.29.130.1 if 3

It didn't work as expected (I am by no means a networking expert, but I figured I would try it.)  Since it didn't work, I deleted it.

route delete 10.29.130.0 mask 255.255.255.0 10.29.130.1 if 3

Came back and ran another validation wizard on the cluster and now the validation fails with the following error (to each of the other nodes in the cluster):

Network interfaces FT4-Infra01.VSPEX.COM - Mgmt and FT4-Infra03.VSPEX.COM - Mgmt are on the same cluster network, yet address 10.29.130.37 is not reachable from 10.29.130.35 using UDP on port 3343.

I check my firewall, and those ports are open on all node for all firewall profiles.  From FT4-Infra01 (the machine I was messing with), I can ping the other nodes of the cluster.  From the other nodes in the cluster, I cannot ping FT4-Infra01.  Yes, I know ping is a different rule, but I always go back to basics.  And the fact that it is not responding to pings after playing with the route is strange.

Does anybody have any ideas about what playing with the route command could have changed?  I am assuming that is the cause because everything worked fine before issuing the command and now these errors are there.  No other changes were made to the cluster or the nodes.

.:|:.:|:. tim

I need to update Multi-path drivers on my Windows server 2008 Standred 64bit Service Pack 2. I am installing netapp_windows_host_utilities_6.0.2_x64.msi on my server and it's giving me error:

{The following hotfixes are not available on the system:

1. Q2684681 - msiscsi.sys (Required: 6.0.6002.22814 / Installed: 6.0.6002.18005)

2. Q2754704 - mpio.sys (Required: 6.0.6002.22814 / Installed: 6.0.6002.18005)

Please install the hotfixes listed and retry the installation.}

Can anybody help me to solve this problem or provide me these hotfixex. I try a lot online search and try a lot of hotfixes but no result.

Thanks,

Ravinder Kumar.

I need to update Multi-path drivers on my Windows server 2008 Standred 64bit Service Pack 2. I am installing netapp_windows_host_utilities_6.0.2_x64.msi on my server and it's giving me error:

{The following hotfixes are not available on the system:

1. Q2684681 - msiscsi.sys (Required: 6.0.6002.22814 / Installed: 6.0.6002.18005)

2. Q2754704 - mpio.sys (Required: 6.0.6002.22814 / Installed: 6.0.6002.18005)

Please install the hotfixes listed and retry the installation.}

Can anybody help me to solve this problem or provide me these hotfixex. I try a lot online search and try a lot of hotfixes but no result.

Thanks,

Ravinder Kumar.

2 Hyper-V hosts (2012 R2 DC) in Cluster config

Cluster got created BEFORE Hyper-V hosts AD Computer Objects got moved to a proper desired OU

Is there a way to move Hyper-V host AD objects now?

Will Cluster need to be re-created?

Thanks

Seb

We have Windows 2008R2 Failover cluster as 2-node and majority disk configuration.   We have several SQL services set to Start/Manual.   When we perform a failover test, these services do not start.   Is that normal?

Also, we use CommVault to backup our Quorum database.   It creates GxClusPlugin instance in the Cluster.   This instance does not failover and fails.   Has anyone advice on this?

Thanks

Using the Configure Role option in Failover Cluster Manager on Server 2012 R2.  After selecting Virtual machines from the list, upon enumeration I receive the following error:

"An item with the same key has already been added"

I've looked at other solutions to this issue but they are unrelated.  Some mention firewall configuration and others network card guid on VM.  I can create a blank VM (no operating system and no NIC) with the same results.

This error appears even if there isn't a non-highly available VM to be converted to highly available (which i've run in the past and it will just enumerate nothing).

Tied to this error is the fact that when I do try to create a highly available virtual machine, the wizard completes but the virtual machine is created as non-highly available with no error given.  This is when I tried the Configure Role option and get the error listed above (assuming both are related to each other somehow).

HA Configuration:

Servers: Windows Server 2012 R2

2 node SQL Server FCI Cluster

2 node Web Server Behind a load balancer

is it possible to use cluster disk as a shared storage for IIS Servers?

Environment

Cluster Nodes = two

Cluster Nodes OS = Windows 2012

Application = IIS

Query

I configured the cluster. I want to cluster IIS as failover cluster. For this I am using the following article. As per the direction of the below article I replaced both (SITE_NAME = "MyWebSite" andAPP_POOL_NAME = "DefaultAppPool") . Now when I try to online the generic script resource it failed.

http://support.microsoft.com/kb/970759/en-us

Please Note: When I used the same script mentioned in the above link with default web site, it works fine.

Any comment will be appreciated. Thanks. Zahid Haseeb.

Hello Everyone,

We are in the design process of building a new 2012 R2 Hyper environment having moved away from VMware.

My planned setup is

• 2 x HP360 G8 Servers,
• 1 x HP P2000 SAN,
• Interdependent switches to mange the Hyper-V management (migration traffic etc.)

I have built a test environment to help me plan our new system, at the moment the storage for the test lab is local on each physical host.

When I build the main system i will be using a HP P2000 with SAS connections to both hosts, am i going about this the right way? 

My thoughts were to setup the P2000 with a ISCI target connected to a large volume, then connect to the target via the initiator on both of my Hyper-V hosts. 

Would this then enable me to create VM's on the shared (Clustered) storage? and allow me to move servers around etc.

Hope this makes sense :)

Thank you all in advance!

Rob

We currently have 2 servers, both housing 3 VMs (6 nodes total).  2 Disk are used to house these VM's.  Cluster Disk 1 keeps going offline, which kicks 2 of our servers offline until we migrate the disk to another node (puts it into redirected mode).  We then have to restart the server to re-establish to connection to the cluster disk.  Digging around in event viewer, I saw the following:

Cluster resource 'Cluster Disk 2' in clustered service or application 'b0a21897-e59b-46c9-a495-273dc5ad2aea' failed.

Cluster physical disk resource 'Cluster Disk 2' cannot be brought online because the associated disk could not be found. The expected signature of the disk was '{92eb716c-6878-42ad-b7de-f3879d72e232}'. If the disk was replaced or restored, in the Failover Cluster Manager snap-in, you can use the Repair function (in the properties sheet for the disk) to repair the new or restored disk. If the disk will not be replaced, delete the associated disk resource.

The Cluster service failed to bring clustered service or application 'b0a21897-e59b-46c9-a495-273dc5ad2aea' 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.

I ran the cluster validation test and all seemed to check out except for Cluster Disk 1 and the two servers associated with this server, as shown below:

Validating cluster resource Cluster Disk 2.

This resource is marked with a state of 'Offline'. The functionality that this resource provides is not available while it is in the offline state. The resource may be put in this state by an administrator or program. It may also be a newly created resource which has not been put in the online state or the resource may be dependent on a resource that is not online. Resources can be brought online by choosing the 'Bring this resource online' action in Failover Cluster Manager.

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.

All disks are housed on our SAN.  Any idea where I can start troubleshooting further?  Changing the signature of the disk or finding out which application is failing?  All help is greatly appreciated.

Hello,

I am confuse with the following settings:

1. "If resource fails, attempt to restart on current node" once within 15 mintes ... no problem with this one.

2. "If restart is unsuccessful, fail over all resources in this serviceor application"

What is(are) the all recources in this service or application? Is it also the two drives in dependency?

is it also the file server share?

If YES this mean that the service (TSM) is the Manager of all other resources above, isn't it ?

Thanks,

Dom

System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Environment

Cluster Nodes = two

Cluster Nodes OS = Windows 2008R2

Application = IIS

Query

I created generic service resources of many windows services under Microsoft Failover Cluster and they are failing over successfully but when I create a generic service resource for WWW, then the WWW service is not able to online via Microsoft Failover Cluster. It stuck in online pending.

I have noticed two things.

1.) If the WWW service is set to manual and started at passive node and I manually restart the Active node then the WWW service successfully switch over to stand by/passive node. but if the WWW service is set tomanual and not started on stand by/Passive node then the WWW service is not failing over.

2.) if I kill the WWW service manually (as a test case) on Active Node via this command (taskkill /f /pid XXXX) then the WWW service failed and is not failing over to standby/passive node.

Any comment will be appreciated. Thanks. Zahid Haseeb.