We are new to SQL 2016 and I'm trying to setup AlwaysOn to replicate a read only database for reporting purposes. I have it successfully setup in my DEV and TST environments but I'm trying to setup Production and I'm getting this error when trying to add a secondary replica:
"Failed to obtain cluster information. Either the specified instance of SQL Server is not running on a Windows Server Failover Cluster (WSFC)node, or the user lacks sysadmin permissions on the SQL Server instance to obtain the cluster information."
We've had this setup before and it crashed and burned and I had to delete the availability group and my sysadmin deleted the Cluster. We went back to DEV and TST to work out the issues and I got those back up and running with no issues. My sysadmin has gone over all the setup and compared them to DEV and TST and cannot see what the issue might be. We are following the Microsoft document https://social.technet.microsoft.com/wiki/contents/articles/36143.sql-server-2016-step-by-step-creating-alwayson-availability-group.aspxAny ideas what we might be missing? I confirmed my account has sysadmin...i confirmed that always on is still enabled on both servers...we have one cluster setup with 2 separate nodes.
1) check always-on is enabled in SQL configuration manager or run SELECT SERVERPROPERTY ('IsHadrEnabled');
2) check you are local admin on all nodes
3) check cluster permission by right click on properties of the windows cluster in fail-over cluster manager
Thank you for that info. One of the first things I checked was to make sure each server had AlwaysOn still enabled. We noticed this message in the logs:
Always On: The availability replica manager is waiting for the instance of SQL Server to allow client connections. This is an informational message only. No user action is required.
And when I did some digging online, i found this:
If you delete and re-create a WSFC cluster, you must disable and re-enable the Always On availability groups feature on each instance of SQL Server that hosted an availability replica on the original WSFC cluster.
So unfortunately since this our Production server, I will need to disable and re-enable the feature during a planned maintenance window and hope it clears up the error. 🙂
Viewing 3 posts - 1 through 2 (of 2 total)