Re: SQL 2008 Clustering Error

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

On Jul 20, 2:46 pm, Ross Mistry <RossMis...@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:
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...@xxxxxxxxx" wrote:
On Jul 20, 9:44 am, "drew.fl...@xxxxxxxxx" <drew.fl...@xxxxxxxxx>
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 -

Thanks, Ross, I appreciate the advice.

Drew
.

Relevant Pages

  • RE: Event Viewer
    ... I recommend that you refer to article KB242768 to remove the DNS orphaned ... registry entry and refer to KB290991 to remove SQL server registry entry. ...
    (microsoft.public.win2000.active_directory)
  • Re: Installing/Moving SQL Server 2000 on to SBS 2003 Standard Edition
    ... Users can still use public DNS to locate resources. ... but that instance does require its own SQL CALs ... and cannot benefit from the SBS "all apps in one" CAL. ... >> you could probably sell your unfettered SQL Server ...
    (microsoft.public.windows.server.sbs)
  • Re: Cant log into Domain
    ... What is listed for the DNS IPs?? ... Is it the IP address of the LAN adapter for the SBS server?? ... Several issues are appearing in a new installation of SBS2003. ... I've upgraded MSDE to SQL server following the instructions on the ...
    (microsoft.public.windows.server.sbs)
  • Re: Same instance name in cluster ?
    ... By using DNS round robin users can access 2 SQL servers instead of only one. ... SQL Server MVP ... For dns alias it's not possible to create an entry with a \ ... contact them from a single dns name so I can have high performance and high ...
    (microsoft.public.sqlserver.clustering)
  • Re: Recipient policy error with event ID 8231
    ... this was caused by DNS not resolving netbios names. ... set up the DNS settings on the Exchange box to append our local domain ... MCP (SQL Server), CCA ... We have an Exchange 2003 server which I recently upgraded to SP2. ...
    (microsoft.public.exchange.admin)