Select the product you need help with

Visual Basic Procedure to Count the Members of a Group Returns a Value of 1,000 for All Groups with Over 1,000 Members

Article ID: 814925 - View products that this article applies to.

SYMPTOMS

When you try to use the following Microsoft Visual Basic procedure to return the number of members of groups in your domain, for any group that contains more than 1,000 members, the result is 1000, where GroupName is the name of the group whose members you want to count:

get adsgroup = getobject("LDAP://cn=GroupName")
wscript.echo adsGroup.Members.count

Back to the top | Give Feedback

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

(http://support.microsoft.com/kb/260910/EN-US/ )

How to Obtain the Latest Windows 2000 Service Pack

Hotfix Information

A 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=support

(http://support.microsoft.com/contactus/?ws=support)

Note 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 Global 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-Feb-2003  15:30  5.0.2195.6613     124,176  Adsldp.dll
   16-Feb-2003  15:30  5.0.2195.6601     130,832  Adsldpc.dll
   21-Feb-2003  07:19  5.0.2195.6667      62,736  Adsmsext.dll
   16-Feb-2003  15:30  5.0.2195.6660     377,616  Advapi32.dll
   16-Feb-2003  15:30  5.0.2195.6611      49,936  Browser.dll
   16-Feb-2003  15:30  5.0.2195.6663     135,952  Dnsapi.dll
   16-Feb-2003  15:30  5.0.2195.6663      96,528  Dnsrslvr.dll
   16-Feb-2003  15:30  5.0.2195.6661      46,352  Eventlog.dll
   16-Feb-2003  15:30  5.0.2195.6627     148,240  Kdcsvc.dll
   20-Feb-2003  15:11  5.0.2195.6666     204,560  Kerberos.dll
   02-Dec-2002  18:09  5.0.2195.6621      71,888  Ksecdd.sys
   24-Jan-2003  13:40  5.0.2195.6659     509,712  Lsasrv.dll
   24-Jan-2003  13:41  5.0.2195.6659      33,552  Lsass.exe
   05-Feb-2003  07:59  5.0.2195.6662     109,328  Msv1_0.dll
   16-Feb-2003  15:30  5.0.2195.6601     312,592  Netapi32.dll
   16-Feb-2003  15:30  5.0.2195.6627     360,720  Netlogon.dll
   21-Feb-2003  07:19  5.0.2195.6666     929,552  Ntdsa.dll
   21-Feb-2003  07:19  5.0.2195.6666     392,464  Samsrv.dll
   16-Feb-2003  15:30  5.0.2195.6622     112,912  Scecli.dll
   16-Feb-2003  15:30  5.0.2195.6625     305,936  Scesrv.dll
   16-Feb-2003  15:30  5.0.2195.6601      51,472  W32time.dll
   16-Aug-2002  04:32  5.0.2195.6601      57,104  W32tm.exe
   21-Feb-2003  07:19  5.0.2195.6666     125,200  Wldap32.dll

Back to the top | Give Feedback

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.

Back to the top | Give Feedback