July 15, 2014 at 8:05 am
I have just set a SQL 2012 availability group up, testing it is working and all seems fine.
I am not adding a listener to the set up and after googling around, can't seem to figure out why it won't work.
"the WSFC cluster could not bring the network name resource with DNS name "......." online. the DNS name may have been taken or have a conflict with existing name services or wsfc Cluster service may not be running or may be inaccessible......"
I have had a DNS created for the listener and a static IP, and using a port which is not currently used.
I have tried this with out an already created DNS, but using the created IP for it and it didn't work. I Have SA permission on the instance and local admin on the box.
Please shed some light on this? Also a domain admin has tried and had the same error. It is an easy thing i am missing I'm sure but can't seem to find it! The dns is not being used elsewhere either
July 15, 2014 at 11:57 am
your clustername account (domain/ CLUSTERNAME$) should have the full permissions to create objects in AD or you can manually go to AD and find your listner name and under security you add clustername account and grant full rights and then cluster should be able to bring you listener up in cluadmin.
July 15, 2014 at 11:58 am
SQLSteve (7/15/2014)
I have just set a SQL 2012 availability group up, testing it is working and all seems fine.I am not adding a listener to the set up and after googling around, can't seem to figure out why it won't work.
"the WSFC cluster could not bring the network name resource with DNS name "......." online. the DNS name may have been taken or have a conflict with existing name services or wsfc Cluster service may not be running or may be inaccessible......"
I have had a DNS created for the listener and a static IP, and using a port which is not currently used.
I have tried this with out an already created DNS, but using the created IP for it and it didn't work. I Have SA permission on the instance and local admin on the box.
Please shed some light on this? Also a domain admin has tried and had the same error. It is an easy thing i am missing I'm sure but can't seem to find it! The dns is not being used elsewhere either
Here is the link for it....to fix.
July 22, 2014 at 8:57 am
Thanks for your help - this resolved the issue!
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply