October 9, 2017 at 4:55 pm
We have 2 nodes, both were running SQL 2014 cluster. We had to upgrade the windows OS to 2016, the network admin wiped out the operating system but the windows cluster was not destroyed. After the OS upgrade was done, the old SQL roles were removed from the windows cluster.When I tried to install SQL 2016 server failover cluster, I used the same virtual cluster virtual IP address which was used for the SQL 2014 cluster. However I got below error:
Error installing SQL Server Database Engine Services Instance Features
The common properties for resource 'SQL IP Address 1 (VirtualSQLName)'
could not be saved. Error: There was a failure to call cluster code from a provider.
Exception message: The cluster IP address is already in use..
Why the installation fails if the old roles were removed, meaning the virtual IP address is not being in use by any old SQL instance since they were uninstalled.
Thanks.
October 9, 2017 at 6:16 pm
lsalih - Monday, October 9, 2017 4:55 PMWe have 2 nodes, both were running SQL 2014 cluster. We had to upgrade the windows OS to 2016, the network admin wiped out the operating system but the windows cluster was not destroyed. After the OS upgrade was done, the old SQL roles were removed from the windows cluster.When I tried to install SQL 2016 server failover cluster, I used the same virtual cluster virtual IP address which was used for the SQL 2014 cluster. However I got below error:Error installing SQL Server Database Engine Services Instance Features
The common properties for resource 'SQL IP Address 1 (VirtualSQLName)'
could not be saved. Error: There was a failure to call cluster code from a provider.
Exception message: The cluster IP address is already in use..Why the installation fails if the old roles were removed, meaning the virtual IP address is not being in use by any old SQL instance since they were uninstalled.
Thanks.
Did you double check for the IP being used with ping and/or nslookup?
You may want to check the arp cache and see if the IP entry is still in there: arp -a
Sue
October 10, 2017 at 3:20 am
This was removed by the editor as SPAM
October 10, 2017 at 5:44 am
Thank you both Sue and Prettsons, I did see the link but I have not tried it yet. I am going to give it a try today. I did ping the IP and it shows it is being in use.
October 10, 2017 at 8:08 am
lsalih - Tuesday, October 10, 2017 5:44 AMThank you both Sue and Prettsons, I did see the link but I have not tried it yet. I am going to give it a try today. I did ping the IP and it shows it is being in use.
If ping resolves, have you tried nslookup to see what is using that IP?
Sue
October 10, 2017 at 8:16 am
Sue,
I have, and I am getting can't find the IP message.. As I said the two nodes were rebuilt but the cluster was not destroyed. The old SQL instances were manually removed from the cluster.
I did arp -a as you suggested, and that showed the ip in cached. I issued arp-d to remove the entry, then tried the install again. I got same error, but when
October 10, 2017 at 8:42 am
lsalih - Tuesday, October 10, 2017 8:16 AMSue,
I have, and I am getting can't find the IP message.. As I said the two nodes were rebuilt but the cluster was not destroyed. The old SQL instances were manually removed from the cluster.
I did arp -a as you suggested, and that showed the ip in cached. I issued arp-d to remove the entry, then tried the install again. I got same error, but when
Maybe try a flushdns since ping (I think) uses the client dns service.
Sue
October 10, 2017 at 10:48 am
Sue,
After talking to network team, it turned out I was given the windows cluster ip address and not the virtual SQL ip address which makes a big difference. I used the correct IP and my cluster installation is now complete.
Thank you for your help.
October 10, 2017 at 10:56 am
lsalih - Tuesday, October 10, 2017 10:48 AMSue,After talking to network team, it turned out I was given the windows cluster ip address and not the virtual SQL ip address which makes a big difference. I used the correct IP and my cluster installation is now complete.
Thank you for your help.
Yup..that makes a difference. Glad it worked out and thanks for posting back -
Sue
October 11, 2017 at 3:24 am
This was removed by the editor as SPAM
October 13, 2017 at 7:18 am
Hi Prettsons,
My one challenge setting up the cluster is the CEIP resource, I had to deal with security issue and not having the resource failover properly to the other node. Is it safe to remove this resource from the cluster?
I had to change the default login account for the CEIP service to use local account in order to make the instance come online, and now I am dealing with the instance failing to come back online when I try to it to the other node. I think it has to do with access right to the audit log file in the other node which I am troubleshooting.
I am not sure why Microsoft made this part of the cluster resource if it is an option and can be turned off if you do not want to send feedbacks to Microsoft. a true pain.
I was getting below before I changed the service account to use local account when I was installing the failover cluster node:
Thecluster resource 'SQL Server CEIP (INSTANCE0name)' could not be broughtonline. Error: There was a failure to call cluster code from a provider.Exception message: Generic failure . Status code: 5023. Description: The groupor resource is not in the correct state to perform the requested operation
October 16, 2017 at 6:58 am
lsalih - Friday, October 13, 2017 7:18 AMHi Prettsons,
My one challenge setting up the cluster is the CEIP resource, I had to deal with security issue and not having the resource failover properly to the other node. Is it safe to remove this resource from the cluster?
I had to change the default login account for the CEIP service to use local account in order to make the instance come online, and now I am dealing with the instance failing to come back online when I try to it to the other node. I think it has to do with access right to the audit log file in the other node which I am troubleshooting.I am not sure why Microsoft made this part of the cluster resource if it is an option and can be turned off if you do not want to send feedbacks to Microsoft. a true pain.
I was getting below before I changed the service account to use local account when I was installing the failover cluster node:
Thecluster resource 'SQL Server CEIP (INSTANCE0name)' could not be broughtonline. Error: There was a failure to call cluster code from a provider.Exception message: Generic failure . Status code: 5023. Description: The groupor resource is not in the correct state to perform the requested operation
You can remove the CEIP role - follow the instructions towards the end of this article:
How to configure SQL Server 2016 or later to send feedback to Microsoft
Sue
October 16, 2017 at 8:22 am
Sue,
I agree, I could remove rule of CEIP by issuing Remove-ClusterResource but I preferred not do so because it was not recommended. Even though the documentation shows how to add the resource back to the cluster. What happened in my case is that I changed the service account to local on the primary node, but did not fail to change the failback service. Once I replaced all service accounts to local, then everything was successful. I have to remember there are 2 services for each instance and that is where I had the mistake. Now I have a working SQL 2016 cluster without an issue.
Thank you so much for your input and guidance here, I appreciate it very much.
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply