The information in this article applies to:
SYMPTOMSWhen retrieving the ntSecurityDescriptor of an object in the Membership Directory, you encounter the following error:
CAUSESite Server 3.0 does not advertise the fact that it accepts the "ntSecurityDescriptor" control, so Active Directory Service Interfaces (ADSI) 2.5 does not send it and, thus, the property cache will not contain the "ntSecurityDescriptor" by default. ADSI 2.5 was changed to avoid two roundtrips each time for servers that don't support this control. In ADSI 2.0 this works because this version of the program always sends the control, and if the server generates an error, the program sends the request again without the control. RESOLUTION
You must first explicitly load the "ntSecurityDescriptor" attribute into the property cache using the IADs::GetInfoEx() method before requesting it. For example:
Note that if your directory is secured, you must bind to the object using IADsOpenObject::OpenDSObject() (to perform an authenticated bind) rather than using GetObject(). STATUSThis behavior is by design. REFERENCESFor additional information, click the article number below to view the article in the Microsoft Knowledge Base: Q224924 MDM Does Not Display Object ACEs after Install of ADSI 2.5 Additional query words: 8000500D
Keywords : kbADSI prodsitesrv3 |
Last Reviewed: October 19, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |