BUG: Sec. Mgr. Adds Wrong Grp When Local/Global Have Same NameLast reviewed: May 1, 1997Article ID: Q137499 |
The information in this article applies to:
SYMPTOMSIf a global group that belongs to the default domain but happens to be the same name as a local group is added to SQL Security Manager, the local group will be added instead of the default domain group.
WORKAROUNDRename either the local or the global group to a different name.
STATUSMicrosoft 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 INFORMATIONIn SQL Security Manager, make sure the default domain points to a domain with a global group to which you would like to grant permission. For example, suppose the global group on the default domain is 'testgroup' that contains users 'sqluser' and 'administrator,' and there happens to be a local group on the local machine called 'testgroup' that contains users 'johnd' and 'janed.' When groups on the default domain are checked and theoption to grant is selected, the local group 'testgroup' with users 'johnd' and 'janed' will be added, instead of the global group 'testgroup.'
|
Additional query words: sql6 windows nt permissions user manager
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |