.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

SQL server 2008R2 install on a server 2008 R2 failover cluster. Other resources won't failover to o

Posted By:      Posted Date: September 16, 2010    Points: 0   Category :Sql Server
As the subject says, I've built a fresh install w2k8r2 and sql2k8r2 failover cluster. Sql works fine on the primary node, but when I test a failover it breaks. Specifically, if I were to stop the node1 cluster service (causing the cluster to switch to node2), windows changes the cluster DNS appropriatly and moves the shared storage just fine, but sql server doesn't failover.  Server Name, Disk Drives and Other Resources all go offline. I've verified that the advanced policies of the server name, IP, cluster drives all have both nodes checked as possible owners However, Other resources only lists node1 as a possible owner and there appears to be no way to add node2.  Under the Other resources, SQL Server and SQL Server Agent are listed. I'm sorta stumped, I've been combing the forums and have found similar issues, but nothing seems to explain why the two resources won't failover.

View Complete Post

More Related Resource Links

SQL server 2008 failover cluster install

Hello all, Looking for the definitive answer with supporting documentation (link). Does a SQL server 2008 cluster have to be installed as or run as a domain service account or can local accounts be used?  I looked for a document that stated yes or no and could not find one. If anyone can provide info it would be much appreciated. Have all ready looked at these 2 links of interest. http://msdn.microsoft.com/en-us/library/ms143504.aspx#Service_SID http://technet.microsoft.com/en-us/library/cc731002(WS.10).aspx Thanks in advance,  

Failover Cluster Install on Server 2008 R2 (RC)

Has anyone successfully installed a SQL Server 2008 Failover Cluster on Server 2008 R2 (RC)? I'm getting stuck at the Instance Configuration screen, i get an error when trying to detect the SQL Server Network Name, here is the error:

The given network name is unusable because there was a failure trying to determine if the network name is valid for use by the clustered SQL instance due to the following error: 'The network address is invalid.'

I've setup a 2008 SQL Failover Cluster in Server 2008 SP1 without a problem.

SQL Server 2008 A/P Cluster Does not Failover



I have a SQL Server 2008 Enterprise Edition A/P cluster Server on Windows 2008. Recently One of the Clustered Disks Went OFFLINE. The SQL Resource which has Dependency on the clustered Disk also went offline. Shouldnt a Failover of the resources be happening to the second node, if there is a failure in the first node? Are there any settings which need to altered?




Hi, I have successfully installed the slip stream SQL SERVER 2008 Enterprise  sp1  on the two node fail over cluster.Now i need to implement the 2 node failover cluster installation again with the standard  edition of SQL SERVER 2008 sp1.

My question is do i  need to go for a slipstream installation with  standard edition also?

single node SQL server 2008 R2 failover cluster is down

I install a single node SQL server 2008 R2 failover cluster (server 1) and add a node (server 2) on other server . Now , the first sql server (server 1) is down , server 2 still up so i have 1 server running When i install a new single node sql server cluster on a new server two error occur (failed) : - Microsoft Cluster service (MSCS) cluster verification errors. -Cluster shared disk available check Or can i change the server 2 to the single node sql server clutser to add new node ?

named instance sql server 2008 install on cluster

I have a production two-node cluster with sql server 2008 sp1 cu7 running over windows server 2008 sp2. If I were to install a new named instance on this live environment, would it impair the default sql server instance functionality? I'm not referring to processor/io while the install is in progress. My question specifically is would the install process by its nature bring down the default instance. I'm pretty sure it won't, but don't see any documentation that would confirm this. thanks.

In windows server 2008 standard edition feature Failover clustering is not looking

In windows server 2008 standard edition feature Failover clustering is not looking.Yet microsoft is telling that we give 2 node cluster support on 2008 server standard edition.Therefore I have suggested the company to buy it and now I am fixed due to this.  Please Help  "SQLSERVER DBA" "INDIA"

Issues with Kerberos and SQL Server failover-cluster

I have a dual-instance SQL 2008 SP1 2-node Failover-cluster running on Server 2008 x64 SP2. SPNs have been manually created in AD for the service account running SQL Server (on both nodes).When the cluster nodes first boot up and the virtual groups come online, everything works flawlessly. I have linked server connections set up between the two instances of SQL server, with one instance running on each node. I can successfully make linked server connections from one instance to another from a third client PC, indicating Kerberos is working successfully, which is great!Problem is, this all stops working as soon as one of the SQL cluster groups fails over (or is taken offline, and moved to the other node). As soon as this happens, all authentications seems to fall back to NTLM. Of course, running both instances on the same physical node will work since Kerberos is not required for this. But as soon as an instance moves to another node - kerberos seems to be permenantly broken for that instance, even if moved back to its original node, until both nodes are rebooted again.One thing to note - the service account running SQL server is not a domain admin. This of course prevents SQL server from auto-registering the SPN upon startup and generates the following in the SQL log: "The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL

The SQL Server failover cluster instance name 'Server02' already exists as a clustered resource. S

Hello, I have a node of 2 servers of Win 2008 R2 Enterprise and trying to install a 2nd instance in a SQL 2008 R2 Cluster. I had SQL_INSTANCE2 previously installed that I removed from the two nodes. Now when I attempt to install it again from scratch, in setup GUI where I specify the SQL Server Network Name and enter the previously entered name "Server02", I get a failure in the setup with the following error message: "The SQL Server failover cluster instance name 'Server02' already exists as a clustered resource. Specify a different failover cluster instance name." How do I fix this problem, I don't want to enter a new name like "Server03" in order to proceed with the setup, because when I do enter "Server03" the setup does continue without an error message. So what am I missing? Do I have to ask the DNS administrator to see if there's an A record for "Server03" and have him delete it so that the setup works? Or the fix is by doing something else? I would appreciate any help. Thank you  

SQL Server 2005 Cluster failover issue

Hi All, I'm fequently experience Cluster failover issue. The cluster tries to failover and it fails back. Because of this the SQL server is getting restarted and this is a bugging issue during business hours. The following are the System event logs, Cluster resource 'SQL Server' in Resource Group 'Production' failed. The SQL Server Agent (MSSQLSERVER) service was successfully sent a stop control. The SQL Server Agent (MSSQLSERVER) service entered the stopped state. The SQL Server (MSSQLSERVER) service was successfully sent a stop control. The SQL Server (MSSQLSERVER) service entered the stopped state. The SQL Server (MSSQLSERVER) service was successfully sent a start control. The SQL Server (MSSQLSERVER) service entered the running state. The Cluster Service brought the Resource Group "Production" online.    The following are the application event logs, The client was unable to reuse a session with SPID 131, which had been reset for connection pooling. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message. [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed [sqsrvres] printODBCError: sqlstate = HYT00; native error = 0; message = [Microsoft][SQL Native Client]Query timeout expired [sqsrvres] OnlineThread: QP is not online. The client was unable

SQL server 2008 cluster install error - The resource failed to come online due to the failure of o


Hi ,

I ran into the following error when trying to install sql server 2008 cluster (node 1) on windows 2008

The resource failed to come online due to the failure of one or more provider resources. (Exception from HRESULT: 0x80071736)

Any insight on this issue is greatly appreciated





Domain groups in Cluster Security policy during install of SQL Server 2008

I am trying to install SQL Server 2008 on Windows server 2003 and have a question about the stage of 'Cluster Security Policy'.

We need to select 2 groups here, one for SQL server database domain group and the other for SQL server agent domain admin group.

My question is, is it different from service accounts that we used to specify in previous versions? I remember the wizard asking for service account that the sql services need to run under. Is this domain group part a replacement for those individual service accounts? If yes, do I need to have the service account added to a separate group and select that group in this part of 'Cluster security policy'?




SQL Server Service does not start on SQL Failover Cluster Node B even though i turn off Node A (acti


We ahev setup a SQL Server (64-bit) Failover Environment which consist of a Node A (active) and Node B (passif).

The setup was completed successfully and was working fine since june 2008.

Our system administrators have reported that, after they made some changes during a maintenance week-end, the SQL Server Services don't start anymore on the node B (even though they turn off the active node A and make Node B as active). Our attempts to manually start those services arealways failing.

Can someone help?

How can Install Office 2007 on Windows server 2008 R2 64 bit machine in WSS 3.0

I have  64 bit machine  and Windows server 2008 R2 has installed. i have successfully install WSS 3.0  , but  when i tried to install  office 2007 ,  one  error  has  come  "OS is not compatible "  i thought  it was asking  for 64 bit office  2007   and i go through the  google and R&d find no 64 bit office is available ,  i have used   excel .dll in my custom code  so my problem is that   how can  install office 2007  on 64 bot OS 2008 r2  machine .  if anyone can help   me  , please let me know . thanks in advance

Cannot install SQL Server 2008 R2

I download the SQL Server 2008 R2  and cannot complete set up because Windows Power shell failed the details stated that it has not been installed. Setup cannot not be completed.  How do I install Windows Power shell? I choose 64 bit setup because I have a  Vista Home Premium   Service Pack 2 64 -bit Operating System. Should I try to use 32-bit installuation set up?

SQL Server 2008 R2 fails after Windows XP Pro SP3 install

We recently encountered an issue with SQL Server 2008 R2 failing to run after the upgrade from Windows XP Pro SP2 to SP3. This was tested and reproduced (with varying results) on more than one computer. Steps to reproduce this. On a Windows XP Pro machine with Service Pack 2 installed, install SQL Server 2008 R2. Next upgrade Windows to Service Pack 3. Now upon opening SSMS or trying to start the SQL server service you receive the following message: "This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem". In some instances reinstalling/repairing SQL Server 2008 R2 does fix the issue.  In other cases the installer crashes and you need to use msizap to clean it up before you can reinstall.  In other cases you do not receive any errors at all. After testing in multiple virtual machines it looks like the cleaner the Windows install the more likely you are to run into this issue.  On machines with most or all windows updates (prior to SP3) installed you do not necessarily even get the failure.  On machines with just Windows XP Pro SP2 installed with no additional updates you get the failure every time. Obviously the SQL Server 2008 R2 prerequisites are installed in all cases in order to be able to install SQL server to begin with. Any help with this would be appre
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend