No Mapping For Invalid Characters In Computer Name

 Last reviewed: June 19, 1996
Article ID: Q149859
The information in this article applies to:
  • Microsoft Windows NT Workstation versions 3.5 and 3.51
  • Microsoft Windows NT Server versions 3.5 and 3.51
  • Microsoft SQL version 6.0

SUMMARY

Microsoft SQL 6.0 Setup does not provide mapping for invalid characters found in computer names.

MORE INFORMATION

Microsoft SQL 6.0 provides mapping for invalid characters encountered in domain and user names. By default, SQL 6.0 provides the following mapping for these invalid characters: 

   A backslash(\) in the domain name is mapped as an underscore (_).
   A hyphen (-) in user name is mapped as a number sign (#)
For example, the user name "domainname\a-username" will be mapped as "domainname_a#username."

Such mapping is not available for computer names that contain invalid characters. During Setup, an invalid character in the computer name will cause Setup to display an error message; however, SQL setup will continue. Invalid characters in the computer name will cause some problems in SQL connectivity.

SQL 6.0 considers the following characters invalid in computer names:

backslash (\) space ( ) hyphen (-) single quotation mark (') at sign (@) percent sign (%) exclamation point (!) ampersand (&) period (.)

KBCategory: kbusage
KBSubcategory: ntgeneral
Additional reference words: invalid computer mapping sql

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: June 19, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.