adding a node to existing SQL Server 2000 cluster

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.

Hi all I have   6 cluster environments and 10 standalone servers and mix  of  32 bit  64 bit. As I know In place Upgrade not possible SQL2k 32 bit to SQL2008 64 bit. What I want to know is……… 1. If I purchase SQL Server 2008 Ent edition that will have both 64 bit and 32 bit edition or I have purchase separately ? 2. How to do side by side upgrade in Cluster environment I mean I can’t ask my company to provide other cluster to do side by side upgrade. If I do installation in same cluster machines, I can’t provide same Instance name for SQL Server 2008 Instance.hance it is very difficulty for application connectivity Please some body provides me best approach to drive in Upgrade from SQL2k to SQL2008. Thanks in Advance      SNIVAS

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

Dear All, One of my customer is running a active/active SQL 2000 cluster in Windows 2003 and the service account for one of the instance is LocalSystem account. I am not sure how they changed the service account to localsystem because SQL Server doesn't allow LocalSystem account as your service account when you install it on a cluster and it doesn't allow to change the service account to LocalSystem account in Enterprise Manager when running in a cluster. I searched for documentation to findout whether Microsoft supports running SQL Server using LocalSystem account in a cluster but I am unable to find a documentation. Please help me to identify the documentation regarding the support or share your experience Regards BalajiRegards,Balaji, Please mark as answer if you think this answers your questions

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

I want to add a complete node to an existing XML document.So:1. get the XML document from the session2. create a new node3. pass the node and the session to a function, that adds the node on the location of the xpath4. return the new session, updated with the node in the specified locationBelow my code, which DOESNT work.I've had some other advices, but nothing seems to work. What am i doing wrong?!?!Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load    Dim doc As XmlDocument = New XmlDocument()    Dim xmldoc As XmlDocument = Session("XML") 'get XMLdocument from session    Dim locationNode As XmlNode = doc.CreateElement("location")    Dim locationAttribute As XmlAttribute = doc.CreateAttribute("id")    locationAttribute.Value = "3"    locationNode.Attributes.Append(locationAttribute)    Dim titleNode As XmlNode = doc.CreateElement("title")    titleNode.AppendChild(doc.CreateTextNode("Empire State Building"))    locationNode.AppendChild(titleNode)    doc.AppendChild(locationNode)    Dim newNode As XmlNode = doc.ImportNode(locationNode, True)    AddOrUpdateNodeInSession(Session, "//root/dat

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.

Hi,

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

http://msdn.microsoft.com/en-us/library/ms191545(v=SQL.90).aspx

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

Brian

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.

[Details]
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.
================================================================================

 

Hey all,

Current configuration:

2-node sql 2005 cluster

windows 2003 enterprise R2 w/ sp2 x64

sql 2005 enterprise x64 SP3

 

In the process of adding a third node into the existing 2-node cluster, we received the

"A domain group is missing for one or more services.  To install SQL 2005 as a failover cluster, domain groups must be specified for all the clustered services bing installed. To proceed, enter the missiong domain group information." 

The existing cluster functions properly and has been running w/o problems for a long while now.  An AD Global Group was created to support the cluster back when the cluster was initially created.

 

I found different suggestions from people online about this issue, any where from adding registry keys to take trailing blank space from sql resource group name, but none works. 

 

Any ideas?

 

Thank you in advance for any assistance.

--dw

 

I have an existing sp 2010 enterprise server hosting websites and central administration.  I have a seperate sql 2008 r2 server holding the databases.  My goal is to setup another sp 2010 enterprise server to provide redundancy for the websites and central admin.  I believe I am able to accomplish this by adding another web front end to the farm.  On the second server, I install sp 2010, run the config wizard and connect to the config database located on the sql server, however, I am interrupted at step 3 when I am notified of the following:

Failed to connect to the configuration database.
An exception of type System.InvalidOperationException was thrown.  Additional exception information: There was an error encrypting or decrypting credentials. Either a credential update is currently being performed, or you must update the farm account credentials on this server before you can perform this task.
System.InvalidOperationException: There was an error encrypting or decrypting credentials. Either a credential update is currently being performed, or you must update the farm account credentials on this server before you can perform this task.
   at Microsoft.SharePoint.Administration.SPEncryptedString.CheckCredentialLock()
   at Microsoft.SharePoint.Administration.SPManagedAccount.Deploy(SPApplicat

Hi all

Please I have SQL Server 2000 running on Windows 2003 SP2 (A/P) Cluster,Now we are adding new SQL Server 2008R2 Instance to Cluster.

I want know "Database Engine Domain Group","SQL Server Agent Domain Group" section,can I select excisting SQL Server 2000 Engine Domain group or I required to Configure  some thing else.

and

How to find out "Database Engine Domain Group","SQL Server Agent Domain Group" of  excisting SQL Server 2000.

 

Thanks in Adavnce

 

 

---

SNIVAS

I am tryng to get the second node in a two node cluster to start sql services and come up in the cluster.  The second node was configured and running in a cluster when at some point, the sql service and/or cluster service went down.  Now the node will not start...as in SQL service fails and the system log error is:

"The disk associated with cluster disk resource 'Disk Q:' could not be found. The expected signature of the disk was BF17D33C. If the disk was removed from the server cluster, the resource should be deleted. If the disk was replaced, the resource must be deleted and created again in order to bring the disk online. If the disk has not been removed or replaced, it may be inaccessible at this time because it is reserved by another server cluster node."

and the Application log shows:

Error 2(The system cannot find the file specified.) occurred while opening file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf' to obtain configuration information at startup. An invalid startup option might have caused the error. Verify your startup options, and correct or remove them if necessary.

I had to edit the startup parameters on the second node because it appears it cannot "see" the original path, which was a network driv

Hi All

Please let us know if anyone can provide the complete steps to un-clustered the SQL Server node to make stand alone.

Thanks in Advance

Ashish

 

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 ?

Current set-up: three node cluster running Windows Server 2003 Enterprise Edition SP2 with two instances of SQL Server 2005 Standard Edition SP2.

 

Virtual node 1: Standard Edition, default instance, Database Engine only

Virtual node 2: Standard Edition, named instance, Database Engine, Analysis Services and Integration Services

 

Physical node A: Prefered node for virtual node 1

Physical node B: Failover node for both virtual node 1 and 2 (thus having two installations of Standard Edition)

Physical node C: Prefered node for virtual node 2

 

We started off with this set-up because there was no need for Enterprise features, and SQL 2005 supports failover clustering with two nodes in Standard Edition. Saved a bundle of cash, so everybody's happy. Now we need to run a solution on virtual node 2 that requires Enterprise features in Analysis and Integration Services, so an edition upgrade is required on virtual node 2. I have done some research and found several edition upgrade examples, but none that match the above scenario. We are running production on these machines, so I can't risk experimenting with command line options, I have to be right the first time.

 

Is it possible to mix two editions of SQL Server 2005 in one cluster? Can I upgrade virtual node 2 to Enterprise but leave virtual node 1 at

Inside a virtual environment running Windows 2008r2 Ent SP1 and SQL 2008r2 RTM.

Inintial cluster build has gone smoothly for a 2 node cluster using iSCSI. Added up a third node to this cluster manually changed quorum model and MsDTC resource was bouncing all well on the three nodes. Sweat started when the third node failed to add into SQL Failover cluster with the given message "Failed to retrieve data for this request" right after clicking add a node.

Sites talk about adding CuP6 and to lower the security but to note all this worked for first & when adding second node, for the moment this was resolved for me after I restarted all the nodes; going from Node3 to 1. For a moment RemoteRegistry service failed to start on node2 and it wount work even on restarts so moved every thing to node1 now the RPC was up on Node2 and I can go further on adding node3 to SQL cluster but as I'm typing it failed again.

As I check the logs they point about failures to write to registry and at time Network Path not found, User credentials used are all same and pings are going well for the entrire set of IP's I have.

Any insights on this are highly appreciated?

---

yup