KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q253584: How to Prevent an MA from Writing to the Transaction Stack

Article: Q253584
Product(s): Microsoft Windows NT
Version(s): 2.1
Operating System(s): 
Keyword(s): kbenv kbtool
Last Modified: 27-FEB-2000

-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Metadirectory Services, version 2.1 
-------------------------------------------------------------------------------

SUMMARY
=======

When a Management agent (MA) is created, the "Write entries to the transactions
stack during synchronization" setting is enabled by default. Microsoft
recommends that you leave this default setting after your MA is fully
operational. Also, you must use this setting to allow updates generated by the
MA to be issued as delta updates by your other MAs.

MORE INFORMATION
================

You may need to disable this setting when you are testing your MA. To do so:

1. Log on to Compass with an administrator account.

2. In the Action panel, click Bookmarks, and then click Management Agents.

3. Double-click the appropriate MA.

4. In the Action panel, click Configure MA.

5. Click the Metadirectory Relationships tab.

6. On the Configuration tab, click to clear the "Write entries to the
  transactions stack during synchronization" check box.

7. Click OK.

Additional query words:

======================================================================
Keywords          : kbenv kbtool 
Technology        : kbMMSSearch kbMMS210
Version           : :2.1
Issue type        : kbinfo

=============================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.