Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Virtual Network Name Change Error Expand / Collapse
Author
Message
Posted Tuesday, April 15, 2014 8:45 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Yesterday @ 11:04 PM
Points: 396, Visits: 979
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. Details are below:

Node(s) OS: 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: [url=http://msdn.microsoft.com/en-us/library/ms178083(v=sql.100).aspx][/url].

Error Received:
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.
Post #1561916
Posted Wednesday, April 16, 2014 5:27 AM This worked for the OP Answer marked as solution


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 3:38 PM
Points: 6,637, Visits: 14,220
It's a permission issue on the AD side, you'll need to pre stage the VCO, this link gives more detail

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1562242
Posted Wednesday, April 16, 2014 12:22 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Yesterday @ 11:04 PM
Points: 396, Visits: 979
Ok, I'm going to mark this as answered but, I believe the issue lies in user error :)

Original Method I was using to modify SQL Server Network Name:
1. Failover Cluster Manager (Win 2012) -> SQL Server Role -> click resources tab -> Bring Server Name Resource offline.
2. Right Click SQL Server Resource and select Properties
3. On the Properties tab modify VirtualServerName value
4. Click OK and receive error specified in question above.

Correct Way:
1. Failover Cluster Manager (Win 2012) -> SQL Server Role -> click resources tab -> Bring Server Name Resource offline.
2. Right Click on Server Name Resource for SQL Server Network Name and select Properties
3. On the General tab modify the DNS Name to the desired new name for the SQL Server Virtual Network Name

After bringing all the resources back online the virtual network name is successfully changed and accessible. Additionally, the @@SERVERNAME and entry in sys.servers is updated to the new name as well.

Post #1562411
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse