Inexplainable 2008 Failover Cluster Issues

Hi,
We have a 2008 Failover Node & Disk Majority SQL 2005 cluster.
There are 2 nodes in the cluster with 2008 Ent 64-bit SP2 installed.
At around 00:20 each morning we see various FailoverClustering errors in the event logs on both servers.
EventID: 1135, 1069, 1177
Before the FailoverClustering events are seen, 2 informational events appear regarding the 'Microsoft Failover Clustering Virtual Adapater'
EventID: 4201 'The system detected that network adapter Local Area Connection* 9 was connected to the network, and has initiated normal operation.'
This is causing the resources to failover to the secondary node.
I have run the Cluster Validation Wizard and everything passes. I have disabled the Windows Firewall service on both nodes.
We are presenting the storage via NetApp and the nodes have 3 nics installed
NIC1 - Server Vlan - Speed/Duplex Set to 1000Mb Full
NIC2 - Storage Vlan - Speed/Duplex Set to 1000Mb Full
NIC3 - Heartbeat - Speed/Duplex Set to 100Mb Full
Please can anyone help me troubleshoot these issues ?
Thanks
Scott

Hi Scott,
Event ID 1135 — Cluster Service Startup
http://technet.microsoft.com/en-us/library/dd353973(WS.10).aspx
Event ID 1069 — Clustered Service or Application Availability
http://technet.microsoft.com/en-us/library/dd353893(WS.10).aspx
Event ID 1177 — Quorum and Connectivity Needed for Quorum
http://technet.microsoft.com/en-us/library/dd353872(WS.10).aspx
Event ID 4201 — TCP/IP Network Interface Connectivity
http://technet.microsoft.com/en-us/library/dd392958(WS.10).aspx
Hope it helps.
Tim Quan - MSFT

Similar Messages

Is there any way to enable eventlog replication between two nodes in windows 2008 failover cluster.

Is there any way to enable eventlog replication between two nodes in windows 2008 failover cluster.
Thanks Azam When you see answers please Mark as Answer if Helpful..vote as helpful.

Hi,
As far as I know there don’t have the log replica function between failover cluster node, if you want to have the Unified log management you can refer the following related
KB:
Configure Computers to Forward and Collect Events
http://technet.microsoft.com/en-us/library/cc748890.aspx
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.

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

MSDTC set up in SQL Server 2008 failover cluster

Hi Guys,
I am in the process of setting up failover cluster using SQL Server 2008 (64Bit) Enterprise on Windows Server 2008 R2 (64Bit) I have completed almost all the works but I got few questions regarding MSDTC configuration whether the MSDTC disk should
be assigned from SAN or it should be local to the disk , Separate disk for each nodes in the cluter or 1 disk to be used across all the servers for MSDTC in windows fail over cluster.
With regards, Gopinath.

Hi Gopinath,
Please review the following similar blogs to get more details about configuring MDTC and pros & cons of different options.
How to Configure Multiple Instances of Distributed Transaction Coordinator (DTC) on a Windows Server Failover Cluster 2008
http://blogs.technet.com/b/askcore/archive/2009/02/18/how-to-configure-multiple-instances-of-distributed-transaction-coordinator-dtc-on-a-windows-server-failover-cluster-2008.aspx
How to configure DTC for SQL Server in a Windows 2008 cluster
http://blogs.msdn.com/b/cindygross/archive/2009/02/22/how-to-configure-dtc-for-sql-server-in-a-windows-2008-cluster.aspx
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

2008 Failover cluster unable to create computer account

Hello,
I have created a 2008 R2 Failover cluster and I am trying to add a Fail over File server to this.
I get the dreaded
Cluster network name resource 'OfMaClusterFS' failed to create its associated computer object in domain 'xxx.domain' for the following reason: Unable to create computer account.
The text for the associated error code is: Access is denied.
Please work with your domain administrator to ensure that:
- The cluster identity 'OFMACLUSTER$' can create computer objects. By default all computer objects are created in the 'Computers' container; consult the domain administrator if this location has been changed.
- The quota for computer objects has not been reached.
- If there is an existing computer object, verify the Cluster Identity 'OFMACLUSTER$' has 'Full Control' permission to that computer object using the Active Directory Users and Computers tool.
I have created clusters frequently in the past, on my own Domains that I am a domain admin of. Now I am trying to make one on our larger corporate domain that I am not a domain admin of and get this error.
By default, domain users can not add computer accounts to our domain. I do however have an limited account that can add computers to the domain... but I have tried all the tricks I can think of to try and add the Network name to AD and no luck.#
I have tried running the cluster service with this account, but it is still trying to use the OFMACLUSTER$ identity to create the Network name. I have tried manually creating the network name using my limited account, but that doesn't work either,
same error. I don't have the ability to change permissions on the computer name I added for the network name to AD.
I have raised a ticket to our wintel team to try and get them to help, but they aren't exactly the most responsive bunch. I'm just wondering what the best way around this problem is if I am not a domain admin and I can't make the changes I need, or
what concise instructions I can give to the domain admins so that they can help me out without saying that it is a security breach etc.
I would appreciate any advice on this as it's now urgent and also something I will have to do in the future fairly regularly and don't want to get caught in the situation in the future.

Hi jogdial,
To create a cluster, the minimum permission is: Requires administrative permissions on the servers that will become cluster nodes. Also requires
Create Computer objects and Read All Properties permissions in the container that is used for computer accounts in the domain.
If you create the cluster name account (cluster name object) before creating the cluster—that is, prestage the account—you must give it the
Create Computer objects and Read All Properties permissions in the container that is used for computer accounts in the domain. You must also disable the account, and give
Full Control of it to the account that will be used by the administrator who installs the cluster.
The related KB:
Failover Cluster Step-by-Step Guide: Configuring Accounts in Active Directory
http://technet.microsoft.com/en-us/library/cc731002(v=ws.10).aspx
More information:
How to Create a Cluster in a Restrictive Active Directory Environment
http://blogs.msdn.com/b/clustering/archive/2012/03/30/10289577.aspx
I’m glad to be of help to you!
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.

Windows Server 2008 failover cluster in VirtualBox

Hi,
I'm a Windows NT student and I need help with understanding how to do clustering using multiple Windows 2008 R2 Enterprise servers in VirtualBox 4.3.8. I have a Windows 7 host computer. I was wondering if someone could provide clearly detailed step-by-step
directions (ex. Click this, then click that) on what I need to do prior to clustering, as well as starting the clustering process. Please ask if you need additional information.
Thank You.

I'm sorry. I'm such a noob. Should I have 3 virtual machines, where one is the domain controller and the other 2 are nodes? Or is it ok to just have 2 virtual machines?
It's optional. You just need your both cluster nodes (VMs) belong to the same domain. It can be own domain serviced by your private VM or it can be "external" one. See:
Using Guest Clustering for High Availability
http://technet.microsoft.com/en-us/library/dn440540.aspx
Active Directory domain requirements
Failover clusters require that nodes of the same cluster are members of the same Active Directory domain. However, there is no requirement that a guest cluster belongs to the same Active Directory
domain as the physical hosts on which the virtual machines are running.
Also you'll need some shared storage. See (same URL as above):
Storage options
The following tables lists the storage types that you can use to provide shared storage for a guest cluster.
Storage Type
Description
Shared virtual hard disk
New in Windows Server 2012 R2, you can configure multiple virtual machines to connect to and use a single virtual hard disk (.vhdx) file. Each virtual machine can access the virtual hard disk
just like servers would connect to the same LUN in a storage area network (SAN). For more information, see Deploy a Guest Cluster Using a Shared Virtual
Hard Disk.
Virtual Fibre Channel
Introduced in Windows Server 2012, virtual Fibre Channel enables you to connect virtual machines to LUNs on a Fibre Channel SAN. For more information, see Hyper-V
Virtual Fibre Channel Overview.
iSCSI
The iSCSI initiator inside a virtual machine enables you to connect over the network to an iSCSI target. For more information, see iSCSI
Target Block Storage Overview and the blog post Introduction of iSCSI Target
in Windows Server 2012.
Shared VHDX is out as you don't have proper software (Windows 7 is not supported as a host and Windows 2008 R2 does not support shared VHDX as a guest), virtual Fibre Channel is out as you again don't have Windows Server 2012 R2 (and don't have any FC gear).
So iSCSI is your only choice. Either spawn dedicated Windows (or other OS if you like UNIX) VM with iSCSI stack or use third-party Windows software running on your host. Windows Server 2008 R2 does not have iSCSI target embedded so you can get it here:
MSFT iSCSI Target 3.3 Download
http://www.microsoft.com/en-us/download/details.aspx?id=19867
Good luck and happy clustering :)
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

FTP in Windows 2012 Failover Cluster

Hi,
Understand that Windows 2012 is having much improved Failover Clustering features,however i have faced issues when i configured FTP in Windows 2012 Failover Cluster.
1) As per the process configured the shared disk for FTP data path.
2)Installaed FTP feature in both Nodes of Clustert
3)Finally created the Generic Service in Cluster Roles for FTP Service.
After the configuration i found everything working fine but when i try to failover the FTP role found that FTP resource is not moving smoothly. Also i observed that Microsoft FTP service gets in to "starting" mode in the destination Node. To run the FTP
resource Microsft FTP service should be in Started mode.
This happens only when we try to failover else it works fine if you start freshly.
Have any one tried this? Any clue about such issue ?
Regards:Mahesh

Hi,
In earlier versions of Internet Information Services, Microsoft provided generic resource monitor components to support high availability Web server instances by using the Microsoft Clustering infrastructure. However, custom code was needed to fully realize
the potential of this solution. Also, the generic scripts that Microsoft provided did not satisfy customer needs.
From IIS 7 to configure IIS in a clustered environment by using Windows Server failover clustering, you have to use a custom (scripting) code to enable such a high availability scenario.
Note:
We recommend that administrators carefully evaluate the use of Network Load Balancing (NLB) instead of using failover clustering as the primary and preferred method for improving the scalability and availability of Web applications that have multiple servers
that are running new IIS (from IIS 7) . One benefit of NLB is that all servers can actively participate in the concurrent handling of incoming HTTP requests. Another benefit is that in an NLB IIS environment, it can be much easier to support rolling updates
and rollbacks while still providing high availability of Web applications.
To configure high availability for IIS FTP servers using Failover Clustering:
Install the Web Server role on all cluster nodes.
Install the Failover Clustering feature on all cluster nodes and create the cluster.
Set up a file share that will be used for IIS shared configuration
Configure the IIS shared configuration on all cluster nodes
Configure Offline Files for IIS Shared Configuration on all cluster nodes
Configure the FTP site and specify the location of its content on one cluster node
Configure high availability for your FTP site by creating a generic script in Failover Cluster Manager
For more detailed configuration procedure please refer to following MS articles:
Note: I didn’t find IIS 8 in Windows Server 2012 failover cluster configuration guide, below guide was published for II 7 in Windows server 2008 and Windows Server 2008 R2, but its basis configuration procedures should also apply to Windows Server 2012.
How to configure FTP 7.5 for IIS 7.0 in a Windows Server 2008 failover cluster
http://support.microsoft.com/kb/974603
Configure IIS Network Load Balancing
http://www.iis.net/learn/web-hosting/configuring-servers-in-the-windows-web-platform/network-load-balancing
Deploying IIS on a Failover Cluster
http://blogs.msdn.com/b/clustering/archive/2009/06/01/9674799.aspx
Hope this helps!
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Lawrence
TechNet Community Support

Question about updating SQL Server on failover cluster

Hi all,
I would like to better understand the update process of SQL Server (2008 r2) in a failover cluster environment.
In our cluster we have 4 instances of SQL running, where two of them I am able to at anytime stop the instance and update it.
The question is... Applying the latest update, will update forcibly all instances installed on that node, or do I have the ability to choose which instance I want to update?
This way, I could "test" the update process in those two SQL Instances, as described in http://support.microsoft.com/kb/958734 and after finishing I would update the remaining instances.
Please let me know.
Thanks in advance.
Nuno Silva

Hi Nuno,
It's a failover cluster issue, I moved it to SQL Server High Availability and Disaster Recovery. So that you can get better help.
Regards,
Charlie Liao
TechNet Community Support

Mac10.x client can't connect to File Server on Windows2008 Failover Cluster

Installation of a cluster was made according to the document "Failover Cluster Step-by-Step Guide: Configuring a Two-Node File Server Failover Cluster " http://technet.microsoft.com/en-us/library/cc731844.aspx.
My Mac OS X 10.5.2 and Mac OS X 10.4.11 clients be able to connect to a non-cluster file server on a Windows 2008 (the File Services role) and also to old file cluster on a Windows 2003.
Why Mac clients can't connect to Windows 2008 Failover Cluster?

Are you running a firewall on the Macs. If yes does it work with out the firewall? If it works with out the firewall that means you will have to create a custom ipf rule which includes the both the physical an virtual IP addresses of your cluster.

Hyperv - 2008 R2 cluster migration

I want to migrate a Hyperv- 3 node cluster to another domain in a different forest. Is this possible, so help me with steps.

Hi,
the best way will be to rebuild the cluster at the new domain.
Here some informations_
Windows 2008 failover Cluster domain migration
http://social.technet.microsoft.com/forums/windowsserver/en-US/079cf6e9-9597-4265-b240-afa7972b2da7/windows-2008-failover-cluster-domain-migration
Moving a Hyper-V cluster to a new AD Domain
http://namitguy.blogspot.de/2012/03/moving-hyper-v-cluster-to-new-ad-domain.html
Hope that helps
Regards
Sebastian

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]

SSL Cert for 2008 R2 Reporting Services that is installed on a Failover Cluster - server address mismatch?

I utilized the idea from
http://www.mssqltips.com/sqlservertip/2778/how-to-add-reporting-services-to-an-existing-sql-server-clustered-instance/ to install 2008 R2 Reporting Services on a new Clustered SQL instance. In short, create the new Clustered SQL instance on Node1,
installing Reporting Services with it. Then on Node2, Add a Failover Cluster Node (without choosing Reporting Services); following that up with starting the SQL setup.exe with a cmd to bypass a check so that I can then install the Reporting Services
feature on Node2. It points out using the SQL Cluster Network name for connecting to Reporting Services.
I verified upon failover that I could still access the Reports and ReportServer URLs. However, when wanting to add an SSL certificate to the RS configuration, I run into the warning of "mismatched address - the security certificate presented by
this website was issued for a different website's address", where I can continue and get to the Reports or ReportManager URLs.
I played with different certs (internal CA created) and SANs and other things, but I still get this error with the cert. The Reports URL, for example, is <a href="https:///Reports">https://<SQLClusterNetworkName>/Reports, and the
cert has a CN and Friendly Name of SQLClusterNetworkName (with SAN of DNS: SQLClusterNetworkName.<domain>), but the error still happens.
What am I missing to eliminate the mismatched address warning when using the SQLClusterNetworkName as the base of the URLs?

I got it working by using the FQDN as the common name on the SSL cert, with FQDN in RS URLs.

MS DTC not coming online on SQL Server 2008 R2 failover cluster

Dear Experts,
On a SQL Server 2008 R2 failover cluster, MS DTC cluster service is not coming online. It fails with below error message.
"The DTC cluster resource's log file path was originally configured at: E:. Attempting to change that to: M:. This indicates a change in the path of the DTC cluster resource's dependent disk resource. This is not supported. The error code
returned: 0x8000FFFF".
From the Component Services, we can see under the clustered DTCs, in the properties of the log file that it is configured for E drive. The 'Transaction list' and 'Transaction Statistics' are empty. When I try to change the log file path to
point to M drive I get this warning message.
"An MSDTC log file already exists in the selected directory. Resetting an existing MS DTC log file may cause your databases and other transactional resource managers to become inconistent. Please review the MSDTC Administrator's manual before
proceeding. Do you wish to reset the existing MS DTC log"
Could you please advise if this is safe to proceed with this warning as the 'Transaction list' and 'Transaction Statistics' are empty or would it cause any other issue.
Thanks,
MM

Tauseef
Did you tried using wmi....win32_share
$path = "location where to create the folder"
$share = $Shares=[WMICLASS]'WIN32_Share' # class in wmi for share
$Sharename = 'Sharename'
New-Item -type directory -Path $Path
$Shares.Create($Path,$Sharename,0,255,$Sharename)
$Acl = Get-Acl $Path # cmdlet for getting access control list
$Access = New-Object system.security.accesscontrol.filesystemaccessrule("Username","FullControl","ContainerInherit, ObjectInherit", "None", "Allow")
$Acl.AddAccessRule($Access)
Set-Acl $Path $Acl
Thanks Azam When you see answers please Mark as Answer if Helpful..vote as helpful.

2008 R2 SP1 failover cluster, after connect to VM from failover cluster manager console I've get only upper quourter of screen console

Hello :)
I have to ask because this issue is boring me a long time ago :(
From time to time when I connect to virtual machine from failover cluster manager console I've get virtual machine connection screen (console) which is reduced only to upper left quorter of full screen. There is no scroll bar ... If I live migrate
VM to another node (or restart VM on same node) and reconnect, console screen is displayed ok (ie all console screen is visible).
It is happening regardless of OS version installed into guest VM: 2003 R2, 2008 R2, 2012, 2012 R2).
I've check inside VM ( I can see that integration services are installed and running but when I click onto console window with mouse I've get message:
"Virtual Machine Connection
Mouse not captured in Remote Desktop session
The mouse is available in a Remote Desktop session when
integration services are installed in the guest operating
system...."
From SCVMM console I can see that IC version on guest VM is: 6.1.7601.17514
I would like to know what is going on and is there any way how can I detect those situation or even better how to prevent it ?
Thank you for any idea.
Best regards
Nenad

Hi Nenad,
As you mentioned you have tried 2003 R2, 2008 R2, 2012, 2012 R2 guest vm, but all this do not work properly, With Server 2003 platform the 2008r2 Hyper-V the 2003R2 are not
supported, in your case you must update to Windows Server 2003 R2 with Service Pack 2.
Server 2012 as guest vm on 2008r2 you must install the following hot fix:
You cannot run a Windows 8-based or Windows Server 2012-based virtual machine in Windows Server 2008 R2
https://support2.microsoft.com/kb/2744129?wa=wsignin1.0
Server 2012 is the last version of Windows that will be supported as a guest operating system on 2008r2 Hyper-V therefore the 2012r2 guest vm is not supported.
Please use the following command can query all guest vm’s IC version, please compare this problematic vms IC version with functioning vms.
The following powershell command can be used to display the version of integration services installed on all VMs on the Hyper-V host:
PS C:\Users\administrator> get-vm | ft name, IntegrationServicesVersion
Name
IntegrationServicesVersion
TestVM2012
6.2.9200.16433
SQL01
6.2.9200.16433
SQL02
                                  6.2.9200.16433
SCVMM01
6.2.9200.16384
SCVMM02
6.2.9200.16384
I’m glad to be of help to you!
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.

Failover Cluster 2008 R2 - VM lose connectivity after live migration

Hello,
I have a Failover Cluster with 3 server nodes running. I have 2 VMs running in one the the host without problems, but when I do a live migration of the VM to another host the VM lose network connectivity, for example if I leave a ping running, the ping command
has 2 response, and 3 packets lost, then 1 response again, then 4 packets lost again, and so on... If I live migrate the VM to the original host, everything goes OK again.
The same bihavior is for the 2 VMs, but I do a test with a new VM and with that new VM everything Works fine, I can live migrate it to every host.
Any advice?
Cristian L Ruiz

Hi Cristian Ruiz,
What your current host nic settings now, from you description it seems you are using the incorrect network nic design. If you are using iSCSI storage it need use the dedicate
network in cluster.
If your NIC teaming is iconfigured in switch independent + dynamic, please try to disable VMQ on VM Setting for narrow down the issue area.
More information:
VMQ Deep Dive, 1 of 3
http://blogs.technet.com/b/networking/archive/2013/09/10/vmq-deep-dive-1-of-3.aspx
I’m glad to be of help to you!
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.
Hi!
thank you for your reply!
Yes, We are using iSCSI storage, but it has its own NICs for that (2 independant NIcs just to connect the server with the storage) and they are configured to not use those NICs to cluster communication. The team configuration is just for the LAN connectivity.
The NIC teaming is configured using BACS4 software from a DELL server and in Smart Load Balancing and Failover (as you can see here
http://www.micronova.com.ar/cap01.jpg). The link you passed is for Windows Server 2012 and we are running Windows Server 2008 R2, BUT as you can see in the following capture the NICs has that feature disabled
( http://www.micronova.com.ar/cap02.jpg ).
One test that I'm thinking to do is to remove teaming configuration and test just with one independant NIC for LAN connection. But, I do not know if you think another choice.
Thanks in advance.
Cristian L Ruiz
Sorry, another choice I'm thinking too is to update the driver versión. But the server is in production and I need to take a downtime window for test that.
Cristian L Ruiz

Inexplainable 2008 Failover Cluster Issues

Similar Messages

Maybe you are looking for