Management Agent Obsoletes Records After a Rename in Microsoft Metadirectory Services (322242)


The information in this article applies to:

  • Microsoft Metadirectory Services 2.2 SP1
This article was previously published under Q322242

SYMPTOMS

Under some specific conditions and configurations of a management agent, mass obsoletions can occur. For example, the Active Directory Management Agents (ADMA) logs may contain an entry that is similar to the following entry:
datetime 1069-CONNECTOR FAILED[14105]: CN=name\, name,CN=Users,NC=test.microsoft.com,ma=MicrosoftMA,DsaName=testlab,ou= Server,dc=test,dc=microsoft,dc=com
datetime Metaverse operation is not performed due to failure in the connector

CAUSE

This problem may occur if the database is damaged. This may trigger the obsoletion of a large number of users. This problem may result in a very specific scenario that involves provisioned users. For example, one or more provisioned users are disconnected from their metaverse entries. The management agent then discovers that a rename of the user has occurred in the Connected Directory. This might occur when a user is moved to another container in the Connected Directory, and this is a change of the distinguished name of the user. This may cause one or more records to become damaged, and this may cause more damage to the database over time.

RESOLUTION

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 Microsoft Metadirectory Services (MMS) service pack that contains this fix.

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:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

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 following file attributes or later: 
   Date         Time   Version      Size       File name
   ----------------------------------------------------------
   03-Jan-2002  16:37  2.2.1300.16    175,104  Cdir_ad.dll
   20-May-2002  14:01  2.2.1300.26  1,015,296  Cdir_ex.exe
   20-May-2002  14:01  2.2.1300.26  1,032,192  Cdir_ldp.exe
   20-May-2002  14:01  2.2.1300.26  1,017,856  Cdir_ln.exe
   20-May-2002  14:01  2.2.1300.26  1,060,864  Cdir_nt.exe
   20-May-2002  14:01  2.2.1300.26    998,400  Cdir_nw.exe
   20-May-2002  14:01  2.2.1300.26    987,648  Cdir_vns.exe
   20-May-2002  14:00  2.2.1300.26    964,096  Importt.exe
   20-Sep-2001  16:41  2.2.1300.10     26,624  Ldapschema.dll
   22-Apr-2002  09:04  2.2.1300.21  1,030,656  Viacompact.exe
   20-May-2002  14:00  2.2.1300.26  1,266,176  Viaserver.exe
   20-May-2002  14:01  2.2.1300.26    997,888  Zscript.exe
   01-Aug-2001  15:17                     834  Updoid.bat
   25-Jul-2001  15:08                 166,356  Db5attr.oid

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 MMS 2.2 post-Service Pack 1 cumulative hotfixes, click the article number below to view the article in the Microsoft Knowledge Base:

320718 MMS 2.2 Post-Service Pack 1 Cumulative Hotfix List

Modification Type:MinorLast Reviewed:9/30/2005
Keywords:kbHotfixServer kbQFE kbbug kbenv kbfix KB322242
©2004 Microsoft Corporation. All rights reserved.