Cluster resource 'SQL Network Name (XXXSQL01)' failed to go online because its associated computer account (XXXSQL01) exists in Active Directory and the Kerberos authentication is not enabled for the resource. Client applications that are using Kerberos based authentication (either directly or through the Negotiate security package) will fail to authenticate when contacting a service by this network name. To bring the resource online, either enable Kerberos authentication or delete the computer account.

Issue:-

Sometimes in Windows Server 2003 Windows Cluster you get error

Issue:-

Cluster resource 'SQL Network Name (XXXSQL01)' failed to go online because its associated computer account (XXXSQL01) exists in Active Directory and the Kerberos authentication is not enabled for the resource. Client applications that are using Kerberos-based authentication (either directly or through the Negotiate security package) will fail to authenticate when contacting a service by this network name.
 To bring the resource online, either enable Kerberos authentication or delete the computer account.

Problem:-

The reason for this could be that the changes in Active Directory isn't
replicated around to all Domain Controllers. You could initiate Force
Replication but if you are in an enterprise environment this could cost in
terms of bandwidth. Hence when you delete the computer account and it's notreplicated you would get this message.

Resolution:-

Start-->run-->cluadmin.exe-->right click on the resource group and on right pane click on SQL Network Name --> Right click on the SQL Network Name--> Click on Parameters Tab and select the check box      DNS Registration Must Succeed 

Enable Kerberos Authetication.

Then try to bring the resource on line. it will come up.

SQL Server 2012 - INDIRECT CHECKPOINTS

SQL Server 2012 - INDIRECT CHECKPOINTS

Violation of AlwaysOn constraint

================================

Rakesh configures WSFC cluster with two nodes, NODE01 and NODE02. He installs a SQL Server failover cluster instance, fciInstance1, on both NODE01 and NODE02 where NODE01 is the current owner for fciInstance1.

On NODE02, Rakesh installs another instance of SQL Server, Instance3, which is a stand-alone instance.

On NODE01,  Rakesh  enables fciInstance1 for AlwaysOn Availability Groups. On NODE02, he enables Instance3 for AlwaysOn Availability Groups. Then he sets up an availability group for which fciInstance1hosts the primary replica, and Instance3 hosts the secondary replica.

At some point fciInstance1 becomes unavailable on NODE01, and the WSFC cluster causes a failover of fciInstance1 to NODE02. After the failover, fciInstance1 is a AlwaysOn Availability Groups-enabled instance running under the primary role on NODE02. However, Instance3 now resides on the same WSFC node as fciInstance1. This violates the AlwaysOn Availability Groups constraint.

Detailed Explanation in this blog:-

http://blogs.msdn.com/b/arvindsh/archive/2012/09/26/failover-cluster-instance-alwayson-availability-group-dr-scenario.aspx

SQL 2012 setup fails with "Wait on the database engine recovery handle failed in windows server 2008 R2 Cluster"

SQL 2012 setup fails with "Wait on the database engine recovery handle failed in windows server 2008 R2 Cluster"

Remove a Secondary Replica from an Availability Group & Remove a Database from AlwaysOn for Maintenance or Migration

Remove a Secondary Replica from an Availability Group & Remove a Database from AlwaysOn for Maintenance or Migration & Remove primary replica or drop Availability Group for Reconfiguration of AlwaysOn.

A problem occurred when loading the Microsoft SQL Server Management Studio menu.

Issue:-

After SQL Server 2012 Enterprise edition installation, some time SSMS do not invoke and Error comes like


---------------------------
Microsoft SQL Server Management Studio
---------------------------
A problem occurred when loading the Microsoft SQL Server Management Studio menu. To fix this problem, run 'Ssms.exe /resetsettings' from the command prompt. Note: this command resets your environment settings.