GetSecurityDescriptorGroup() Returns Incorrect Primary Group

 Last reviewed: August 13, 1997
Article ID: Q152272
3.51 WINDOWS kbnetwork

The information in this article applies to:

  • Microsoft Windows NT Workstation version 3.51
  • Microsoft Windows NT Server version 3.51

SYMPTOMS

Applications that use the Win 32 call GetSecurityDescriptorGroup() may receive an incorrect or invalid primary group security ID (SID) for the referenced security descriptor.

CAUSE

The primary group SID returned is invalid because the Local Security Authority (LSA) ignores the value that should be set in the primary group field of an object's security descriptor.

RESOLUTION

The LSA was modified to correctly set the primary group SID on an objects security descriptor.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.51. This problem was corrected in the latest Windows NT 3.51 U.S. Service Pack. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces): 

   S E R V P A C K

KBCategory: kbnetwork
KBSubcategory: nt32app NTSrvWkst
Additional reference words: 3.51 prodnt
Keywords : nt32ap NTSrvWkst kbnetwork
Version : 3.51
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: August 13, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.