Error when failing over Availability Group with Listener

The following error shows up in the System event log on the secondary server when trying to fail over an availability group that has a listener configured:

"Cluster network name resource 'resource_name' cannot be brought online. The computer object associated with the resource could not be updated in domain '' for the following reason:

Unable to set DnsHostName attribute.

The text for the associated error code is: A constraint violation occurred.

The cluster identity 'cluster_object' may lack permissions required to update the object. Please work with your domain administrator to ensure that the cluster identity can update computer objects in the domain."

This was due to inadequate permissions for the computer account of the Windows cluster.  The cluster computer object needs the "Read All Properties" and "Create Computer Objects" permission in the domain.  It also needs Full Control to the computer object for the cluster itself.  Once those permissions were granted, the availability group failed over successfully.

Here is the Microsoft article that details the permissions needed.

Create failed for Availability Group Listener

Error when setting up a listener for an availability group for SQL Server AlwaysOn:

"Create failed for Availability Group Listener 'listener_name'.

An exception occurred while executing a Transact-SQL statement or batch.

The WSFC cluster could not bring the Network Name resource with DNS name 'dns_name' online. The DNS name may have been taken or have a conflict with existing name services, or the WSFC cluster service may not be running or may be inaccessible.  Use a different DNS name to resolve the name conflict, or check the WSFC cluster log for more information.
The attempt to create the netowrk name and IP address for the listener failed.  The WSFC service may not be running or may be inaccessbile in its current state, or the values provided for the network name and IP address may be incorrect.  Check the state of the WSFC cluster and validate the network name and IP address with the network administrator."

This was due to inadequate permissions for the computer account of the Windows cluster.  The cluster computer object needs the "Read All Properties" and "Create Computer Objects" permission in the domain. Once those permissions were granted, the listener was created successfully.

Here is the Microsoft article that details the permissions needed.

Quorum Error When Creating an AlwaysOn Availibility Group

I ran into the following error today when trying to create a new availability group for AlwaysOn.  This was on a fresh install of SQL 2012.

"The local node is not part of quorum and is therefore unable to process this operation. This may be due to one of the following reasons:

• The local node is not able to communicate with the WSFC cluster.

• No quorum set across the WSFC cluster.

For more information on recovering from quorum loss, refer to SQL Server Books Online."

To fix this issue, make sure you have the prerequisite hotfixes applied:
Prerequisites, Restrictions, and Recommendations for AlwaysOn Availability Groups (SQL Server)

In particular, this specific error requires hotfix 2494036.

If the error still comes up, disable and re-enable AlwaysOn in SQL Server Configuration Manager, then restart the SQL instance.