BUG: Security Mgr w/ Long Group Names Can Cause Unhandled Ex.Article ID: Q150461Creation Date: 30-APR-1996 Revision Date: 06-MAY-1996
The information in this article applies to:
BUG#: 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:
Rename either the global group or the local group to a shorter name such
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
Windows NT has the following character limits:
ITEM MAXIMUM CHARACTERS ----------------- ------------------ domain name 15 machine name 15 global group name 15 local group name 256 |
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.