Article ID: 819629
Article Last Modified on 10/26/2006
APPLIES TO
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
SYMPTOMS
When you use the IADsTools (and the client user interface, Replmon.exe) to display the results for queries that result in a large number of objects, some data may be incomplete or may not appear.
CAUSE
On the server, the IDAPAAdminLimits attribute determines the maximum number of objects that an Active Directory query can find. If the Active Directory query finds more objects than the maximum number permitted by the server, IADsTools returns incomplete results. This problem may occur if Active Directory runs a LIghtweight Directory Access Protocol (LDAP) query that does not specify a MaxPageSize parameter.
RESOLUTION
Hotfix Information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone 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 usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
File Information
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 -------------------------------------------------------- 16-May-2003 05:50 1.0.0.2234 831,539 Iadstools.dll 16-May-2003 05:50 1.0.0.2234 1,191,987 Replmon.exe
WORKAROUND
To work around this problem, modify the MaxPageSize attribute.Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Windows Server 2003, Microsoft Exchange 2000 Server, Microsoft Exchange Server 2003, or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk. To modify the MaxPageSize attribute, follow these steps:
- In an Active Directory database editor (for example, you can use either ADSIEdit or Ldp.exe), bind to an Active Directory domain controller in the forest (a specific domain controller is not required).
- In Active Directory, locate the following object:
"CN=Default Query Policy,CN=Query-Policies,CN=Directory Service,CN=Windows NT,CN=Services,CN=Configuration,DC=<yourRootDomainName>"
- Modify the MaxPageSize value in the lDAPAdminLimits attribute to increase the maximum number of objects that a query can return.
When you change the value in the attribute on one domain controller, the change replicates to all the other domain controllers. As a result, the number of objects that an Active Directory query can return to IADsTools also changes.
Note Implement this work around only until you install the hotfix. When you install the hotfix, the MaxPageSize value returns to its default value of 1000.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
MORE INFORMATION
For additional information about IADsTools, click the following article number to view the article in the Microsoft Knowledge Base:
301921 INFO: The Security Context for Using IADsTools Methods
For additional information about how hotfix packages are named , click the following article number to view the article in the Microsoft Knowledge Base:
816915 New Naming Schema for Microsoft Windows Hotfix Packages
Keywords: kbhotfixserver kbqfe kbbug kbfix kbqfe kbwin2000presp5fix KB819629
