Make sure, the account you are using to install this Failover Cluster should have Create Computer Object and Read all Properties permissions on the OU. Once the validation completed successfully, click the checkbox next to Create the cluster node using the validated nodes to start the failover cluster installation. This will check whether the all the necessary pre-requisites are met to begin the failover cluster installation. Open Failover Cluster Manager from the Tools menu in Server Manager to start the failover cluster Validate Configuration wizard. I have installed the Failover Cluster role on both of these servers and configured a heartbeat network between these two servers. To configure AlwaysOn, both the servers, Node01 and Node02, should be part of the same Windows Server Failover Cluster. On the other server, I brought the disk online to test that the disk is accessible on both the server.

To begin with, I initialized the disk on one server using Computer Management, brought it online, formatted with NTFS partition and assign a drive letter ( Q) before taking it offline. I am going to use those two servers as Windows server Failover Cluster nodes and setup AlwaysOn availability group using that. In the last post, I had configured the iSCSI target service to share the disk between two servers. Once the Shared Memory client protocol is enabled, I was able to open the SQL Server logs using SSMS (both from GUI and using T-SQL query). However, when I checked the SQL Native Client Configuration, I observed that the client protocol Shared Memory was in disabled state. Both TCP/IP and Shared Memory was enabled. Started looking at the SQL Server Configuration Manager, checked the Protocols used by the SQL Server instance. Since the error was related to Loopback Connection, I suspect the issue might be related to network configuration. Although when I tried to open the SQL server error log using Notepad, I was able to read through the error log. When I expanded the SQL Server instance using SSMS, and expanded Management and select SQL Server Logs, no error log files were listed there. Please see event log for more information. Today while I was trying to access the SQL Server error log on my express instance (by executing xp_readerrorlog), I received the below error.įailed to open loopback connection. Recently my laptop was upgraded to Windows 10.

Ms sql master database