FIX: SQL Cluster Install Fails When SVS Name Contains Special Characters (220156)



The information in this article applies to:

  • Microsoft SQL Server 7.0

This article was previously published under Q220156
BUG #: 54278 (SQLBUG_70)

SYMPTOMS

When installing SQL Server 7.0 clustering on a cluster whose SQL Virtual Server (SVS) name contains special characters (such as hyphens or dashes), the Cluster Wizard returns the message "Invalid Name".

CAUSE

The SQL Server 7.0 Cluster Wizard performs the same name checks as the SQL Server 6.5 Cluster Wizard, even though SQL Server 7.0 now supports all computer names that are valid under Windows NT.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next SQL Server service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:
   Version    File name     Platform
   ---------------------------------
   7.00.643   S70643i.exe   x86
   7.00.643   S70643a.exe   Alpha
				

NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.


STATUS

Microsoft has confirmed this to be a problem in SQL Server 7.0.

Modification Type:MinorLast Reviewed:10/5/2005
Keywords:kbBug kbfix kbQFE KB220156