We have two nodes in our Always on setup running SQL 2014 SP1 with,just now, 1 database setup for always on.If I do a forced failover from Node 1 to Node 2 and then back again from Node 2 to Node one everything works perfectly.However, if I stop the SQL Server services on the Primary node the secondary node does not pick up. The dashboard says the role on the secondary gets stuck into resolving. As soon as I start the services on the Primary node it is all fine.Where do I even start to debug this issue?These are the message I see in the dashboard when it doesn't function:This secondary replica is not connected to the primary replica. The connected state is DISCONNECTEDThe role of this availability replica is unhealthy. The replica does not have either the primary or secondary role.At least one availability database on this availability replica has an unhealthy data synchronization state. If this is an asynchronous-commit availability replica, all availability databases should be in the SYNCHRONIZING state. If this is a synchronous-commit availability replica, all availability databases should be in the SYNCHRONIZED state.
↧