Failover cluster Validation

Hi
If i have production servers working on hyper v failover cluster and i want for some reason to run the validaion on the failover cluster
what is the consideration before i ran the validation ?
shall i shutdown all vms?
Thanka
MCP MCSA MCSE MCT MCTS CCNA

Hi Yasser,
Here are a few articles that might help. I've pointed out a few of the key comments here, and it appears that storage validation is the only category that will cause downtime. So if you want to validate storage, then yes, you'll need to shut them down.
http://technet.microsoft.com/en-us/library/cc732035(WS.10).aspx (Server 2008/2008R2)
"By default, the wizard warns you if storage tests have been selected but will not be run on storage that is online, that is, storage used by clustered services or applications. In this situation, you can run validation tests (including
storage tests) by creating or choosing a new logical unit number (LUN) from the same shared storage device and presenting it to all nodes. By testing this LUN, you can avoid disruption to clustered services and applications already online within the cluster
and still test the underlying storage subsystem."
http://blogs.msdn.com/b/clustering/archive/2011/06/28/10180803.aspx (Server 2008R2)
"Across these dozens of tests, only a few of them will impact running cluster workloads and these are all within the storage category, so skipping this entire category is an easy way to avoid disruptive tests."
http://technet.microsoft.com/library/jj134244#BKMK_RUN_TESTS (Server 2012/2012R2)
"If a clustered role is using a disk when you start the wizard, the wizard will prompt you about whether to take that clustered role offline for the purposes of testing. If you choose to take a clustered role offline, it will remain offline
until the tests finish."
Thanks,
Jared

Similar Messages

Failover Cluster Validation Report Error with IBM USB Remote NDIS Network device

We are setting up Microsoft Windows Server 2008 R2 Failover Cluster on IBM X3850 X5 and get errors in the Failover cluster Validation Report due to the IBM USB Remote NDIS Network Device is using APIPA adresses and both servers are using same APIPA-adresse.
How should I configure the Server and OS for the Failover cluster to be MS approved?
IBM don't recommend that i disable the Network device, but it is a possible solution!?!

What I did was use ipconfig /all to see the settings it is using and then when and set the ip setting on the NDIS driver to be that except I increment the last value by 1 for each node so that they do not have the same IP address. I ran the
cluster validation again and it came up clean and I have not experienced any issues yet. It does give warnings about it being an Automatic Private IP Address and should not be used, which is ok because we are not going to use it anyways.
Rich Baumet

Failover cluster validation errors

We are trying to set up a failover cluster file server between two domain controllers running Windows Server 2012 RC.
When we go through the Validate Configuration wizard, we receive the following errors messages against the Active Directory configuration (names have been changed).
"It could not be determined whether node computer1.example.com is a read only domain controller because of this error: The object does not exist."
and
"Node(s) computer1.example.com computer2.example.com cannot reach a writable domain controller. Please check connectivity of these nodes to the domain controllers."
Does anyone have any ideas why this might be happening? Replication and DNS appear to be working fine for all other services.

I did some tracking down of the problem, and it appears that it stems from the cluster not being able to retrieve the node names. The function specifically is called GetFqdnNodeNamesFromCluster( ).
It can be seen if you run "Get-ClusterLog" while the cluster is in the process of being created. This error seems to be the root of the cluster creation failure. Here is a stacktrace:
PS C:\Users\gamroot> Get-ClusterLog -v
VERBOSE: Connecting to cluster on local computer TESTNODE1.
VERBOSE: at MS.Internal.ServerClusters.Cluster.GetNodes()
at Microsoft.FailoverClusters.PowerShell.FCCmdlet.GetFqdnNodeNamesFromCluster(Cluster cluster, Boolean onlineOnly)
at Microsoft.FailoverClusters.PowerShell.GetClusterLogCommand.WrappedProcessRecord()
at Microsoft.FailoverClusters.PowerShell.FCCmdlet.ProcessRecord()
VERBOSE: at MS.Internal.ServerClusters.Cluster.GetCoreClusterGroup()
at MS.Internal.ServerClusters.SafeFilteredEnumHandle..ctor(Cluster cluster, Boolean filterCoreGroups, Boolean
filterCoreResources)
at MS.Internal.ServerClusters.SafeClusterEnumHandle..ctor(Void* enumHandle, Cluster cluster, ClusterEnumType
enumType, SafeClusterEnumHandleOptions options, SafeClusEnumHandleType safeClusEnumHandleType)
at MS.Internal.ServerClusters.NativeMethods.ClusterOpenEnum(Cluster cluster, ClusterEnumType enumType,
SafeClusterEnumHandleOptions options)
at MS.Internal.ServerClusters.Cluster.GetNodes()
VERBOSE: at MS.Internal.ServerClusters.ClusterRegistryKey.GetValue(String name)
at MS.Internal.ServerClusters.Cluster.GetCoreClusterGroup()
VERBOSE:
Get-ClusterLog : Failed to retrieve the list of nodes for 'TESTCLUSTER1'.
Could not retrieve the core cluster group for the cluster 'TESTCLUSTER1'.
An error occurred while querying the value 'ClusterGroup'.
Element not found
At line:1 char:1
+ Get-ClusterLog -v
+ ~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (:) [Get-ClusterLog], ClusterCmdletException
+ FullyQualifiedErrorId : NotFound,Microsoft.FailoverClusters.PowerShell.GetClusterLogCommand

Failover Cluster Validation Report with warnings

Hi,
I have 2 Node cluster on windows 2008 R2.I have run cluster validation report and found following warnings pls suggest and guide me health of cluster and how to fix and remove these warnigns. thx.
Validate All Drivers Signed
Validate that tested servers contain only signed drivers.
Validating that the servers contain only signed drivers...
The node 'cluster1.domain.com'has unsigned drivers.
Device Name Device Class Driver Version Driver Date Manufacturer Inf Name Driver Name Device ID Description Status Start Mode
Virtual CloneDrive SCSIADAPTER 5.4.4.3 1/15/2011 12:00:00 AM Elaborate Bytes AG oem1.inf Value Not Found ROOT\SCSIADAPTER\0000 Virtual CloneDrive Value Not Found Unknown
Unsigned drivers were found on one or more of the servers.

Hi,
you need to run iso files at your cluster nodes often?
Well i think you need to provide iso files to your VMs. This is possible without "Virtual CloneDrive"!
I have seen many errors with this kind of software up to bluescreens.
But ok if you really need this software just ignore the warning from cluster validation report.
The cluster will work correctly if this are the only warnings from cluster validation report.
Regards
Sebastian

Failover cluster validation tool report

I have two same model and config HP server form 2 nodes cluster, in Windows 2008R2 enterprise, when use failover cluster manager validate a configure, the result report said system configuration - software update level, some software updates missing on 1
node:
KB3029944, KB3023562, KB3021952, KB3013455, KB3004394, KB2980245, KB2926765, KB2913152, KB2862966, KB2847311 and KB2709981 (all version is correct for Windows 2008R2 64bit)
I try manual download from Microsoft and standalone install, all security update get "The update is not applicable to your computer" .
So how to install security update back the sever match 2 nodes software level ?

Both server is same day purchasing inside hardware and firmware is same, only deploy Windows days is not same, Windows update method via internet, if both server is same why after Windows update some
software updates missing on 1 node ?
Honestly the failover cluster manager validate report all pass except system
configuration - software update level not pass, if
I don't care missing updates form cluster any large critical will happen?

Access is denied messages in Win2012 R2 Failover Cluster validation report and CSV entering a paused state

Been having some issues with nodes basically dropping out of clusters config.
Error showing was
"Cluster Shared Volume 'Volume1' ('Data') has entered a paused state because of '(c000020c)'. All I/O will temporarily be queued until a path to the volume is reestablished."
All nodes (Poweredge 420) connected a Dell MD3200 shared SAS storage.
Nodes point to Virtual 2012 R2 DC's
Upon running validation with just two nodes, get the same errors over and over again.
Bemused!
List Software Updates
Description: List software updates that have been applied on each node.
An error occurred while executing the test.
An error occurred while getting information about the software updates installed on the nodes.
One or more errors occurred.
Creating an instance of the COM component with CLSID {4142DD5D-3472-4370-8641-DE7856431FB0} from the IClassFactory failed due to the following error: 80070005 Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)).
and
List Disks
Description: List all disks visible to one or more nodes. If a subset of disks is specified for validation, list only disks in the subset.
An error occurred while executing the test.
Storage cannot be validated at this time. Node 'zhyperv2.KISLNET.LOCAL' could not be initialized for validation testing. Possible causes for this are that another validation test is being run from another management client, or a previous validation test was
unexpectedly terminated. If a previous validation test was unexpectedly terminated, the best corrective action is to restart the node and try again.
Access is denied
The event viewer on one of the hosts shows
Cluster node 'zhyperv2' lost communication with cluster node 'zhyperv1'. Network communication was reestablished. This could be due to communication temporarily being blocked by a firewall or connection security policy update. If the problem persists
and network communication are not reestablished, the cluster service on one or more nodes will stop. If that happens, run the Validate a Configuration wizard to check your network configuration. Additionally, check for hardware or software errors related
to the network adapters on this node, and check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk.
Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected
such as hubs, switches, or bridges.
Only other warning is because the 4 nic ports in each node server are teamed on one ip address split over two switches - I am not concernd about this and could if required split then pairs, I think this is a red herring????

Hi,
Such events happen because of the following reason:
1- Client for Microsoft Networks and File and Printer Sharing for Microsoft Networks not enabled on all network interfaces. Check this KB article: http://support.microsoft.com/kb/2008795
. Please make sure these two protocols are enabled on all cluster networks
2- Network connectivity issue can cause this event as well. Please make sure the network cabling/Cards/Switches are correctly configured and working as expected
3- Connectivity issue with the storage can also cause this event. Please make sure all the nodes are connected to storage. Check HBA/Cabling connectivity to SAN. Make sure
that the SAN drivers are up-to-date.
4- Antivirus may interrupt network communication and cause this failure. Please exclude CSV volumes from being scanned by AV: http://social.technet.microsoft.com/wiki/contents/articles/953.microsoft-anti-virus-exclusion-list.aspx
5- Disable TCP Chimney related settings on all cluster nodes. http://support.microsoft.com/kb/951037
6- Please check the Network Binding Order (http://social.technet.microsoft.com/Forums/windowsserver/en-US/2535c73a-a347-4152-be7a-ea7b24159520/hyperv-r2-csv-cluster-recommended-binding-order?forum=windowsserver2008r2highavailability)
7- Firewall Rules For All Inbound and Outbound For Cluster and Hyper-V for all the Profiles
8- Update NIC Driver/Firmware.
9- Check Compatibility of the NIC with Windows Server 2012R2
10- Set-NetAdapterRss - Resources and Tools for IT Professionals | TechNet : http://technet.microsoft.com/en-us/library/jj130863.aspx
11- Check the Following Article http://social.technet.microsoft.com/Forums/windowsserver/en-US/e06fede9-931c-4dee-8379-4fd985e20f0a/hypervvmswitch-eventid-106
12- General Updates to be applied on the nodes :
Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update rollup: November 2013 : http://support.microsoft.com/kb/2887595
Windows 8.1 and Windows Server 2012 R2 General Availability Update Rollup :
http://support.microsoft.com/kb/2883200
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Install Guide - SQL Server 2014, Failover Cluster, Windows 2012 R2 Server Core

I am looking for anyone who has a guide with notes about an installation of a two node, multi subnet failover cluster for SQL Server 2014 on Server Core edition

Hi KamarasJaranger,
According to your description, you want configure a SQL Server 2014 Multi-Subnet failover Cluster on Windows Server 2012 R2. Below are the whole steps for the configuration. For the detailed steps about the configuration, please download
and refer to the
PDF file.
1.Add Required Windows Features (.NET Framework 3.5 Features, Failover Clustering and Multipath I/O).
2.Discover target portals.
3.Connect targets and configuring Multipathing.
4.Initialize and format the Disks.
5.Verify the Storage Replication Process.
6.Run the Failover Cluster Validation Wizard.
7.Create the Windows Server 2012 R2 Multi-Subnet Cluster.
8.Tune Cluster Heartbeat Settings.
9.Install SQL Server 2014 on a Multi-Subnet Failover Cluster.
10.Add a Node on a SQL Server 2014 Multi-Subnet Cluster.
11.Tune the SQL Server 2014 Failover Clustered Instance DNS Settings.
12.Test application connectivity.
Regards,
Michelle Li

Microsoft update KB 3002657 and 2008 R2 failover cluster for virtualization

After installing Microsoft update KB 3002657 on my Windows 2008 R2 failover cluster for virtualization, nodes in cluster lost connection to CSV and all my VM's were moved to node owning the volume.
I lost whole day to solve that problem.
But should i keep that update not installed on cluster nodes or anyone maybe has a solution for that ?

Hi a3pl,
Unfortunately, the available information is not enough to have a clear view of the occurred behavior from the cluster perspective. Please offer us
more information such as the failover cluster validation error, the failover error event ID, with the current information it is difficult to presume which part may cause this issue, we strongly suggest you install the following update when you use failover
cluster.
Recommended hotfixes and updates for Windows Server 2008 R2-based server clusters
http://support.microsoft.com/en-us/kb/980054
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]

Windows 2012 Server multinode failover cluster (6 nodes)

Dear All,
We are facing problem of Huge time takes for cluster validation test on IBM Blade Server with Storage. The details are given below.
Escalated with IBM OEM, confirmed that "there is no hardware issue with Server and storage, Please take support from OS (Microsoft) OEM as 2 node validation test is working fine".
Server : IBM BladeCenter S-HS23
OS : Windows 2012 X64 Datacenter Edition
MPIO.SYS Version: Default came from OS
Note : Failover cluster validation test is successful on 2 nodes in 15 min with 5 shared volumes between 2 nodes and also between set of 2 on other 6 nodes.
When we are running validation test on 6 nodes its taking 30 min in list and more than 45 min potential cluster disk.
Thanks in adv for support from your end....
T & R,
Kamlesh
kamlesh

Hello,
I'd ask in the
High Availability (Clustering) subforum of the Windows Server forums.
Karl
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
My Blog:http://unlockpowershell.wordpress.com
My Book:Windows PowerShell 2.0 Bible
My E-mail: -join ('6F6C646B61726C40686F746D61696C2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}})

Failover cluster fails validation after a single node restart

I had a lab environment setup that works great, passes validation, can do live migrations without issue but as soon as I restarted one of the nodes, the then still live node became the only node able to access the storage backend. What's weird is that the restarted
node can still access the CSV storage and run VMs off of it, but the validation report is unable to list the actual disks.
My Cluster consists of 2 nodes. I have an iSCSI backed shared storage server and I can see that both of my nodes
are connected to the iSCSI targets successfully, but the node I first restarted no longer lists any disks/volumes in disk management and the once available MPIO menus are disabled in the iSCSI control panel. I also tried to restart the second node after the
first node came back but although the first node was up and running and had VMs on it, restarting the second node brought the entire cluster down. I see event IDs 1177, 1573, and 1069 appear in the Cluster Events log. When the second node came back up, the
cluster came back with it, but not the storage. Both nodes seem to display similar behavior in that they cannot access the storage backend. Now the storage is inaccessible by both nodes. I was able to get both nodes connected to the storage backend by
going to the iscsicpl and disconnecting all current connections to the iSCSI backend and adding them back. Doing the test again after bringing the storage back up resulted in the same behavior and this time redoing the iSCSI connections is not helping.
I think the issue here is that the first node I restarted is unable to see any disks/volumes from the storage backend only after joining the cluster and doing a restart. Before joining the cluster I did reboots on both nodes and both were able to connect to
the iSCSI backend without issue. It wasn't until after joining the cluster that node 1 became unable to access the storage backend after reboots. The validation report fails with "No disks were found on which to perform cluster validation tests. To correct
this, review the following possible causes: ..." although none of the suggestions seem applicable and the validation report was successful right before the restart of the node.
Does anyone have suggestions on how to further troubleshoot or resolve this issue?
I am using Hyper-V Server 2012 R2 on both nodes and they are joined to the same domain.

Hi,
I don’t found the similar issue, please your storage compatible with server 2012R2, Update Network Card Drivers and firmware on both the Nodes, temporarily disable your AV
soft and firewall install the Recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters update.
The Recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters
http://support.microsoft.com/kb/2920151/en-us
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Very Strange Network Issue With Two Guests on 2012 R2 Hyper-V Failover Cluster

Hi all. We're having a odd issue with two guests on our 2012 R2 failover cluster.
In a nutshell, if we shutdown a particular server (I'll call it Server A) another totally different server (Server B) on the same node loses it's network connectivity to the domain. If we start server A back up, network connectivity returns on server B.
At first I thought server A might be running a service that was somehow linked to server B, so I decided to disable server A's NIC. Interestingly, that had no affect on server B's connectivity.
The next step I tried was pausing server A and again, no adverse affect on server B's connectivity.
Next step was to live migrate server A to another node. This action did
cause server B to lose its network connection.
One other clue is that if I ping server B from either of the Hyper-V hosts in the cluster, I never lose network connection to server B.
So I would suspect this is some network issue on the cluster, but I'm kind of at a loss where to go from here.
Has anyone seen this behavior before or does anyone have any troubleshooting suggestions I can try?
Thanks!
George Moore

Hi Sir,
I'v never seen this before .
>>Next step was to live migrate server A to another node. This action did
cause server B to lose its network connection.
They are connecting to same virtual switch ?
First please run cluster validation to check if there is any error .
If it is ok , please try the following items for troubleshooting :
1. shutdown serverA serverB
2. then add another virtual NIC for serverB
3. start server B check if the issue happens to both "old" and "new" virtual NIC .
In addition , you can live migrate both A and B to another node , then try to live migrate A to the original node .
If the issue persists , I would suggest you to remove that virtual switch on both nodes then re-create them .
Best Regards,
Elton Ji
If it is not the answer please unmark it to continue
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] .

Cannot add multiple members of a failover cluster to a DFSR replication group

Server 2012 RTM. I have two physical servers, in two separate data centers 35 miles apart, with a GbE link over metro fibre between them. Both have a large (10TB+) local RAID storage arrays, but given the physical separation there is no physical shared storage.
The hosts need to be in a Windows failover cluster (WSFC), so that I can run high-availability VMs and SQL Availability Groups across these two hosts for HA and DR. VM and SQL app data storage is using a SOFS (scale out file server) network share on separate
servers.
I need to be able to use DFSR to replicate multi-TB user data file folders between the two local storage arrays on these two hosts for HA and DR. But when I try to add the second server to a DFSR replication group, I get the error:
The specified member is part of a failover cluster that is already a member of the replication group. You cannot add multiple members for the same cluster to a replication group.
I'm not clear why this has to be a restriction. I need to be able to replicate files somehow for HA & DR of the 10TB+ of file storage. I can't use a clustered file server for file storage, as I don't have any shared storage on these two servers. Likewise
I can't run a HA single DFSR target for the same reason (no shared storage) - and in any case, this doesn't solve the problem of replicating files between the two hosts for HA & DR. DFSR is the solution for replicating files storage across servers with
non-shared storage.
Why would there be a restriction against using DFSR between multiple hosts in a cluster, so long as you are not trying to replicate folders in a shared storage target accessible to both hosts (which would obviously be a problem)? So long as you are not replicating
folders in c:\ClusterStorage, there should be no conflict.
Is there a workaround or alternative solution?

Yes, I read that series. But it doesn't address the issue. The article is about making a DFSR target highly available. That won't help me here.
I need to be able to use DFSR to replicate files between two different servers, with those servers being in a WSFC for the purpose of providing other clustered services (Hyper-V, SQL availability groups, etc.). DFSR should not interfere with this, but it
is being blocked between nodes in the same WSFC for a reason that is not clear to me.
This is a valid use case and I can't see an alternative solution in the case where you only have two physical servers. Windows needs to be able to provide HA, DR, and replication of everything - VMs, SQL, and file folders. But it seems that this artificial
barrier is causing us to need to choose either clustered services or DFSR between nodes. But I can't see any rationale to block DFSR between cluster nodes - especially those without shared storage.
Perhaps this blanket block should be changed to a more selective block at the DFSR folder level, not the node level.

Server 2008 Hyper-V Failover Cluster Error on Domain Controller Reboot

I am pretty new to Hyper-V virtual but I have 2 Hyper-V Clusters, each with 2 Nodes and a SAN, 1 Physical Domain Controller for failover cluster management and 1 virtual domain controller as backup. All is running well, no issues. I installed
windows updates on the physical DC and upon reboot, got an error 5120 on cluster 2 that says "Cluster Shared Volume 'Volume1' ('Cluster Disk 1') is no longer available on this node because of 'STATUS_CONNECTION_DISCONNECTED(c000020c)'. All I/O will
temporarily be queued until a path to the volume is reestablished. It pointed to the 2nd node in that cluster as being the issue but when I look at it, it is online and all healthy so I don't understand why the error was triggered and if the DC would
go down for a failure, would that node not be able to access the CSV permanently.
Appreciate any help anyone can provide.

Hi mtnbikediver,
In theory, if you has the correct configuration of cluster the DC restart will not cause the CSV down, does your shared storage installed on your DC? Did you run
the cluster validation before you install the cluster? We strongly recommend you run the cluster validation before you build the cluster, same time please install the recommend update of 2008 cluster first.
Recommended hotfixes for Windows Server 2008-based server clusters
http://support.microsoft.com/kb/957311
I found a similar scenario issue the DC restart will effect the cluster network name resource offline, but it is for 2008R2.
Cluster network name resource cannot be brought online when one of the domain controllers is partly down in Windows Server 2008 R2
http://support2.microsoft.com/?id=2860142
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 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 2008 Failover Cluster - Cannot add a generic service

Trying to add a generic service in a failover cluster.
Select the option Services and Application and it opens the wizard and then displays the error "An error was encountered while loading the list of services. QueryServiceConfig failed. The system cannot find the file specified"
The cluster validation wizard completes successfully. Permissions do not appear to be an issue as this account can seemly do everything else so I am at a loss to understand why this API is failing when it tries to query the server for services information.
Having searched the Internet the only thing I have found was someone posting a similar issue in the Greek language Technet forum(if I recall correctly) and their comment was they rebuild their cluster.
Windows 2008 (SP2) x64 two node cluster running a non-Microsoft database. We need to add a non-Microsoft Enterpirse backup solution and this is their documented method (adding it as a generic service) - both bits of software are from big vendors.
Symantec AV, but have tried with that disabled so don't think it has anything to do with that. Something is stopping the API from reporting back but I can't find what.
Really appreciate some help before we have to log a chargable call with Microsoft support
Thank you

Hi,
Have you tried the suggestion? I want to see if the information provided was helpful. Your feedback is
very useful for the further research. Please feel free to let me know if you have addition questions.
Best regards,
Vincent Hu

Failover cluster Validation

Similar Messages

Maybe you are looking for