Unable to remove replica from read-scale availability group in SQL Server 2017

by tejas   Last Updated August 29, 2018 06:06 AM

I'm trying to remove a replica from a cluster-less (CLUSTER NONE) availability group in SQL Server 2017, but the operation is failing with this error message:

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

TITLE: Microsoft SQL Server Management Studio

Drop failed for Availability Replica 'egguswdb'. (Microsoft.SqlServer.Management.SDK.TaskForms)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=14.0.17277.0+((SSMS_Rel_17_4).180625-0100)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Drop+AvailabilityReplica&LinkId=20476


ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)


Could not process the operation. Always On Availability Groups does not have permissions to access the Windows Server Failover Clustering (WSFC) cluster. Disable and re-enable Always On Availability Groups by using the SQL Server Configuration Manager. Then, restart the SQL Server service, and retry the currently operation. For information about how to enable and disable Always On Availability Groups, see SQL Server Books Online. Availability group 'EggAG' failed to process remove-replica command. The operation encountered SQL Server error 35222 before the availability group configuration could be updated, and has been rolled back. Refer to the SQL Server error log for details. If this is a Windows Server Failover Clustering (WSFC) availability group, verify that the local WSFC node is online, and then retry the command. Otherwise, contact your primary support provider. (Microsoft SQL Server, Error: 35222)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=14.00.2002&EvtSrc=MSSQLServer&EvtID=35222&LinkId=20476

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

But the server isn't part of any WSFC cluster. Sounds like a bug in SQL Server? Any advice other than dropping/re-adding the entire availability group?



Related Questions






SQL Availability Group

Updated November 20, 2017 21:06 PM