Failed to bring availability group 'availability_group' online. The operation timed out. Verify that the local Windows Server Failover Clustering (WSFC) node is online. Then verify that the availability group resource exists in the WSFC cluster. If the problem persists, you might need to drop the availability group and create it again.
Method 1: Use manual steps
- Create a logon in SQL Server for the [NT AUTHORITY\SYSTEM] account on each SQL Server computer that hosts a replica in your availability group.
- Grant the [NT AUTHORITY\SYSTEM] account the following server-level permissions:
- Alter Any Availability Group
- Connect SQL
- View server state
- To create the [NT AUTHORITY\SYSTEM] account, run the following in a query window:
CREATE LOGIN [NT AUTHORITY\SYSTEM] FROM WINDOWS WITH DEFAULT_DATABASE=[master]
- To grant the permissions to the [NT AUTHORITY\SYSTEM] account, run the following in a query window:
GRANT ALTER ANY AVAILABILITY GROUP TO [NT AUTHORITY\SYSTEM]
GRANT CONNECT SQL TO [NT AUTHORITY\SYSTEM]
GRANT VIEW SERVER STATE TO [NT AUTHORITY\SYSTEM]
Make sure that these permissions exist on each SQL Server computer that could host the primary replica of the availability group.
Note The Resource Host Monitor Service process (RHS.exe) that hosts SQL Resource.dll can be run only under a System account.
For more information, see Troubleshooting automatic failover problems in SQL Server 2012 AlwaysOn environments .
Article ID: 2847723 - Last Review: Jun 6, 2013 - Revision: 1