Microsoft KB Archive/252897

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 16:16, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base


TAMA Does Not Run Update Script for Management Agent

Article ID: 252897

Article Last Modified on 11/1/2006



APPLIES TO

  • Microsoft Metadirectory Services 2.1



This article was previously published under Q252897

SYMPTOMS

Together Administration Management Agent (TAMA) in Microsoft Metadirectory Services (MMS) 2.1 creates connector space objects and the Export.ta file, and then optionally runs a TAMA script. However, after you run TAMA, the connector name space objects and Export.ta file are successfully created but the TAMA control script may not run. If the TAMA script does not run, the associated management agent contains the correct connector space objects but the connected directory is not updated. In addition, the operator's log does not report the failure to update the connected directory.

CAUSE

This behavior occurs if the distinguished name (DN) of the management agent contains spaces.

RESOLUTION

To work around this issue, do not use spaces in the DN when you create management agents. For existing management agents, create a replacement management agent and delete the agent that contains spaces in its name.

NOTE: Renaming management agents is not supported.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Metadirectory Services 2.1.


Additional query words: prb zoomit via ma zscript genlogs fail fails execute

Keywords: kbbug kbenv kbpending KB252897