June 11, 2015 at 11:01 am
Hello All
I am trying to setup an AG on a cluster, I was able to define where I want my replica, but I need to setup the ip for the listener of that one
When I am adding the Ip at the listener I am getting the following message:
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.
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. (Microsoft SQL Server, Error: 41009)
Browsing around I found this guide:
https://technet.microsoft.com/en-us/library/cc731002(v=ws.10).aspx
And I make sure that the cluster has permissions to "Read all properties", "Create Computer Objects", even to "Create all child" permissions
I also added those permissions to the account that starts sql at that cluster and I am logged as that and I am still getting the error
I would appreciate any help on this since it is getting a bit urgent....
June 11, 2015 at 11:22 am
as to add some more info, at AD the cluster and all its nodes are not at the default OU...
June 11, 2015 at 2:00 pm
as to add some more info, at AD the cluster and all its nodes are not at the default OU...
June 12, 2015 at 4:28 am
check with your network admins as you'll likely need to grant specific permissions for the cluster CNO to create VCO's
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
June 12, 2015 at 6:34 am
Perry Whittle (6/12/2015)
check with your network admins as you'll likely need to grant specific permissions for the cluster CNO to create VCO's
Thanks, I was able to solve the non-issue, the network ifnormation that I was provided was not very accurate and that was the source of the problem
April 9, 2019 at 1:31 pm
Hi Ricardo,
Do you happen to remember what they got wrong (i.e. was it in a different subnet)?
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply