This article lists some common causes of unsuccessful automatic failover. Additionally, this article discusses the steps that you can perform in order to diagnose the cause of these failures.
The symptoms when an automatic failover is triggered successfully
Note The secondary replica transitions successfully from a RESOLVING_NORMAL status to a PRIMARY_NORMAL status.
The symptoms when automatic failover is unsuccessful
For example, in the following image, SQL Server Management Studio reports that the secondary replica is in Resolving status because the automatic failover process was unable to transition the secondary replica into the primary role:
This article describes several possible reasons that automatic failover may not succeed, and how to diagnose each cause.
Article ID: 2833707 - Last Review: Apr 22, 2013 - Revision: 1