Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
Only Members of the Administrators Group Can Retrieve the ntSecurityDescriptor Attribute from an IDirectorySearch Result Set
Article ID: 321854 - View products that this article applies to.
This article was previously published under Q321854
Users who are not members of the Administrators group cannot retrieve the ntSecurityDescriptor attribute in a result set from an IDirectorySearch search operation, yet members of the Administrators group can retrieve it.
Service Pack InformationTo resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/260910/EN-US/ )How to Obtain the Latest Windows 2000 Service Pack
Hotfix InformationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name -------------------------------------------------------- 13-May-2002 20:53 5.0.2195.5781 123,664 Adsldp.dll 13-May-2002 20:53 5.0.2195.5781 131,344 Adsldpc.dll 13-May-2002 20:53 5.0.2195.5781 62,736 Adsmsext.dll 13-May-2002 20:53 5.0.2195.5720 357,648 Advapi32.dll 13-May-2002 20:53 5.0.2195.5595 135,952 Dnsapi.dll 13-May-2002 20:53 5.0.2195.5595 96,016 Dnsrslvr.dll 13-May-2002 20:53 5.0.2195.5722 45,328 Eventlog.dll 13-May-2002 20:53 5.0.2195.5639 146,192 Kdcsvc.dll 22-Apr-2002 20:24 5.0.2195.5640 199,952 Kerberos.dll 02-May-2002 22:44 5.0.2195.5724 71,024 Ksecdd.sys 07-May-2002 18:40 5.0.2195.5744 504,080 Lsasrv.dll 07-May-2002 18:40 5.0.2195.5744 33,552 Lsass.exe 08-Dec-2001 00:05 5.0.2195.4745 107,280 Msv1_0.dll 13-May-2002 20:53 5.0.2195.5626 306,960 Netapi32.dll 13-May-2002 20:53 5.0.2195.5723 360,208 Netlogon.dll 13-May-2002 20:53 5.0.2195.5719 916,752 Ntdsa.dll 13-May-2002 20:53 5.0.2195.5585 386,832 Samsrv.dll 13-May-2002 20:53 5.0.2195.5757 128,784 Scecli.dll 13-May-2002 20:53 5.0.2195.5757 299,792 Scesrv.dll 13-May-2002 20:53 5.0.2195.5677 48,912 W32time.dll 25-Apr-2002 23:15 5.0.2195.5677 57,104 W32tm.exe 13-May-2002 20:53 5.0.2195.5737 125,712 Wldap32.dll 07-May-2002 18:40 5.0.2195.5744 504,080 Lsasrv.dll
To work around this problem, you can have the code bind to each object individually by using the IADs interface or the IDirectoryObject interface and then retrieve the ntSecurityDescriptor attribute for each object. This workaround is much less efficient than returning the ntSecurityDescriptor attribute from a search. It takes several times longer to complete.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.