Timeline for AlwaysOn High Availability - not always kicking in
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 28, 2018 at 11:49 | vote | accept | test | ||
| Feb 20, 2018 at 14:19 | answer | added | test | timeline score: 0 | |
| Feb 20, 2018 at 12:07 | comment | added | Shivam Kumar | also make sure password in service control manager is set correctly for service account or is not expired or changed which can create such issues | |
| Feb 20, 2018 at 11:51 | comment | added | Shivam Kumar | Preffered and Possible owners are separate things: blogs.msdn.microsoft.com/alwaysonpro/2014/02/28/… | |
| Feb 20, 2018 at 11:49 | comment | added | test | Both nodes are listed as preferred owners. The critical events for the Failover Cluster Manager shows the following msg: The Cluster service failed to bring clustered role 'NA_AVG01' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered role. | |
| Feb 20, 2018 at 11:42 | comment | added | Shivam Kumar | Do you have node B listed as the possible owner in failover cluster? If not then the services will never failover to B which I suspect is happening over here in your case. | |
| Feb 20, 2018 at 11:01 | comment | added | Shanky | When you shutdown SQL Server WSFC does not see this as a scenario where failover is required and hence the node B remains secondary replica and does not transform to primary. And since listener always connects to primary replica so in your case it is not working | |
| Feb 20, 2018 at 10:54 | review | First posts | |||
| Feb 20, 2018 at 11:02 | |||||
| Feb 20, 2018 at 10:47 | history | asked | test | CC BY-SA 3.0 |