This issue occurs because of any of the following causes in your Windows cluster environment or availability group configuration.
Cause 1
You did not install
KB2494036 to all Windows cluster nodes that were designated as hosting replicas. To work around this issue in this situation, install
KB2494036 , and then rerun the New Availability Group Wizard.
For more information about the prerequisites for AlwaysOn availability groups, go to the following Microsoft Developer Network (MSDN) website:
Cause 2
You create an availability group without automatic failover in SQL Server 2012 (version 11.0.2100.60). Specifically, you configure the availability group by using one of the following methods:
- When you set up the availability group in the wizard, you configured a replica for asynchronous availability mode.
- When you set up the availability group in the wizard, you configured a replica for manual failover mode.
To work around this issue in this situation, upgrade SQL Server 2012 to SQL Server 2012 Service Pack 1 (SP1), and then rerun the New Availability Group Wizard.
Note This issue is resolved in SQL Server 2012 SP1.
Cause 3
A secondary replica is hosted by your Windows cluster node. This replica is configured for automatic failover without a vote. This configuration may be by design for your particular deployment. In this situation, you can safely ignore the warning message.
To check whether a particular cluster node has a vote, see the
NodeWeight value on the nodes. To obtain the
NodeWeight value, run the following Windows PowerShell cmdlets:
Get-ClusterNode | < cluster name >, Nodeweight
Cause 4
A primary replica is hosted by your Windows cluster node without a vote. This configuration may be by design for your particular deployment. In this situation, you can safely ignore this warning message.
