SQL Server 2005 cluster resources fail after a side by side installation of SQL Server 2008 on a Windows Server 2008

Article ID: 2000403 - View products that this article applies to.
Expand all | Collapse all

Symptoms

Consider the following two scenarios:

Scenario 1:

  • You install SQL Server 2005 failover cluster on a Windows Server 2008 or Windows Server 2008 R2 failover cluster using the default configuration.
  • On the same system you install a new instance of SQL Server 2008 failover cluster.

Scenario 2: 

  • You install two or more instances of SQL Server 2005 failover cluster on a Windows Server 2008 or Windows Server 2008 R2 failover cluster using the default configuration.
  • You upgrade one of them to SQL Server 2008.

In either of these scenarios, you will notice that the SQL Server resource of  all the SQL Server 2005 instances that are currently active on the node where the SQL Server 2008 setup actions are performed, enters a failed state in the Failover Cluster Manager. 

Note: In the above statements, the phrase 'default configuration' implies that you install the SQL Server 2005 failover cluster using the default options during the setup process and did not make any changes to the failover action of the SQL Server resource after the setup has been complete. Also any stand alone (non-clustered) instances running on the node are not affected by this problem.

Cause

The default configuration of SQL Server 2005 failover cluster does not set the following policy on SQL Server resources:

"If resource fails, attempt restart on current node."

All the instances of SQL server running on a node will always share the highest version of SQL cluster resource dll present on that node. When installing or upgrading to SQL Server 2008 for the first time, the setup process replaces the existing version of SQL cluster resource dll with a newer and a higher version. As part of this procedure, it shuts down SQL Server resources to avoid a system reboot at the end of setup. Hence, if the policy above is not set, the cluster will not attempt to restart the failed SQL Server resources.

Resolution

Use Failover Cluster Manager (cluadmin.msc) to set the following policy for each of the SQL Server resources:

  • If resource fails, attempt restart on current node.

You should also consider selecting the following option on SQL resources to enable the cluster service to failover the resources to another node in cases where it is not able to bring SQL resources online on the same node.

  • If restart is unsuccessful, fail over all resources in this service or application.

The above options can be found by navigating to the Policies tab under the Properties pane of the resource.

More Information

Example:

Assume you have the following environment.

  • You have a two node (named N1 and N2) Windows Server 2008 R2 cluster.
  •  You install SQL Server 2005 failover cluster instance 1 (be it default or named instance) across both nodes, and make it online on N1.
  •   You install another SQL Server 2005 failover cluster instance 2 (be it default or named instance) side by side across both nodes, and make it online on N2.

Scenario 1: Suppose you want to upgrade cluster instance 1 to SQL Server 2008. After you finish the upgrade on N1, cluster instance 2 will stay online; then you continue and finish the upgrade on N2, cluster instance 2 will become failed.

Scenario 2: Suppose you want to install a SQL Server 2008 failover cluster instance 3 (be it default or named instance) across both nodes. After you finish the installation on N1, SQL Server 2005 failover cluster instance 1 will become failed, and cluster instance 2 will stay online; then you continue and finish the installation on N2, SQL Server 205 failover cluster instance 2 will become failed too.

Related links:
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Properties

Article ID: 2000403 - Last Review: September 22, 2009 - Revision: 6.0
APPLIES TO
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Enterprise Evaluation
  • Microsoft SQL Server 2008 Standard
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Standard Edition
Keywords: 
KB2000403

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com