.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 2005 SP3 w/KB970892 installed on Cluster can't add new node.

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

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.



View Complete Post

More Related Resource Links

sql 2005 cluster ssis not installed passive node


I am doing an SQL Server 2005 Cluster install. The install appeared to go
okay. On the active node everything installed fine. However, when we looked
at the other node only the configuration tools got installed. SQL Server
Management Studio did not get installed. Would anyone know what caused this
and how to install the SQL Server 2005 on a cluser correctly? I understand
that that the management tools only get installed on the primary node.
Should I run setup on the secondary node to install the tools?

I also went through the summary log for the install and  noticed that almost
everything that was installed on the active node was  also installed on the
passive node. The products that did not get installed  on the passive node

- Microsoft SQL Server 2005 Integration Services
- Microsoft SQL Server 2005 Notification Services
- Microsoft SQL Server 2005 Reporting Services
- Microsoft SQL Server 2005 Tools

Should not these have been installed on the passive node as well?

"None of the selected features can be installed" error on SQL 2005 Cluster

Hey All, I installed SQL 2005 on a cluster.  Everything on the primary node works fine.  However, as the documentation suggests, the SQL Management Studio (and other tools) are not installed on the standby node by default.  However, when I go to try and install on the 2nd node I get the following error: TITLE: Microsoft SQL Server Setup------------------------------ None of the selected features can be installed or upgraded. Setup cannot proceed since no effective change is being made to the machine. To continue, click Back and then select features to install. To exit SQL Server Setup, click Cancel. For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.06&EvtSrc=setup.rll&EvtID=SQLSetup90&EvtType=28108 ------------------------------The link is referencing something about requiring a complex SA password.   I can verify that the directory structure on node 1 where the management studio and client tools exist does not exist on node 2.   I'm at wits end here, I've tried uninstalling/reinstalling/everything. Anyone have any ideas? thanks!

Security Update for SQL Server 2005 Service Pack 3 (KB970892) could not be installed


Auto updates picked up this update to install but it wouldn't install. I tried doing it manually with no success. Anyone run across this?I have the service pack 2 with updates already. What would cause this?

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


SQL server 2005 cluster - second node - sql service will not start - node is showing down in cluster


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

Maintenance restart procedures for Win2k3 Enterprise SQL 2005 2-node cluster


We are looking to perform normal maintenance on a Win2k3 Enterprise SQL 2005 2-node cluster.

In the past we have shut down the passive node, then restarted the primary server.  Once it's back and we see the cluster resources back online we then boot the passive node.

Are there other procedures that we need to follow or does the graceful restart of the server also shutdown the SQL services and the database correctly?  I'm getting a mixed bag from all research I've seen.  Any help is greatly appreciated.


SQL 2005 Standard to Enterprise Edition upgrade on existing three-node cluster


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

install SQL server 2005 cluster in an exisiting two node SQL 2005 cluster

Hi.. i have an existing SQL Server 2005 instance already running in a two node cluster utilizing all the shared disk resources. I am now to install another SQL Server 2005 cluster in this same 2 node make it as active passive. Can you please let me know what are the pre requistes for it(like SQL Virtual ip, More shared disks.. ) for isntalling a new SQL instance in an existing two node clujster and what is the impact and how to proceed. Is it same way of installing a normal cluster or if differs. Thanks for your help in advance.

Installed Visual Studio 2005 on new laptop - can't open C# web services project solution.

Installed Visual Studio 2005 on new laptop - can't open C# web services project solution - get the 'project not supported by this installation' error. Tried re-installing to no avail. Have run various flavors of devenv as recommended in various posts. Still the same message. I can open the solution fine on my old laptop.    Update: We re-installed service pack 1 for VS and the problem was resolved.

SQLServer 2008 Tools and SQL 2005 Cluster

I recently built a SQL Server 2005 cluster on the o/s Windows Server 2008 R2.  I have been attempting to connect to the cluster from my Windows 7 dekstop with my SQL Server 2008 Tool set.  I have been unable to attach to this cluster since its creation. The firewall is temp off, remote connections in the surface area configuration is set to pipes and tcp/ip and the Browser surface is up and running. I ran Wireshark against the cluster and I could see that there was UDP conversations for ms-sql-m (SQL Port) but that was as far as it would get.  I am using a named instance so not using 1433, but I do see the cluster offering up high RPC ports but the client never responds after the initial UDP response. When I noticed that there was a two way conversation taking place, I went to a seperate machine and fired up SQL Server 2005 Tools and I was easily able to attach to the cluster.  So my question is - Are there any known incompatibilities between SQL Server 2005 cluster services and SQL Server 2008 Tool set?  I can use my 2008 tools to attach to a non-clustered SQL Server 2005 w/o issue.   Error when attempting to connect: A network-related or instance-specific error occured while establishing a connection to sql server.  The server was not found or was not accessible.  Verify that the instance name is correct and the SQL Server is con

SQL Server 2005 - Installation in Cluster Environment - "Service SQL Server Browser (SQLBrowser) fai

Windows Server 2003 R2 Enterprise Edition SP2 32-bit All updates and patches installed Two-node cluster environment configured. Cluster functions perfectly. Trying to install SQL Server 2005 Enterprise Edition (32-bit) as a clustered application. Installation proceeds fine until it begins to install the SQL Server Database Services product. Status window says "Starting Services. Service: SQL Server Browser". Error message is presented: "Service 'SQL Server Browser' (SQLBrowser) failed to start. Verify that you have sufficient privileges to start system services". SQL Server Service Account is in the Administrators group on both local systems, and is a domain account. Account used for the installation is in the Administrators group on both local systems, and is a domain account. Have cancelled out of the install and rebooted both servers numerous times. Exact same error continues to occur. Cluster is active and all resources are owned by node #1 - the node where SQL Server Installation is being run. In the event viewer, I see: Event ID: 10 Description: The SQLBrowser service was unable to establish SQL instance and connectivity discovery". I am also seeing errors like: Source: SQLBrowser. The SQL configuration for SQL is inaccessible or invalid. Source: SQLBrowser. The Configuration of the AdminConnection\TCP protocol in the SQL instance xxxxxx i

Reinstalled SQL 2005 on cluster won't start.

OS: Windows Server 2003 32-bit. Cluster: 2-node Active/Passive We're working on upgrading from SQL 2005 to SQL 2008, and we're using this cluster to test the cluster upgrade/install procedures. So, updated the existing SQL 2005 instance to SQL 2008. This went fine. Added an additional SQL 2008 instance. This went fine. Uninstalled SQL 2008 (both instances) from both nodes. This went fine. Installed SQL 2005 (clustered setup). At the end of the install process, received a message about unable to do (something). However, the install reported successful. In the SQL0001_<computername>_Core(local) are these messages: Running: OpenPipeAction at: 2010/7/24 10:20:31 Complete: OpenPipeAction at: 2010/7/24 10:20:31, returned false Error: Action "OpenPipeAction" failed during execution. and much later: Error: Action "UninstallForRS2000Action" failed during execution.  Error information reported during run: Action: "UninstallForRS2000Action" will be marked as failed due to the following condition: In the SQL0001_<computername>_Core.log: Running: LaunchLocalBootstrapAction at: 2010/7/24 10:11:30 Error: Action "LaunchLocalBootstrapAction" threw an exception during execution.  Error information reported during run: "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe" finished and returned: 0 Aborting que

Sql Server 2005 Cluster on EXS 4.0 VMWARE

Hi, I have this problem, i have sql server on Cluster with two nodes, the nodes are machine vmware, i was exs 3.5 and in december the esx was upgrade to version 4.  Of January the nodes present this problem:The node lost communication with cluster node 'SVRSQLN02' on network 'Servidores'.The node lost communication with cluster node 'SVRSQLN02' on network 'HeartBeat'.What can i do?

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.

Applying windows patches to a SQL 2005 2Node Cluster

Can anyone advise the correct procedure for applying windows patches on a two node active / passive SQL 2005 cluster We have disagreements whether the node being patched is active or it should be passive, would appreciate any comments   Thanks

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
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