![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I'm trying to setup a SQL 2008 Cluster on a Windows 2008 Failover Cluster. I'm going through the SQL Server Failover Cluster instance setup wizard. I make it to the Instance Configuration screen. I've entered SQL2K8_Cluster into the SQL Server Network Name field. I've created an A record in DNS that matches the name specified. I have also given an instance name of Primary and an instance ID of Primary. I haven't changed the Instance root directory specification at all. Name resolution appears to be working properly as I can do an nslookup on the name and I get an IP address returned. Further if I do a ping it comes back with the right IP address. I don't get any responses but DNS is definitely doing it's job. The specific error that I receive when I try to progress past this screen is: The SQL SErver failover cluster network name 'SQL2K8_Cluster is not valid. The name must be a valid DNS and WinS name. Please tell me that I don't have to setup WINS on my network to get this to work properly. I just spent 2 months getting rid of it. Any help would be greatly appreciated. Drew Flint Plex Systems |
#3
| |||
| |||
|
|
On Jul 20, 9:44 am, "drew.fl... (AT) gmail (DOT) com" <drew.fl... (AT) gmail (DOT) com wrote: I'm trying to setup a SQL 2008 Cluster on a Windows 2008 Failover Cluster. I'm going through the SQL Server Failover Cluster instance setup wizard. I make it to the Instance Configuration screen. I've entered SQL2K8_Cluster into the SQL Server Network Name field. I've created an A record in DNS that matches the name specified. I have also given an instance name of Primary and an instance ID of Primary. I haven't changed the Instance root directory specification at all. Name resolution appears to be working properly as I can do an nslookup on the name and I get an IP address returned. Further if I do a ping it comes back with the right IP address. I don't get any responses but DNS is definitely doing it's job. The specific error that I receive when I try to progress past this screen is: The SQL SErver failover cluster network name 'SQL2K8_Cluster is not valid. The name must be a valid DNS and WinS name. Please tell me that I don't have to setup WINS on my network to get this to work properly. I just spent 2 months getting rid of it. Any help would be greatly appreciated. Drew Flint Plex Systems I think I might have figured this out. Evidently, the SQL Server Network Name doesn't like to have _s in the name. Although the instance name and instance id both support these. |
#4
| |||
| |||
|
|
That error typically occurs if you are not using a valid DNS or WINS server name. *No, WINS is not required and can be retired. -- Ross Mistry - Author Windows Server 2008 Unleashed, SQL Server 2008 Management & Administration "drew.fl... (AT) gmail (DOT) com" wrote: On Jul 20, 9:44 am, "drew.fl... (AT) gmail (DOT) com" <drew.fl... (AT) gmail (DOT) com wrote: I'm trying to setup a SQL 2008 Cluster on a Windows 2008 Failover Cluster. I'm going through the SQL Server Failover Cluster instance setup wizard. I make it to the Instance Configuration screen. I've entered SQL2K8_Cluster into the SQL Server Network Name field. I've created an A record in DNS that matches the name specified. I have also given an instance name of Primary and an instance ID of Primary. I haven't changed the Instance root directory specification at all. Name resolution appears to be working properly as I can do an nslookup on the name and I get an IP address returned. Further if I do a ping it comes back with the right IP address. I don't get any responses but DNS is definitely doing it's job. The specific error that I receive when I try to progress past this screen is: The SQL SErver failover cluster network name 'SQL2K8_Cluster is not valid. The name must be a valid DNS and WinS name. Please tell me that I don't have to setup WINS on my network to get this to work properly. I just spent 2 months getting rid of it. Any help would be greatly appreciated. Drew Flint Plex Systems I think I might have figured this out. Evidently, the SQL Server Network Name doesn't like to have _s in the name. Although the instance name and instance id both support these.- Hide quoted text - - Show quoted text - |
![]() |
| Thread Tools | |
| Display Modes | |
| |