.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

Installing an additional SQL Cluster Node

Posted By:      Posted Date: September 29, 2010    Points: 0   Category :Sql Server


We have a 2 node SQL Failover Cluster (2008).

We wish to replace these 2 Servers (Virtual Machines) with 2 new ones.  I was hoping I could 'cheat' and instead of powering off both current Virtual Machines and then having to do the SQL install from scratch on the 2 new Servers. I could do the following instead:

A:  Add the 2 new Virtual Machines as additional Failover Clusters into the current SQL Environment (so we now have a 4 node SQL Cluster)

B:  Power off the 2 OLD Virtual Machines (so the 2 new Virtual Machines make up the new Cluster)

Would this work or would it be looking for certain files, etc that were installed on the Primary Node?

View Complete Post

More Related Resource Links

Installing new SQL Failover Cluster Node



I have a 2 Node SQL Cluster.  Node A is the Primary Box where SQL was first installed and Node B is the Secondary Box where I added it to the Failover Cluster.

I now wish to replace Node A with a new Server (reason being, we have had issues with this and wish to rebuild it from scratch).  My question is...

If I move the SQL Resources onto Node B, can I then rebuild Node A Server and then add it as 'failover cluster node'?  Or will this not work as it will already detect that Node A was part of this Cluster before? And during the initial install did Node A install files that are required for Node B to work?

SQL 2008 64 Bit 2 node cluster

I wanted to get some feedback on how much memory and CPUs I needed for each node in a 2 Node Cluster. The operating System will be Windows 2008 R2 64 bit Enterprise and the SQL version will be SQL 2008 R2 64 Bit. It will have a total of 8 instances of SQL Server. 2 of those instances will be SQL Server Reporting Services ( 1 SQL Native and the other SharePoint enabled). This cluster will have both nodes in a virtual enviroment. Any feedback would be greatly appreciated.

Adding second node to SQL Server cluster fails.

I have successfully created a MSCS cluster and I have the SQL cluster up and running on the first node.   When I put the install cd in the second node and go through the install it fails with the error SQL Server Setup has encountered the following error:  Object reference not set to an instance of an object. I'm assuming I get this error because on the cluster node configuration screen the "cluster network name" box is blank.   It won't let me select a name or type a name. The SQL cluster is up and running on the first node.   I can ping the sql cluster network name from both boxes.   The setup shows the installed node and the node I"m trying to add, so I don't see any problem. I have Windows 2008 R2 on both nodes and I'm installing SQL Server 2008 R2.   Any idea how I can get past this error?    Thank you.

Adding thrid Node to SS2K8 cluster fails on adding fileshare

I am attempting to add a third node to a two node cluster. I am using the SS2K8 SP1 slipstream I used to successfully install the other two nodes. The new node of the cluster is:  Hardware: Dell R610 blade  OS: Windows Server 2008 R2 Enterprise 64 bit SQL: SQL Server 2008 SP1 64 bit Enterprise. The two node system has been running for months without problems. How do I fix a failure to add a file share for filestream because the value of group was null (Bold Italics below)? I have not found anything on the web that addresses this problem. Brad The bootstrap summary file woes content(s): Detailed results:   Feature:                       Database Engine Services   Status:                        Failed: see logs for details   MSI status:                    Passed   Configuration status:          Failed: see details below   Configuration error code:      0x11428655   Configuration error description: Value cannot be null.  Parameter name: group &nbs

SQL node remove failed on Cluster :The state of your SQL Server installation was not changed after t

HI guys , Have you faced this .I am not able to remove the SQL Server 2008 ENT node .The error is : Overall summary:   Final result:                  Failed: see details below   Exit code (Decimal):           -2068643838   Exit facility code:            1203   Exit error code:               2   Exit message:                  The state of your SQL Server installation was not changed after the setup execution. Please review the summary.txt logs for further details.   Start time:                    2010-09-12 09:40:40   End time:                      2010-09-12 09:48:26   Requested action:              RemoveNode The details.txt shows the same error in a different way : Running Action: CloseUI 2010-09-12 09:44:44 Slp: Stop action skipped in UI

Issues installing SQL 2008 on Win 2008 R2 Cluster

Hello All, I'm having issues installing SQL Server 2008 on a Win 2008 R2 Cluster. The "SQL Server failover cluster install" went fine, now the "Add a node to a SQL Server failover cluster" that is giving me problems. I'm running the setup using slipstream, I was told it would not work without using slipstream. I'm running the command "Setup.exe /PCUSource=D:\sp" inside of the folder where I have the setup file for my Enterprise install of SQL Server 2008. For some reason, the whole install fails, reporting issues with the "Install_sql_engine_core_inst_Cpu64_Action" part of the process. I removed any numbers or characters from the folders my media intallation is located, as this KB below suggests: http://support.microsoft.com/kb/955666 Below is how part of my log file looks like. Let me know if you have any suggestions.   <LOG STARTS> 2010-08-09 14:24:06 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100809_142013\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_ 2010-08-09 14:24:06 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100809_142013\Registry_SOFTWARE_Microsoft_Windows_CurrentVer

network configuration and best practice for 2 node cluster

For our 2 node cluster i have set the following: Node 1 nic 1 :,, Node 1 nic 2:, node 2 nic 1:,, node 2 nic 2:, Is this a configuration of good practice?? how does the cluster know which subnet to use as the private and which one to use as the public? The cluster IP should belong to the public subnet, for ex: But what about the MSDTC?? should it have an Ip of the public subnet or private subnet? Thanks.

SQL Management Studio not on Passive Node SQL 2008 Cluster

Hello, I would like to be able to use SQL Management Studio on the passive node in our cluster if there's a failover and Passive Node becomes Active Node.  It seems like the Add Node install didn't load SQL Management Studio on our passive node. Any help is appreciated. Thanks,  Morrisos

Error Adding 2nd Cluster Node - Account Name Box Greyed Out


I am in the process of setting up a 2008 R2 SQL cluster using SQL 2008 R2.  I have the first node up and running, and all is well.  Going through the process to the add the 2nd node, I am stuck.

At the part where you configure the SQL service accounts, the SQL server agent account is greyed out.  Hovering your mouse over it shows that field as "Read-Only"  The box for the password you can type in, so I went ahead and put in the password I used for the account on the first node.  (it's a domain account with the corect privledges).  On the database engine section it lets me select my domain account and then I put in the password.  Clicking next gives me an error stating that the "Credentials you provided for the SQL Server Agent service are invalid."  

I know the password is correct, but without the accout name box being greyed out, I am not sure it is pointing to the right account.  Other people too are having this issue:  http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/aae80395-7d29-4a07-a1b7-29959e78d382   What is marked as a solution on that thread really isn't.  Follow up posts show other people at the same spot I am.

Installing Integration services as standalone on a existing cluster


Hi All,

  I have SQL Server 2005 std edition installed on a windows 2003 clustered server. As integration services does not support i was asked to install it as a standalone on both nodes. When I had started the setup it showing on both the nodes. How do i install it only one node at a time and not on the cluster. Do i need to have separate instance of sql server too.



Chandra Mohan



SQL 2005 SP3 w/KB970892 installed on Cluster can't add new node.


We have SQL 2005 Enterprise Cluster, the cluster is running SP3 with the KB970892 hotfix installed. Using Cluster administrator "add new" node, then via Add\Remove programms add SQL node, all is good to this point. However the new node has the RTM EXE and if I try to run the SP3 from the active node w/KB I can't select the MSSQLServer option because "The product instance MSSQLServer been patched with more recent updates", if I try to fail the server over to the new node and install the SP3 I get "failed, no passive nodes updated" and the RTM node also does not update.



Cluster Node Change


Hello Friends/Colleagues,


I have 2 nodes active/active with 3 virtual instances.

2 instances on node 1 and 3d instance on node 2.


Sometimes they automatically change from node 1 to node 2.

Is there any way that I get some notification regarding the instance that have changed from one node to another?


I found following may be probable solution:

EXEC master..xp_cmdshell 'cluster resource "SQL Server (Instance Name)"'

Result: Instance Name, Node Name

Put results into table..........Again run the command.....compare.......too much stuff.....

If someone knows the easy path to this.......


How could I get the information that has been changed?


Your help would be really great!



Adding a second node to a SQL 2005 Windows 2003 cluster - NewbieQ



I've been asked to replace the hardware for one of our SQL 2005 cluster nodes because of it's age etc etc..  I have evicted the node from the cluster and added in the new one but now have to add the SQL component to it.  I'm not familiar with this bit!  I have found this guide on Technet


Which seems to be exactly what I need but I have a few questions;

1.  Do I install SQL 2005 on the new node and then perform the steps in the guide above or will it be installed as part of the process following the steps above?

2. Will the current active node go offline or anything like that during the installation? 

3. Do I run the setup from the new node or the current active node?

Sorry for all the questions but I'm new the clustering side of things and dont want to mess this bit up

Thanks in advance


Add a new passive node to set up Active/Active/Passive cluster



We have a SQL cluster server running with SQL 2005 Enterprise Edition SP2 on Windows 2003 Enterprise Edition.

Currently the cluster has 2 nodes with Active/Active. Now I need to add a new node as a Passive node. So after I have done it, the cluster will be a Active/Active/Passive cluster.


Because the cluster is a production server, I need to know exactly how I add a new node onto the current cluster without breaking anything. Also this is my first time to install a passive node, so it is difficult for me to understand how to install and configure it.


I have already added the physical node onto the cluster group so I can see the new node 'paused' from the Cluster Administrator.  Now I need to install the SQL but I am too nervous to run the installation p

Intermittent unavailability of an instance in a failover cluster while a standby node is offline.


Hi everyone.

I've got a small failover cluster that I run for the websites my company has. During a RAM upgrade of the standby server, our websites started to show errors about not being able to access the database server. I verified that the instance was indeed up and the server accessable via remote desktop.
I also tried a SQL connection to it and it worked, but that might have been after it became available again.

This happened on and off until we were able to roll back the hardware changes that were in progress on the standby server and we were able to bring it back up.

There was nothing of interest in the SQL Server log, but there is a continous log for the whole duration of the problem, so there was no restart of the SQL Server service. The event viewer is of more interest, since it shows events relating to the heartbeat network card, but I don't know how that would affect the availability of the server, since the standby node is offline. I'd appreciate any help you can provide, it's not very redundant if it also depends on the standby server being up. :)

Here are the event logs from the time of the problem:

Level Date and Time Source Event ID Task Category
Information 4/23/2010 10:55:56 AM Microsoft-Wind

Two node SQL 2008 cluster on two Windows 2008 servers


Hi, I want to know if it is possible to setup a two node SQL 2008 Server cluster with a single named instance on two Windows Server 2008 boxes (any version). The  documentation suggests that setting up any type of SQL cluster needs to be on an existing Windows cluster. Would rather not setup a windows cluster if possible.


Any help would be appreciated.

Error Adding Node to SQL 2008 R2 Cluster


Windows Server 2008 R2 64bit. SQL 2008 R2 64bit.

The Windows Failover cluster is installed with 2 nodes. SQL Cluster was installed successfully on node 1. Ran SQL setup to add a SQL node 2. Made it to the service accounts screen. The SQL Server Agent service account name box is grayed out and nothing can be entered. If I hit next I get the following error. I can't get past this. I looked for any cumulitive updates for R2, but there aren't any. Does anyone have a work around? If not I will have to scrap the install and go back to the non R2 version of SQL.

[Error Message]
The credentials you provided for the SQL Server Agent service are invalid. To continue, provide a valid account and password for the SQL Server Agent service.

Microsoft.SqlServer.Configuration.Agent.InputValidationException: The credentials you provided for the SQL Server Agent service are invalid. To continue, provide a valid account and password for the SQL Server Agent service.


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