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

Similar Messages

Windows 2012 Failover Cluster - File server role (vCO)

Hi,
I wonder if anybody can shed some light on a query i have.
A windows 2012 failover cluster will be built in AD domain example.uk. Cluster File server roles will be created and will reside in this domain also.
We also have a requirement to run a cluster file server role in the child domain off secure.example.uk. Is this possible? or do the file server roles and related vCO's have to reside in the same domain as the cluster (CNO).
I know the CNO can be used to create the VCO but could a prestage a VCO in the child domain of secure.example.uk.
Mark

Hi Mark,
By default CNO will create
VCO automatically in default domain computer OU, we generally use the
KISS principle to place the CNO and VCO to the same OU, and as far as I know there no known design document indicate the VCO can be placed in different domain, therefore I suggest you place the CNO and V CO at same OU.
More information:
When Creating a New Resource or Role in Windows Server 2012 R2 Failover Cluster, the Network Name Fails to Come Online or Failed to Create Associated Computer Object in Domain
http://blogs.technet.com/b/askpfeplat/archive/2014/11/17/when-creating-a-new-resource-or-role-in-windows-server-2012-r2-failover-cluster-the-network-name-fails-to-come-online-or-failed-to-create-associated-computer-object-in-domain.aspx
CNO Blog Series: Increasing Awareness around the Cluster Name Object (CNO)
http://blogs.technet.com/b/askcore/archive/2012/09/25/cno-blog-series-increasing-awareness-around-the-cluster-name-object-cno.aspx
How to Create a Cluster in a Restrictive Active Directory Environment
http://blogs.msdn.com/b/clustering/archive/2012/03/30/10289577.aspx
Prestage Cluster Computer Objects in Active Directory Domain Services
https://technet.microsoft.com/en-us/library/dn466519.aspx
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 Failover Cluster

Having a problem creating 2 node cluster. I launch FCM, begin the process of adding nodes. Node 1 goes in fine. Node 2 gives an error which is, "unable to connect to xxx.xxxx.com via WMI. This may be due to networking issues
or firewall configuration.
Node 1 and 2 are virtual. Have tried them on the same metal and on different metal.
Any advice would be much appreciated.

Hi shageman0304,
Unfortunately, the available information is not enough to have a clear view of the occurred behavior. Could you provide more information about your environment. For example,
the exact text of any error? When this problem occurs the system log record information, screenshots is the best information.
If you have install any third party software on this node please disable or exit them, please install the Recommended hotfixes and updates for Windows Server 2012-based failover
clusters updates then monitor this issue again.
Recommended hotfixes and updates for Windows Server 2012-based failover clusters
http://support2.microsoft.com/kb/2784261
After install the updates, if the issue still exist please performing the following steps:
1. Open Task Manager on the affected server and check if the wmiprvse.exe is running if not please enable the wmi service.
2. Restart wmi service.
3. Restart the server.
Please rerun the validation test then post the error part, that report will quickly locate the issue.
More information:
Unable to launch Cluster Failover Manager on any node of a 2012/2012R2 Cluster
http://blogs.technet.com/b/askcore/archive/2013/12/17/unable-to-launch-cluster-failover-manager-on-any-node-of-a-2012-2012r2-cluster.aspx
Event Logs
http://technet.microsoft.com/en-us/library/cc722404.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.

Apply SP1 to SQL 2012 clustered on a Windows 2012 failover cluster

For earlier versions of clustering there was an ability to prevent a resource from failing to a particular node. I used this when service packing clusters to ensure that no SQL instances would attempt to fail back to the node I was patching. That ability
doesn't seem to exist anymore. ANd pausing or stopping a node causes rule failure in the SP setup.
Has anyone successfully performed this patching and are there any best practises or tips to follow?
Regards, Matt Bowler MCITP, My Blog

Hello Matt,
This is still available, though I'm not sure where you remember it being. You can choose individual resources in a resource group and can also do it at the resource group level as well. It's in the properties of each level and allows each resource or resource
group to be allowed to run on only the nodes selected.
Here is the KB on it (though they use the command line):
http://support.microsoft.com/kb/958734
I'd patch the instances on the nodes that the instance is not currently active (if more than 1), pause the node and reboot if necessary. Continue rolling until services need to be moved or your patched nodes outweigh your unpatched nodes at which point I'd
move the services and patch all remaining nodes.
-Sean
Sean Gallardy | Blog |
Twitter

The lease timeout between avaiability group and the Windows Server Failover Cluster has expired

Hi,
I am having some issues where I get a lease timeout from time to time. I have a Windows 2012 Failover Cluster with 2 nodes and 2 SQL 2012 Always-on Availability Groups. Both nodes
are a physical machines and each node is the primary for an AG.
From what I understand if
the HealhCheckTimeout
is exceeded without the signal exchange the lease is declared 'expired' and the SQL Server resource dll reports that the SQL Server availability group no longer 'looks alive' to the Windows cluster manager. Here are the properties I have setup
which are the default settings:
LeaseTimeout - 20000
HealthCheckTimeout - 30000
VerboseLoging - 0>
FailureConditionLevel – 3
Here are the events that occur in the Application Event Viewer:
Event ID 19407:
The lease between availability group 'AG_NAME' and the Windows Server Failover Cluster has expired. A connectivity issue occurred between the instance of SQL Server and the Windows Server Failover
Cluster. To determine whether the availability group is failing over correctly, check the corresponding availability group resource in the Windows Server Failover Cluster.
Event ID 35285:
The recovery LSN (120881:37533:1) was identified for the database with ID 32. This is an informational message only. No user action is required.
SQl server logs are too long to post in this box but I can send them if you request.
The AG is setup to failover automatically but it did not failover. I am trying to figure out why the lease timed out. Thanks.

From what I've been able to find out, this is due to an issue with the procedure sp_server_diagnostics. It sounds like the cluster is expecting this procedure to regularly log good status "Clean" in the log files, but the procedure is designed not
to flood the logs with "Clean" messages, so only reports changes, and does not make an entry when the last status was "Clean" and the current status is "Clean". The result is that the cluster looks to be unresponsive. However, once it initiates
the failover, the primary machine responds, since it was never really down, and the failover operation stops.
The end result is that there really never is a failover, but the database becomes unavailable for a few minutes while this is resolved.
I'm going to try setting the cluster's failure condition level to 2 (instead of 3) and see if that prevents the down time.
blogs.msdn.com/b/sql_pfe_blog/archive/2013/04/08/sql-2012-alwayson-availability-groups-automatic-failover-doesn-t-occur-or-does-it-a-look-at-the-logs.aspx

Mount Points in Windows 2012 R2 Cluster not displaying correctly

Hi,
Try
and I might, I can't get Mount Points displayed properly in a Windows 2012 R2 cluster.
In Windows 2008 R2, I added them, and they appear under Storage, as for Example, Cluster Disk 7: Mounted Volume (S:\SYSDB). (I may have had to bring them offline/online).
in Windows 2012 R2, they are showing up as, for example, '\\?\Volume{7c636157-e7e9-11e4-80dc0005056873123}'
In the error log it shows up as :
Cluster disk resource 'Cluster Disk 7' contains an invalid mount point. Both the source and target disks associated with the mount point must be clustered disks, and must be members of the same group.
Mount point 'SYSDB\' for volume '\\?\Volume{7c636106-e7e9-11e4-80dc-005056873123}\' references an invalid target disk. Please ensure that the target disk is also a clustered disk and in the same group as the source disk (hosting the mount point).
Now I've checked the error, and in
https://technet.microsoft.com/en-au/library/dd353925(v=ws.10).aspx it says
"The mounted disk and the disk it is mounted onto must be part of the same clustered service or application. They cannot be in two different clustered services or applications, and they cannot be in the general pool of Available Storage in the cluster."
So I have created a 'Other Server' Role. When I go right click on the Role and go to 'Add Storage', Cluster Disk 6 (the root volume) displays S:\, and Cluster Disk 9 (hosting the mountpoint) says Mount Point(s): (S:\SYSDB). I select both, and add, but
alas, the Mount Point still shows up as '\\?\Volume{7c636106-e7e9-11e4-80dc-005056873123}\ (not S:\SYSDB or Cluster Disk 6: Mounted Volume (S:\SYSDB).) as I would expect.
They are both clustered disks (iSCSI). I would expect when it says in the "same group", both added to the same role would be in the same group.

Hi,
Thankyou for your response. That's (sort of) good to know, but it seems to be a step backwards from Windows 2008 R2, where you would actually have the meaningful Mounted Volume: (S:\SYSDB) displayed, to the meaningless '\\?\Volume{7c636157-e7e9-11e4-80dc0005056873123}'
GUID. Obviously before you do anything, you need to cross reference the disk number to 'Disk Management'; it would be better if is was displayed correctly in Failover Cluster Manager in the first place.
Secondly, the GUID is somewhat misleading. In Windows 2008 R2 for example, it appears as though the same GUID was displayed on each node (e.g. using Mountvol.exe). In Windows 2012 R2, it appears as though different GUID's are displayed on each node, e.g.
Node 1.
\\?\Volume{7c6368a4-e7e9-11e4-80dc-005056873123}\
S:\SYSDB\
Node 2.
\\?\Volume{97cc0d34-e7e9-11e4-80db-0050568724c4}\
S:\SYSDB\
But the GUID in Failover cluster manager remains the same (you can't really cross reference with what you see in FCM to Mountvol).
Strangely enough, when I check the registry in 'MountedDevices' on Node 1, both of the GUIDs are displayed (even though only one is displayed in MountVol.exe), referencing the same Disk ID listed in Diskpart.exe. I can see this mentioned in
https://support.microsoft.com/en-us/kb/959573, where is says :
A volume can be multiple unique volume names (and thus multiple GUIDs) when it is used by multiple running installations of Windows. This could happen in the following scenarios and in similar scenarios where multiple installations of Windows have
accessed the volume:
Using a volume on a shared disk in a cluster where multiple nodes have accessed the volume.
Oh well, that's progress I guess.

Virtual Domain Controllers in 2012 Failover Cluster. Time Skew

Hi All,
Not sure if this is the correct space for this topic, however i'll give it a go anyway.
We have a 2 Hosts (HP DL385) Windows Server 2012 Failover Cluster.
Storage is provided by a 12 Bay NAS with iSCSI connections (This is catering for CSV's and Quorum)
We are running 2 Virtual domain controllers (2008R2)
The issue we experience is that if the cluster goes down, and when it comes back online the time on the domain controllers (one or the other or both) skews by any where up to 3 days which causes havoc for our office until we can resync clocks with the PDCe.
Time Synchronisation Integration Service is disabled on both Domain Contollers
A few days back we need to reboot the storage on the cluster, and the tasks performed were as follows:
-Power off all virtual machines (Graceful Shutdown)
-Put all CSV's into maintenance mode
-Offline Disk Witness to Quorum
-Rebooted Storage (Waited until it came back online)
-Online Quorum Storage (Successful)
-Bring CSV's out of maintenance mode (Successful & Browsable)
-Power on all Virtual Machines (Successful)
This is where the time Skewed and caused headaches. The time for some reason went to 2 days 11hrs in the past on 1 domain controller.
With this DNS lookups failed to work, Cluster services failed, Cluster Aware Updating Failed, RDP to VM's (and Virtual Hosts) by DNS Name failed (Date time error)
There doesn't seem to be anything in the EventLog except for date/time stamp on events being 2 days in the past.
Now this is why i'm not sure if the issue is cause by fail over clustering, or is an issue with the domain controllers.
Any advice regarding this or if anyone has seen this behaviour before any info would be great
Thanks
Rob

Hi Rob,
Does both this two DCs on your cluster VM and there have not others DCs? Microsoft recommends that files for virtualized domain controllers be placed on non-CSV
disks, Non-CSV disks can be brought online without authentication. Because non-CSV disks can be brought online more easily.
For virtual machines that are configured as domain controllers, it is recommended that you disable time synchronization between the host system and guest operating
system acting as a domain controller. This enables your guest domain controller to synchronize time from the domain hierarchy, please confirm your PDC time is always correct.
The related KB:
Running Domain Controllers in Hyper-V
https://technet.microsoft.com/en-us/library/d2cae85b-41ac-497f-8cd1-5fbaa6740ffe(v=ws.10)#deployment_considerations_for_virtualized_domain_controllers
Things to consider when you host Active Directory domain controllers in virtual hosting environments
http://support.microsoft.com/kb/888794?wa=wsignin1.0
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]

How to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster)

I have a scenario with the three nodes with server 2012 standard, each running an instance of SQL Server 2012 enterprise, participate in a
single Windows Server Failover Cluster (WSFC) that spans two data centers.
If the nodes in the primary data center are unavailable due to data center outage. Then how I can able to access node in the WSFC (Windows Server Failover Cluster) in the secondary disaster recovery data center automatically with some script.
I want to write script that can be able to check primary data center by pinging some IP after every 5 or 10 minutes.
If that IP is unable to respond then script can be able to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster)
Can you please guide me for script writing for automatic failover in case of primary datacenter outage?

please post you question on failover clusters in the cluster forum. THey will explain how this works and point you at scipts.
You should also look in the Gallery for cluster management scripts.
¯\_(ツ)_/¯

How to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster) with scrpiting

I have a scenario with the three nodes with server 2012 standard, each running an instance of SQL Server 2012 enterprise, participate in a
single Windows Server Failover Cluster (WSFC) that spans two data centers.
If the nodes in the primary data center are unavailable due to data center outage. Then how I can able to access node in the WSFC (Windows Server Failover Cluster) in the secondary disaster recovery data center automatically with some script.
I want to write script that can be able to check primary data center by pinging some IP after every 5 or 10 minutes.
If that IP is unable to respond then script can be able to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster)
Can you please guide me for script writing for automatic failover in case of primary datacenter outage?

You are trying to implement manually what should be happening automatically in the cluster. If the primary SQL Server becomes unavailable in the data center, it should fail over to the secondary SQL Server automatically. Is that not working?
You also might want to run this configuration by some SQL experts. I am not a SQL expert, but if you have both hosts in the data center in a cluster, there is no need for replication between those two nodes as they would be accessing
the database from some form of shared storage. Then it looks like you are trying to implement Always On to the DR site. I'm not sure you can mix both types of failover in a single configuration.
FYI, it would make more sense to establish a file share witness in your DR site instead of placing a third node in the data center for Node Majority quorum.
. : | : . : | : . tim

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 server 2012 failover cluster error: Cluster resource 'Virtual Machine Configuration ... of type 'Virtual machine configuration in clustered role ... failed.

I have two windows 2012 host server that are clustered using windows failover cluster feature. Each server is hosting four VMs. When migrating from Host2 to Host1, the migration failed with the following error:
Cluster resource 'Virtual Machine Configuration SCPCSQLSRV01' of type 'Virtual Machine Configuration' in clustered role 'SCPCSQLSRV01' failed. The error code was '0x569' ('Logon failure: the user has not been granted the requested logon type at this computer.').
When this happens, the VM that I was migrating can no longer be started even on the original host. The only remedy is to restart the host server.
Any suggestion on resolving this problem?
Thanks
Ikad

Thanks. The article referred to above gives the solution to my issue. There is a group policy that is applied to the OU where the host servers were placed. Doing gpupdate /force temporarily removes the problem. Unfortunately the NT Virtual Machine\Virtual
Machines account is a special account that cannot be added like other accounts and granted the log on as a service right. The thread
http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/d56f2eae-726e-409a-8813-670a406593e8 contains how it can be added which is by creating a group and running the command
Net localgroup VMTest “NT Virtual Machine\Virtual Machines” /add
to add it to a local group VMTest. VMTest is then assigned the right to log on as a service.
Ikad

Windows Server 2012 Failover Cluster (Hyper-V) Event Id 1196

Hi All,
I just installed Failover Cluster for Hyper-V on windows server 2012 with 2 nodes. I got following error event id 1196.
reCreated / deleted Cluster Host A record on DNS and nothing happened.
Any suggestion?
There is similar topic but it couldnt help
http://social.technet.microsoft.com/Forums/en-US/winserverClustering/thread/2ad0afaf-8d86-4f16-b748-49bf9ac447a3/
Regards

Hi,
You may refer to this article to troubleshoot this issue;
Event ID 1196 — Network Name Resource Availability
http://technet.microsoft.com/en-us/library/dd354022(v=WS.10).aspx
Check the following:
Check that on the DNS server, the record for the Network Name resource still exists. If the record was accidentally deleted, or was scavenged by the DNS server, create it again, or arrange to have a network administrator create it.
Ensure that a valid, accessible DNS server has been specified for the indicated network adapter or adapters in the cluster.
Check the system event log for Netlogon or DNS events that occurred near the time of the failover cluster event. Troubleshooting these events might solve the problem that prevented the clustered Network Name resource from registering the DNS name.
For more information please refer to following MS articles:
DNS Registration with the Network Name Resource
http://blogs.msdn.com/b/clustering/archive/2009/07/17/9836756.aspx
Lawrence
TechNet Community Support

Packets sent out the wrong Interface on Hyper-V 2012 Failover Cluster

Here is some background information:
2 Dell PowerEdge servers running Windows Server 2012 w/ Hyper-V in a Failover Cluster environment. Each has:
1 NIC for Live Migration 192.168.80.x/24 (connected to a private switch)
1 NIC for Cluster Communication 192.168.90.x/24 (connected to a private switch)
1 NIC for iscsi 192.168.100.x/24 (connected to a private switch)
1 NIC for host management with a routable public IP (*connected to corp network) w/ gateway on this interface
1 NIC for Virtual Machine traffic (*connected to corp network)
All NICs are up, we can ping the IPs between servers on the private network and on the public facing networks. All functions of hyper-v are working and the failover cluster reports all interfaces are up and we receive no errors. Live migration
works fine. In the live migration settings i have restricted the use of the 2 NICs (live migration or cluster comm).
My problem is that our networking/security group sees on occasion (about every 10 minutes with a few other packets thrown in at different times) syn packets that are destined for the 192.168.80.3 interface goes out of the public interface and is dropped
at our border router. These should be heading out of the 192.168.80.x or 192.168.90.x interfaces without ever hitting our corporate network. Anyone have an idea of why this might be happening? Traffic is on TCP 445.
Appreciate the help.
Nate

Hi,
Please check live migration and Cluster Communication network settings in cluster:
In the Failover Cluster Manager snap-in, if the cluster that you want to configure is not displayed, in the console tree, right-click Failover Cluster Manager, click Manage a Cluster, and then select or specify the cluster that you want.
If the console tree is collapsed, expand the tree under the cluster that you want to configure.
Expand Networks.
Right-click the network that you want to modify settings for, and then click Properties.
There are two options:
Allow cluster network communication on this network-- Allow clients to connect through this network
Do not allow cluster network communication on this network
If the network is used only for cluster node communication, clear “Allow clients to connect through this network” option.
Check that and give us feedback for further troubleshooting, for more information please refer to following MS articles:
Modify Network Settings for a Failover Cluster
http://technet.microsoft.com/en-us/library/cc725775.aspx
Lawrence
TechNet Community Support

SQL Server 2012 Failover Cluster Setup

I have to set up a Lab Test environment for SQL Server 2012 with failover clustering. What are the most cost effective specifications for H\W & S\W. AFAIK Apart of Enterprise edition, Standard edition can support failover clustering for upto
2 nodes with one node in passive mode. Somewhere (Here) I got that it is possible to configure SQL Server failover clustering On SQL
Server 2012 Developer edition. Also Is it possible to use Windows 7 Platform with SQL Server 2012 Developer Edition for configuring Always on Failover Clustering. Although I have researched alot, but puzzled. Seeking for experts advise. Thanks in advance.
Pranshul Gupta

Yes you can configure and install in windows 7.. but make sure you have made all the proper updates as per the microsoft suggestion..
Software and hardware requirments for sql 2012
http://msdn.microsoft.com/en-us/library/ms143506%28SQL.110%29.aspx
http://www.yourdba.com/?p=123
http://resources.arcgis.com/en/help/system-requirements/10.2/index.html#//015100000070000000
Developer Edition..
SQL Server 2012 Developer Edition will continue to be part of the SQL Server 2012 family. The Developer edition provides the same feature set as the Enterprise edition. However, it's licensed per developer and can't be used for production work.
Clustering FAQ's
http://www.brentozar.com/archive/2012/02/introduction-sql-server-clusters/
SQL Server licensing :
http://www.microsoft.com/sqlserver/en/us/future-editions/sql2012-licensing.aspx
http://www.microsoft.com/sqlserver/en/us/get-sql-server/how-to-buy.aspx
Overview and support :
http://msdn.microsoft.com/en-us/library/cc645993.aspx
FCI Failover Cluster Instances (SQL Server)
http://technet.microsoft.com/en-us/library/ms189134.aspx
AlwaysOn Availability Groups (SQL Server) -- AG's
http://technet.microsoft.com/en-us/library/hh510230.aspx
Raju Rasagounder Sr MSSQL DBA

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

FTP in Windows 2012 Failover Cluster

Similar Messages

Maybe you are looking for