BUG: Security Mgr w/ Long Group Names Can Cause SQL Shutdown

Last reviewed: May 2, 1997
Article ID: Q147830

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

SYMPTOMS

Enumerating members of a group with a long name in SQL Security Manager by clicking on the group can cause SQL Server to shutdown due to an unhandled exception. Executing the extended stored procedure xp_logininfo to find the members of the same group can also cause this behavior.

CAUSE

The problem occurs when a local group is granted access to SQL Server, that local group contains a global group, and the number of characters of the following items exceeds 55 characters:

  1. Domain of the local group
2. Local group name 3. Domain of the global group 4. Global group name

WORKAROUND

Rename either the global group or the local group to a shorter name so that the items in the CAUSE section of this article do not exceed 55 characters.

STATUS

Microsoft has confirmed this to be a problem in Microsoft 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

The following character limits exist in Windows NT:

item                maximum characters
-----------------   ------------------
domain name         15
machine name        15
global group name   15
local group name    256


Additional query words: sql6 xp_logininfo SQSECMGR.EXE winnt
Keywords : kbbug6.00 kbinterop kbtool SSrvAdmin
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.