BUG: Using SEM to Change Security Options Changes Space Syntax

Last reviewed: May 2, 1997
Article ID: Q141667

The information in this article applies to:
  • Microsoft SQL Server, version 6.0
BUG# NT: 12762 (6.00)

SYMPTOMS

If you use SQL Enterprise Manager (SEM) to change security options, the key that is used to map the Windows NT space ( ) is actually not used when you stop and restart SQL Server.

WORAKAROUND

Use the SQL Setup program to change security options.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 6.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

After installation, by default MAP$ indicates that the space ( ) character is mapped to the valid SQL Server dollar sign ($) character. If you do not change anything from SEM Security Options, all is well. If you now go into SEM and change the security options, or even if you do not change anything but click "OK" instead of "CANCEL" and then stop and restart SQL Server, MAP$ will not be used.

Similarly, if MAP# or MAP_ is changed to indicate space mapping, it will not be used after SQL Server is stopped and restarted. This can be verified by looking at the registry entries for MAP$, MAP_ and MAP# under HKEY_LOCAL_MACHINE/Software/Microsoft/MSSQLSERVER/MSSQLSERVER.


Additional query words: SQL6 winnt
Keywords : kbbug6.00 kbinterop kbsetup SSrvInst
Version : 6.0
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: May 2, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.