Archive for the ‘Windows Cluster’ Category

Timeout with Multi-subnet Listener

September 1, 2015 Leave a comment


Time-out error and you cannot connect to a SQL Server 2012 AlwaysOn availability group listener in a multi-subnet environment


Once you are done with AG Creation and Listener configuration , change the RegisterAllProvidersIP value from 1 to 0.





PS C:\Users> Get-ClusterResource AG_ListenerName| Get-ClusterParameter RegisterAllProvidersIP

Change to 0


PS C:\Users> Get-ClusterResource AG_ListenerName | Set-ClusterParameter RegisterAllProvidersIP 0

Categories: Windows Cluster

Cluster Core Resource Offline/failed after multiple failovers

February 22, 2015 Leave a comment

Cluster group was failed after multiple server reboots/failovers (moving of cluster resource group multiple times)


Get what all resources are failed / offline

PS:> Get-ClusterResource |Where-Object  {$.state –eq “Failed”}


PS:> Get-ClusterResource |Where-Object  {$.state –eq “offline”}




Check the cluster core resource owner

PS:> Get-ClusterGroup


Move the Cluster Core Resource to the logged in node (If the resource is in failed state , moving the resource will bring the resource online)

Ps:> Move-ClusterGroup “Cluster Group” –Node  SQL02


Bring the offline “Cluster Group” Online

PS:>Start-ClusterGroup “Cluster Group”


Categories: Windows Cluster

Forcing the clearing of persistent reservations on a disk formerly used by the cluster

February 7, 2011 1 comment


It happens most of the time that while Cluster Failover occurs or due to some issue one of the disk or more went off line and on trying to being the resource online we get error as below.


The Cluster service failed to bring clustered service or application ‘SQL Server’ completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.

Cluster resource ‘Disk E:’ in clustered service or application ‘SQL Server’ failed.


If disk failover occurs but the server that takes ownership of a disk cannot read it, the cluster cannot maintain availability of the disk. If information written to the disk is changed during the process of failover, it could cause issues for users or software that requires this information. In either case, if the affected disk is a disk witness (a disk that stores cluster configuration data and participates in quorum), such issues could cause the cluster to lose quorum and shut down.


Open the Disk Management under storage of Computer management .Get the disk number which failed.

Open Command Prompt with “Run as Administrator”

Run the command in command prompt

Cluster node Server name /clearpr:DiskNo(ex:5)

Ex: cluster node cpnftsdtdb1 /clearpr:5

Once clearing of persistent reservations on the disk is done. Try to bring the resource online.

Categories: Windows Cluster

Failover Cluster from Command Prompt

January 21, 2011 1 comment
We all have learnt how windows cluster work and how SQL Server works with Windows Cluster.
As a database administrator i deal everyday with clusters and clusting issues.

Here we will see how to check Cluster,Cluster Resources,Nodes etc from Command Prompt and also how to failover to the available nodes.

It will help you check cluster resources when the Cluster GUI is not able to provide proper information in case Disk Hangs, failover is taking longer then expected etc.


Categories: Windows Cluster