Select the product you need help with

"The specified account name is already a member of the local group" error message when you try to add a Windows NT 4.0 group ACL to a file or to a resource on Windows 2000

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

SYMPTOMS

When you try to add a group access control list (ACL) from a Microsoft Windows NT 4.0 domain to a resource on a Microsoft Windows 2000 domain, you may receive the following error message:

The specified account name is already a member of the local group.

Back to the top | Give Feedback

This problem occurs if you use the Windows 2000 Active Directory Migration Tool (ADMT) to migrate a Windows NT 4.0 domain to a Windows 2000 domain, and then you add a group ACL from the Windows 2000 domain to the resource.

When an account is migrated from a Windows NT 4.0 domain to a Windows 2000 domain, the new account in the Windows 2000 domain includes the Windows NT 4.0 security ID (SID) for the account in the SID history.

Therefore, when you try to add the group ACL from the Windows NT 4.0 domain, the error is returned because that account has already been added with the Windows 2000 group ACL.

Back to the top | Give Feedback

RESOLUTION

Hotfix information

After you apply this hotfix, the name of the group ACL from the Windows NT 4.0 domain will be displayed together with the group ACL from the Windows 2000 domain when you view the permissions for a file or for a resource. Therefore, you can see that the Windows NT group ACL has been added to a file or to a resource.

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.

Prerequisites

You must have Microsoft Windows 2000 Service Pack 3 or Windows 2000 Service Pack 4 installed to apply this hotfix.

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) 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
   ----------------------------------------------------------
   02-Jul-2003  21:46  5.0.2195.6767     80,144  Aclui.dll
   02-Jul-2003  21:46  5.0.2195.6748    124,688  Adsldp.dll
   02-Jul-2003  21:46  5.0.2195.6748    132,368  Adsldpc.dll
   02-Jul-2003  21:46  5.0.2195.6748     63,760  Adsmsext.dll
   02-Jul-2003  21:46  5.0.2195.6761    381,712  Advapi32.dll
   02-Jul-2003  21:46  5.0.2195.6753     69,392  Browser.dll
   02-Jul-2003  21:46  5.0.2195.6680    134,928  Dnsapi.dll
   02-Jul-2003  21:46  5.0.2195.6663     92,432  Dnsrslvr.dll
   02-Jul-2003  21:46  5.0.2195.6753     47,376  Eventlog.dll
   02-Jul-2003  21:46  5.0.2195.6759    148,240  Kdcsvc.dll
   18-Jun-2003  17:43  5.0.2195.6758    205,072  Kerberos.dll
   26-Mar-2003  21:37  5.0.2195.6695     71,888  Ksecdd.sys
   28-May-2003  20:39  5.0.2195.6749    509,712  Lsasrv.dll
   28-May-2003  20:39  5.0.2195.6749     33,552  Lsass.exe
   05-Apr-2003  00:12  5.0.2195.6680    117,520  Msv1_0.dll
   02-Jul-2003  21:46  5.0.2195.6601    311,568  Netapi32.dll
   02-Jul-2003  21:46  5.0.2195.6695    371,984  Netlogon.dll
   02-Jul-2003  21:46  5.0.2195.6697  1,040,144  Ntdsa.dll
   02-Jul-2003  21:46  5.0.2195.6742    392,464  Samsrv.dll
   02-Jul-2003  21:46  5.0.2195.6737    131,344  Scecli.dll
   02-Jul-2003  21:46  5.0.2195.6737    306,448  Scesrv.dll
   27-Jun-2003  00:27  5.0.2195.6761  4,607,488  Sp3res.dll
   02-Jul-2003  21:46  5.0.2195.6601     51,472  W32time.dll
   16-Aug-2002  13:32  5.0.2195.6601     57,104  W32tm.exe
   02-Jul-2003  21:46  5.0.2195.6741    126,224  Wldap32.dll

Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Back to the top | Give Feedback

MORE INFORMATION

For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:

816915

(http://support.microsoft.com/kb/816915/ )

New file naming schema for Microsoft Windows software update packages

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

824684

(http://support.microsoft.com/kb/824684/ )

Description of the standard terminology that is used to describe Microsoft software updates

Back to the top | Give Feedback