The Windows Server Failover Clustering (WSFC) resource control API returned error code 5057. The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid.

Error:-

While creating an  Availability Group Listener I received this error
Msg 41009, Level 16, State 7, Line 1
The Windows Server Failover Clustering (WSFC) resource control API returned error code 5057.
The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid.  For information about this error code, see "System Error Codes" in the Windows Development documentation.



While Adding listener, i got below error:-

USE [master]
GO

ALTER AVAILABILITY GROUP [ADAMAG]
ADD LISTENER N'AdamListener' (
WITH IP
((N'10.12.62.147', N'255.255.255.0')
)
, PORT=1433);
GO



Msg 41009, Level 16, State 7, Line 1
The Windows Server Failover Clustering (WSFC) resource control API returned error code 5057.  The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid.  For information about this error code, see "System Error Codes" in the Windows Development documentation.
Msg 19476, Level 16, State 3, Line 1
The attempt to create the network name and IP address for the listener failed. The WSFC service may not be running or may be inaccessible in its current state, or the values provided for the network name and IP address may be incorrect. Check the state of the WSFC cluster and validate the network name and IP address with the network administrator.
Msg 19476, Level 16, State 1, Line 1
The attempt to create the network name and IP address for the listener failed. The WSFC service may not be running or may be inaccessible in its current state, or the values provided for the network name and IP address may be incorrect. Check the state of the WSFC cluster and validate the network name and IP address with the network administrator.

I did check Cluster and found Cluster is up and running fine.


I look further into this issue and found  Availability group Listener IP was same as  Windows Cluster IP.

or

The listener IP address which user was using was already in use. User was getting ping request from that IP address. 

here Windows Virtual Cluster IP was 10.12.62.147 and while Creating a Listener IP user has  given similar IP 10.12.62.147

Resolution:-

Later I created an  Availability group Listener using different unused  IP 10.12.62.148 and found I was successfully able to create a listener.

Hope this will help someone.

Thanks for Reading. 

Post a Comment

Previous Post Next Post