Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. You get "Failover instance 'MSSQLSERVER' cluster group not found" when you try to add a new node to a single node SQL Server Failover cluster.

You get "Failover instance 'MSSQLSERVER' cluster group not found" when you try to add a new node to a single node SQL Server Failover cluster.

Symptoms

When you try to add a node to an existing single node SQL Server 2008 Failover Cluster using Add node to a SQL Server failover cluster feature of SQL Server 2008 setup program, you may encounter the following error message:

Failover instance 'MSSQLSERVER' cluster group not found.

Additionally you may notice that in the SQL Server Group in the Cluster Administrator or the Failover Cluster Management application, either the SQL Server Agent resource is not present or is created as a generic resource.

You may notice a message that is similar to the following in the Summary.txt log file:

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):      2064843076
  Exit facility code:           787
  Exit error code:             324
  Exit message:               Failover instance 'MSSQLSERVER' cluster group not found.
  Requested action:          AddNode
Note: You can find the summary log at the following location: 
%ProgramFiles%\Microsoft SQL Server\100\Setup Bootstrap\LOG\Summary.txt 
Note:You may notice that though the SQL Agent resource is not present in the cluster, the SQL Agent service will still be present if you look under Services applet.

↑ Back to the top

Cause

The problem occurs because the SQL Server setup program cannot find the SQL Server Agent resource in the cluster either because it is not created or it has been created with an incorrect Resource Type. You can experience this problem when the initial installation of SQL server single node cluster is either incomplete or corrupt.

↑ Back to the top

Resolution

You should examine the SQL Server setup logs for the original installation (Single node setup) to determine the corrective action that needs to be taken for the failed or corrupt installation.

For example, if the setup logs indicate that you need to repair or uninstall the problematic instance, you can refer to the following topics in Books Online:

For further information on how to troubleshoot SQL Server setup issues refer to the following article in Microsoft Knowledge Base:

  • 955396 How to troubleshoot SQL Server 2008 Setup issues

Workaround:

To work around this problem, you can manually create the SQL Server agent resource using the procedure below:

For Windows Server 2003 environment use the following procedure:

  1. In Control Panel, double-click Administrative Tools , and then double-click Cluster Administrator . 
  2. In the Cluster Administrator snap-in, expand Groups , and then click the SQL Server cluster resource group that was installed for the SQL Server 2008 failover cluster. 
  3. Right-click the SQL Server Agent resource, and then click Delete. 
  4. Create the correct SQL Agent Resource type. To do so, Open  a command prompt and type the following command to add the SQL Server Agent resource type to the cluster
    cluster restype "SQL Server Agent" /create /DLL:sqagtres.dll
  5. Recreate the SQL Server Agent resource using the steps below:
    1. Right click on the SQL Server group, point to New and then click Resource.
    2. In the Name box, type SQL Server Agent. In the Resource type box, click SQL Agent Resource, and then click Next.
      Note: The name is case sensitive unless you are on CU3 or above for SQL Server 2008 RTM.
    3. Include the original node on the cluster as possible resource owner.
    4. Right click the newly created SQL Server Agent resource and fill in the following two parameters:
      Specify the virtual server name of the SQL Instance.
      Specify the Instance name.
    5. Add the SQL Server Resource as a dependency for the newly created SQL Server Agent resource.
  6. Open Registry Editor and navigate to one of the following locations and ensure that all the values are set to 1. If not, manually edit the respective values and set them to 1.
    7. This will ensure that the configuration state for all the SQL features is set to 1, indicating that the feature is installed and configured. A value greater than 1 indicates a failure either during the installation or configuration phase of the original setup.

    For default instance:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.MSSQLSERVER\ConfigurationState

    For a named Instance
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft Microsoft SQL Server\MSSQL10.INSTNAME\ConfigurationState
  7. Bring the newly created SQL Agent Resource online.

Once the newly created resources comes online successfully, you can reattempt the AddNode operation that was failing.

Note:In Windows Server 2008 and Windows Server 2008 R2 environments, you can use Failover Cluster Management application to go through the above procedure. The application can be found under Administrative Tools in Control Panel applet.

↑ Back to the top

More Information

For scnearios where the SQL Server Agent resource is missing in the cluster administrator, you can see the following call stack in the Detail.txt  setup log file:

Exception type: System.InvalidOperationException
    Message: 
        Failover instance 'MSSQLSERVER' cluster group not found.
    Stack: 
        at Microsoft.SqlServer.Configuration.Agent.Util.GetClusterGroup(ServiceContainer ctx, String instanceName)
        at Microsoft.SqlServer.Configuration.Agent.Util.GetClusterActiveNode(ServiceContainer ctx, String instanceName)
        at Microsoft.SqlServer.Configuration.Agent.AgentConfigurationPublic.Calculate()
        at Microsoft.SqlServer.Configuration.PublishedProperties.Calculate()
        at Microsoft.SqlServer.Configuration.PublishedProperties.Calculate()
        at Microsoft.SqlServer.Configuration.InstallWizardFramework.ConfigurationController.LoadData()
        at Microsoft.SqlServer.Configuration.InstallWizard.ServicesController.LoadData()
        at Microsoft.SqlServer.Configuration.InstallWizardFramework.InstallWizardPageHost.PageEntered(PageChangeReason reason)
        at Microsoft.SqlServer.Configuration.WizardFramework.UIHost.set_SelectedPageIndex(Int32 value)
        at Microsoft.SqlServer.Configuration.WizardFramework.NavigationButtons.nextButton_Click(Object sender, EventArgs e)
        at System.Windows.Forms.Control.OnClick(EventArgs e)
        at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
        at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
        at System.Windows.Forms.Control.WndProc(Message& m)
        at System.Windows.Forms.ButtonBase.WndProc(Message& m)
        at System.Windows.Forms.Button.WndProc(Message& m)
        at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
        at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam

↑ Back to the top

Keywords: vkball, kb

↑ Back to the top

Article Info
Article ID : 2102055
Revision : 1
Created on : 1/8/2017
Published on : 9/8/2010
Exists online : False
Views : 433