Underscore in Domain Name Causes Validation Errors

Last reviewed: April 24, 1997
Article ID: Q153529

The information in this article applies to:
  • Microsoft Windows NT versions 3.5 and 3.51
  • Microsoft SQL Server versions 6.0 and 6.5
  • Microsoft Systems Management Server versions 1.0, 1.1, and 1.2

SYMPTOMS

SMS fails in logging on to SQL Server when you're using SQL integrated security and attempt to specify an account from a Windows NT domain that contains an underscore, for example, "North_America\bruce."

CAUSE

An underscore ("_") in a domain name is mapped to a "\" by SQL. For example, the domain account North_America\bruce would appear to SQL as North\America. For more information, see page 246 in the Microsoft SQL Server Administrator's Guide.

RESOLUTION

There are two workarounds to this problem:

  1. Use standard security. Go into SQL Setup, Set Security Options, and
select Standard Security. For more information, see page 242ff in the Microsoft SQL Server Administrator's Guide.

  1. Set the underscore character to "not used." Go into SQL Setup, Set
Security Options, Mappings, Set Map_ to "not used."

STATUS

Microsoft has confirmed this to be a problem in Systems Management Server versions 1.0, 1.1, and 1.2. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Additional query words: prodsms
Keywords : kbnetwork smsdatabase smssetup
Version : 1.0 1.1 1.2
Platform : WINDOWS


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: April 24, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.