Microsoft KB Archive/321854

From BetaArchive Wiki
Knowledge Base


Article ID: 321854

Article Last Modified on 2/20/2007



APPLIES TO

  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Professional Edition



This article was previously published under Q321854


SYMPTOMS

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.

RESOLUTION

Service Pack Information

To 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:

260910 How to Obtain the Latest Windows 2000 Service Pack


Hotfix Information

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

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

WORKAROUND

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.

STATUS

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.

Keywords: kbhotfixserver kbqfe kbwin2ksp4fix kbbug kbfix KB321854