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

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

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

Posted By:      Posted Date: May 22, 2011    Points: 0   Category :

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?

View Complete Post

More Related Resource Links

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

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 ?



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.

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

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

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?

Error Changing Default Backup and Log locations on 2 Node SQL 2008 Failover Cluster


My setup is a SAN providing iSCSI targets for a 2 node SQL 2008 Failover cluster on Windows Server 2008.  With the SAN volumes created, MPIO and iSCSI targets defined on each node, I installed the SQL Server cluster with a single iSCSI target, and therefore assigned database files, log files and backup files to be on that single volume.

I have since added a separate volume for both log files and backup files.  All 3 volumes are online in the SQL Resource Group of the cluster and active on the SQL Server active node of the cluster, and all the volumes are accessible from Windows Explorer on both cluster nodes.

Through SQL Mgmt Studio, I changed the default location of the log files, and I changed the default backup location in the registry for each node.

When I try to create a new database, I get an error saying I do not have permission to access the log file volume.  When I try to restore a database, I get the same error when SQL Mgmt Studio tries to access and display the specified backup volume. The text of the error in each case is:

"Cannot access the specified path or file on the server.  Verify that you have the necessary security privileges and that the path or file exists.

If you know that the services account can access a specified file, type in the full path for the file in the File Name con

Sql failover cluster node 1 install error


After the install I get this error

Cluster resource "Sql server (MSSQLSERVER2) could not be brough online.
The resource failed to come online due to the failure of one or more provider resources. (Exception from HRESULT: 0x80071736)

Un-Cluster SQL Server Node


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



Cannot start SQL Server Agent service on Cluster , 2008 R2



I'm testing a two node cluster installation on windows 2008 r2 and sql server 2008 r2 both enterprise before a production deployment and my only issue so far is that the SQl Server Agent service cannot be started.

The failover works fine, the cluster and SQL services changes nodes without any problem but on both nodes i cannot start that service.

I'm using a domain user for the service, member of the local admin and sysadmin on the SQL server itself.

The error i get when i click on start from SQL management console is:

Unable to start service SQLAGENT$SQLTEST on server SERVERNAME. (mscorlib)

Program Location:

Server stack trace: 
 at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.Service.Start()
 at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args,
 Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md,
 Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink
replySink) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.R

adding a node to existing SQL Server 2000 cluster


We have a SQL 2000 cluster pair, say node A and node B. The node B has been corrupted and now the SQL instance is running only on node A. The node B has been rebuilt from scratch and OS reinstalled.

Now, we need to add the node B to node A and they should have a SQL cluster pair. Any one can provide any steps how to add this newly built node to an existing SQL 2000 cluster.

SQL Server does not start when moved to a different node

Sql 2008 R2 on Windows 2008 R2 cluster. When I move instance from node 1 to node 2 everything is fine: all resources come online as they should. When I move the instance from node 2 to node 1, all resources except sql server and agent come online. If I delete errorlog and start the server, sql server and agent startup without problems. Also, I can offline the server on node 2, move it to node 1, and try and start it but it fails unless I delete the errorlog first. I checked startup parameters and servers are identical. I also have a second instance on the same cluster and it moves back and forth between nodes without incident.

multi-site failover cluster, is node & file share majority quorum really correct in this instance -



The HA design we propose in a nutshell:

Primary site A

Node 1: 1 x physical host for a SQL Failover cluster instance for application A

Node 2: 1 x physical host for a SQL Failover cluster instance for application B

Node 3: 1 x physical host for two SQL Failover cluster instances, one for a test env for application A, and another for a test env for application B

Secondary site B

Node 4: 1 x physical host for a SQL Failover cluster instance that acts as a 3+1 failover node that will pic up the failure of either or all of the 3 nodes in Primary site A.

Now I am a complete novice, but my understanding of quorums are that their purpose is to establish when the cluster must stop running due to things like network failures etc. There really is not much out there in terms of a laymans description for quorums :(

The basic requirement for a multi-site failover cluster with an even number of nodes is to use the node & file share majority configuration, and that is what I have here. 4 x nodes (3 at site A and 1 at site B), and a seperate file share for the witness file (which makes the odd number for a majority).

So my understanding is that:

If node 1 fails, it will failover to node 4

If node 1 and 2 fail, they will both failover to node 4

If node 1, 2 and 3 fail, they will all fail

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.

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

SQL Server 2008 Agent Fails to start in a Win 2008 Cluster

When I try to bring SQLAGENT Online, I get the following errors: EventID:53 [sqagtres] StartResourceService: Failed to start SQLSERVERAGENT service.  CurrentState: 1 [sqagtres] OnlineThread: ResUtilsStartResourceService failed (status 435) [sqagtres] OnlineThread: Error 435 bringing resource online.   I just did a fresh SQL Cluster install as well.  When I installed the cluster, the service account was good to go.  I cant figure out what is going on.  SQL Server Engine starts fine.  Any ideas?
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