Error message:
Failed to move a Windows Server Failover Clustering (WSFC) group to the local node (Error code 5016). The WSFC service may not be running or may not be accessible in its current state, or the specified cluster group or node handle is invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
Failed to designate the local availability replica of availability group 'AG_Group' as the primary replica. The operation encountered SQL Server error 41018 and has been terminated. Check the preceding error and the SQL Server error log for more details about the error and corrective actions. (Microsoft SQL Server, Error: 41018)
Failed to move a Windows Server Failover Clustering (WSFC) group to the local node (Error code 5016). The WSFC service may not be running or may not be accessible in its current state, or the specified cluster group or node handle is invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
Failed to designate the local availability replica of availability group 'AG_Group' as the primary replica. The operation encountered SQL Server error 41018 and has been terminated. Check the preceding error and the SQL Server error log for more details about the error and corrective actions. (Microsoft SQL Server, Error: 41018)
Solution details:
1. Go to --> Failover Cluster manager --> Select the particular AG group --> Right-click the listener name--> properties-->Advanced policies. There you'll see the possible owners list.
if the specified server is not part of the owner list. Make sure to select the server name in the owner list
then you will try to failover the AG from Primary to Secondary using SSMS failvoer script.
No comments:
Post a Comment