I am in the process of configuring a two-node failover cluster for a migration project. We are transitioning a stand-alone SQL Server to a cluster.
Environment: 2x nodes with Windows Server 2012 R2 SP1 SQL Version: SQL Server 2008 SP1
The Windows FCI is configured, validated and SQL Failover Cluster is installed and working. No issues there. The part I am having issue with is when attempting to modify the SQL Server Virtual Network Name. I follow the steps outlined here: SQL Network Name Change .
There was an error saving properties for 'SQL Server'. Failed to execute control code 20971654 Error Code: 0x8007000d The data is invalid.
Has anyone encountered this before? All information I have come across concerning renaming the SQL Server Network name has made it seem like a fairly trivial process, but I cannot get it to happen in my setup. Any assistance on this matter would be greatly appreciated.
Background on why I want to do this: The existing SQL Server is pretty much the heart & soul of all our major business operations. There are concerns with not using the same server name after the migration. I have workarounds that involve the use of DNS CNames and/or adding a secondary "OR" dependency IP address to the SQL Network Name Cluster Resource, which would be the IP address currently in use by the SQL server being migrated. We would add the dependency after taking the old server offline. This has been tested and works, but the cleanest setup for me would be to modify the SQL Server Virtual Network Name, if possible.
Not sure if I should answer my own question as I believe the issue lies in user error :)
However, I was following some apparently bad advice, so maybe this will clear up the issue for someone else in the future if they fall into the same trap.
Original Method I was using to modify SQL Server Network Name:
After bringing all the resources back online the virtual network name is successfully changed and accessible.
User contributions licensed under CC BY-SA 3.0