BUG: Security Manager Fails to Expand User GroupID: Q177066
|
Within Security Manager, you can view information about the individual
members of a group with user privileges by double-clicking the group name.
However, if the Everyone group is given permissions on the
HKEY_LOCAL_MACHINE\software\microsoft\mssqlserver\mssqlserver key in the
Windows NT registry, double-clicking the user groups fails.
The xp_logininfo extended stored procedure cannot list the group members if the Everyone group is granted permissions.
To work around this problem, revoke Everyone group permissions. Do to this,
issue the following command:
exec master..xp_revokelogin Everyone
Microsoft has confirmed this to be a problem in SQL Server version 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
The problem is running master..xp_logininfo, which will not list the group
members. An example of both a successful and a failed run of xp_logininfo
is provided below.
In this example, a local Windows NT group 'Group01' was created on the
local server SERVER_A. This group had three users: two local users and one
domain user. From ISQL/W, the command "exec master..xp_logininfo
'group01','members'" was run. The results in each case are shown below.
Mapped
Account name Type Privilege login name Permission path
---------------------------------------------------------------------------
SERVER_A\user_01 user user (null) SERVER_A\Group01
SERVER_A\user_02 user user (null) SERVER_A\Group01
NORTHAMERICA\remote_01 user user remote_01 SERVER_A\Group01
(3 row(s) affected)
Mapped
Account name Type Privilege login name Permission path
--------------------------------------------------------------------------
(0 row(s) affected)
Additional query words: st proc stproc
Keywords : kbusage SSrvAdmin kbbug6.50
Version : WINNT:6.5
Platform : winnt
Issue type : kbbug
Last Reviewed: April 16, 1999