Cluster service verification Failed error

While installing SQL 2008 R2 database server on a failover cluster, the Setup Support Rules identifies problem that might occur when you install SQL Server Setup support files. Any failures must be corrected before setup can continue.
The following rules may fail when you install SQL 2008 R2 database server on a Windows 2012 failover cluster.
Cluster service verification…. Failed
Microsoft Cluster Service (MSCS) cluster verification errors…. Failed

SQL-Clu-error1

How to fix this?
Install Failover Cluster automation Server feature on all the cluster nodes and rerun the SQL database setup wizard.

To install Failover Cluster automation Server feature, Open Server Manager and then click on Manage and select Add Roles and Features.

SQL-Clu-error2

Follow the wizard and from Features page, drill down Remote Server Administration Tools – Feature Administration Tools – Failover Clustering Tools and select Failover Cluster automation Server.

SQL-Clu-error3
Hope this bit of information is helpful for someone to resolve their problem.

SQL Server Agent not listed as cluster resource

While installing SQL Database server 2008 R2 on a Windows 2008 R2 two node cluster, I encountered following problem. Thought of posting this so that this might be helpful for anyone faces the same problem.

The SQL cluster installation completed with failures.

Event Log:

Windows Event Log showed Error “SQLServerAgent could not be started (reason: Unable to connect to server (local); SQLServerAgent cannot start”.  With event ID 103

SQL Server Management Studio:

The SQL Server Management Studio was able to connect to database but the agent service is failed to start.

SQL Server Agent was missing in cluster resource listing.

To add missing agent resource, follow the below steps:

Step-1:  Add the SQL agent resource type:  Run command prompt with Administrator privilege and run

cluster restype “SQL Server Agent” /create /DLL:sqagtres.dll

Step-2:  Add the SQL agent resource: In the Failover Cluster Management, Click Add a resource from Action panel and then click More resources, select A-Add SQL Server Agent.

Note: Name the resource as “SQL Server Agent”, as this is case sensitive unless you are on CU3 or above for SQL Server 2008 RTM.

Right-click on the SQL Agent Resource and go to Properties and fill in values for the following two parameters.

VirtualServerName  (the network name specified while installing SQL cluster)

InstanceName(MSSQLSERVER for default instance  otherwise specify the named instance name).

Add all the SQL Server Resource as a dependency for the newly created SQL Server Agent resource.

Step-3 : Modify the registry entry: Open Registry Editor and browse to the following location.

If you are running Default Instance:

 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.MSSQLSERVER\ConfigurationState

If you are running Named Instance:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft \Microsoft SQL Server\MSSQL10.INSTNAME\ConfigurationState

Make sure that the values for all the keys present are 1. In case it is not, change it to 1.

Note:This will set the configuration state for all SQL features to 1, meaning the feature is installed and configured. A value greater than 1 indicates either an install failure or configuration failure.

Step-4 : bring the  SQL Server Agent online: go to the Failover Cluster Management and thenright clickon SQL Server Agent, bring online.

 

SQL Server Management Studio shows agent service as started.

Step-5: In case the SQL agent resource failed to come online, do a repair:

Launch the SQL Server Setup program (setup.exe) from SQL Server installation media. After prerequisites and system verification, the Setup program will display the SQL Server Installation Center page. Click Maintenance in the left-hand navigation area, and then click Repair to start the repair operation

 

Refreshing SQL 2008 Cluster Hardware

Existing environment:

3 node SQL 2008 cluster built on windows 2008 server operating system. Each nodes hosting own database instance, all other nodes are configured as failover nodes for each instances.

Scope:

Refresh server hardware to different model with zero down time for database services. Third party cluster manager agent, backup and monitoring agents should remain same.

Preparation:

Get details of cluster disks assigned to the existing nodes and assign same disks to the new server.

Cross check the disk availability and verify with existing nodes.

Solution summary:

Failover instance from one node and shut down the node for backup.

Use physical to physical migration tool to take image backup and restore the same to new proposed server hardware.

Bring up the new server and perform cleanup such as uninstall drivers/management tools related to old server hardware etc..

To view and remove unused devices in Device Manager,

Open command prompt as administrator and run following commands

Set devmgr_show_nonpresent_devices=1

Devmgmt.msc

Click on view ->  show hidden devices

All devices (used and unused) will be listed,

Right click on the one grayed (unused), select Uninstall.

Make sure to select “remove drivers for this device” and click OK.

Evict the missing node (old server node) from SQL database cluster

Remove old cluster configuration settings from new server.

Open command prompt as administrator and run following commands

Cluster node <node name> /forcecleanup

Refresh (remove and add ) the  failover clustering feature

Rejoin the node to existing database cluster

Assign resource in all groups

To verify the node assignment on all resources,

  1. Right      click each and every resources,      expand resources wherever required.
  2. Select      Properties.
  3. Click      “Advanced Policies”.
  4. Check      all nodes are checked in the “Possible Owners” box.

Repeat 1-4 on the entire resource group

Failback the instance to new node and observe application connectivity

Repeat the same for other nodes….

%d bloggers like this: