Horkay Blog
The postings on this site are my own and do not represent my Employer's positions, advice or strategies.
Thursday, 19 December 2013

Had an issue with a SQL Server Always On Failover Cluster Instance.

Lots of things happened at once that caused this thing to fail, It was not a production Always On cluster but one used for Load and Performance testing so it isn't monitored as closely as it should have been.

A bunch of windows patches were applied, than the SAN Storage had an issue, the end result was a mess and we had to delete the availability groups and reset them up, in the process of doing so we received this error:

Create failed for Availability group {name here}.

Failed to create, join or add replicat to availability group {name here}, because node {Server} is a possible owner for both replica {replica instance} and {primary instance}.  If one replica is failover cluster instance, remove the overlapped node from its possible owners and try again (Microsoft SQL Server, Error: 19405).

This is in a bit of a complicated environment, where we are using Always On, to off-load read-only queries with the Read-Intent attribute.  So it's a 3 node cluster, with a SQL Server Fail over cluster on nodes A and B, and a Stand-alone Instance on node C where we host the replica's to handle the read-only queries.  Works Great, till you screw the environment over with patching and san maintenance all at the same time.

This error means exactly what is says, but it took me a while to figure out that some how the sql server instance in cluster manager, was marked as having a preferred owner of all 3 nodes.  Which isn't possible as the SQL FCI was only able to be nodes A and B.  Simply unchecking the 3rd node fixed the issue, though it threw a sub-sequent error that the availability group already existed, so we had to go in and manually run a tsql command to delete the availability group on both the primary and replica instances.

Thursday, 19 December 2013 09:28:38 (Central Standard Time, UTC-06:00) | Comments [0] | SQL Server | Web_Blog#
Search
Popular Posts
Unpatched Vulnerabiltiy discovered ...
Spring Fornicator brewed...
DTA - Failed to initialize MSDB dat...
SQL Server Security, not where it n...
Check the Uptime of a Windows Serve...
Recent Posts
Archive
May, 2017 (2)
April, 2017 (1)
March, 2017 (1)
February, 2017 (1)
December, 2016 (2)
October, 2016 (2)
September, 2016 (1)
August, 2016 (1)
July, 2016 (1)
March, 2016 (2)
February, 2016 (3)
December, 2015 (4)
November, 2015 (6)
September, 2015 (1)
August, 2015 (2)
July, 2015 (1)
March, 2015 (2)
January, 2015 (1)
December, 2014 (3)
November, 2014 (1)
July, 2014 (2)
June, 2014 (2)
May, 2014 (3)
April, 2014 (3)
March, 2014 (1)
December, 2013 (1)
October, 2013 (1)
August, 2013 (1)
July, 2013 (1)
June, 2013 (2)
May, 2013 (1)
March, 2013 (3)
February, 2013 (3)
January, 2013 (1)
December, 2012 (3)
November, 2012 (1)
October, 2012 (1)
September, 2012 (1)
August, 2012 (1)
July, 2012 (4)
June, 2012 (3)
April, 2012 (1)
March, 2012 (3)
February, 2012 (3)
January, 2012 (4)
December, 2011 (3)
October, 2011 (2)
September, 2011 (2)
August, 2011 (8)
July, 2011 (4)
June, 2011 (3)
May, 2011 (3)
April, 2011 (1)
March, 2011 (2)
February, 2011 (3)
January, 2011 (1)
September, 2010 (1)
August, 2010 (2)
May, 2010 (2)
April, 2010 (3)
March, 2010 (1)
February, 2010 (4)
January, 2010 (1)
December, 2009 (3)
November, 2009 (2)
October, 2009 (2)
September, 2009 (5)
August, 2009 (4)
July, 2009 (8)
June, 2009 (2)
May, 2009 (3)
April, 2009 (9)
March, 2009 (6)
February, 2009 (3)
January, 2009 (8)
December, 2008 (8)
November, 2008 (4)
October, 2008 (14)
September, 2008 (10)
August, 2008 (7)
July, 2008 (7)
June, 2008 (11)
May, 2008 (14)
April, 2008 (12)
March, 2008 (17)
February, 2008 (10)
January, 2008 (13)
December, 2007 (7)
November, 2007 (8)
Links
Categories
Admin Login
Sign In
Blogroll