Article ID: 313692
Article Last Modified on 10/12/2005
APPLIES TO
- Microsoft Metadirectory Services 2.2 Service Pack 1
- Microsoft Metadirectory Services 2.2 Service Pack 1
This article was previously published under Q313692
SYMPTOMS
Test mode does not work as expected when you run the Active Directory Management Agent (ADMA). In addition, when you run the ADMA in test mode, deletions that are sent to Active Directory are processed; the objects in Active Directory are deleted.
CAUSE
The reason that the deletions are processed is that the Update Active Directory checkbox is selected during the ADMA run. Test mode was designed only for testing metadirectory updates. However, test mode is not supported in the ADMA. This is because all other management agents besides the ADMA have staged processing to discover from connected directory, synchronize to Microsoft Metadirectory Services, and update connected directory. The original design expected that the files for discovery and export would be used to predict the updates that would go out to Active Directory and into the connector space. This, however, did not allow any type of prediction as to what effects would occur during the synchronize metaverse stage, and therefore the flag to run in test mode and log this processing was introduced. You can using the flat file management agents to discover and synch with logging to determine the actual effects on the Metaverse without having to send out the connected directory changes. You can examine those changes in the export files that will not be sent.
For the ADMA, you only have two stages, import and export. For this management agent, there is no way to examine the exports that will go out without applying them. If the administrator wants to see what types of changes will occur to the metaverse and does not want to send outbound changes, then the administrator only needs to clear the Update Active directory checkbox. The ADMA cannot support this feature because the ADMA does not have all the required logic to handle a test import. This required logic is beyond the logic required for the flat file management agents because the ADMA does not use the same staged processing.
RESOLUTION
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next version of Microsoft Metadirectory Services 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 should have the following file attributes or later:
Date Time Version Size File name
--------------------------------------------------------------
03-Jan-2002 16:37 2.2.1300.16 shp 175,104 Cdir_ad.dll
14-Dec-2001 16:14 2.2.1300.15 shp 1,028,096 Cdir_ldp.exe
11-Sep-2001 14:41 2.2.1300.7 shp 1,013,760 Cdir_ln.exe
02-Aug-2001 16:39 2.2.1300.4 shp 960,000 Importt.exe
20-Sep-2001 16:41 2.2.1300.10 shp 26,624 Ldapschema.dll
21-Sep-2001 11:26 2.2.1300.8 shp 1,270,160 Viaserver.exe
This hotfix detects that Test mode is activated and prevents the ADMA from running until you deactivate Test mode. After you apply this hotfix, the ADMA cannot run in Test mode. If you try to run the ADMA in Test mode, the following message is recorded in the Adma.log file:
ERR_00 0c48 02/02/04 15:29:44.468 (AD-MA_runMa)
!!!!!!!!!!
!!
!! The AMDA's test mode flag has been set.
!! This mode is unsupported.
!! The ADMA has been disabled until this flag is removed.
!! Please disable the 'Test Metadirectory Updates' option
!! in the UI or remove the msMMS-dsSyncLogOnly attribute
!! from the MA record.
!!
!!!!!!!!!!
DBG_01 0c48 02/02/04 15:29:44.562 (AD-MA_runMa) MA completed
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
MORE INFORMATION
How to Clear the Test Mode Check Box
- In Compass, click the ADMA that logged the message that is listed in the "Resolution" section of this article.
- Click Operate MA.
- Click the Operational Settings tab.
- Clear the Log synchronization details without updating the metadirectory check box. This removes the msMMS-dsSyncLogOnly attribute from the MA object.
NOTE: If you are setting the msMMS-dsSyncLogOnly attribute to TRUE on the management agent programmatically, remove the attribute or set the value to FALSE.
For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
320718 Microsoft Metadirectory Services 2.2 Post SP1 Hotfix List
Additional query words: mms zoomit
Keywords: kbbug kbfix kbqfe kbhotfixserver KB313692
