Microsoft KB Archive/300900

From BetaArchive Wiki
Knowledge Base


Attempts to Make Modifications with CDIR_LDP Within a Generic Management Agent Are Unsuccessful

Article ID: 300900

Article Last Modified on 1/25/2006



APPLIES TO

  • Microsoft Metadirectory Services 2.1
  • Microsoft Metadirectory Services 2.2 Service Pack 1
  • Microsoft Metadirectory Services 2.2 Service Pack 1



This article was previously published under Q300900

SYMPTOMS

Using a generic management agent (MA), the zscript template calls CDIR_LDP in the following way:

EXECUTE E:\zoomserv\BIN\cdir_ldp -imp -url="ldap://MetaDir+389" -dn="ma=SelfModifier,DsaName=MetaDir,ou=Applications,dc=Microsoft,dc=com" -impfile="E:\zoomserv\Data\ds\00000050\InputFile"


The following log message may appear in the Zscript.log file:

E:\zoomserv\BIN\cdir_ldp -imp -url="ldap://MetaDir+389" -dn="ma=SelfModifier,DsaName=MetaDir,ou=Applications,dc=Microsoft,dc=com" -impfile="E:\zoomserv\Data\ds\00000050\InputFile" Start of the LDAP update process Modify request on object ma=SelfModifier,DsaName=MetaDir,ou=Applications,dc=Microsoft,dc=com Invalid modification response 80 - SOME OTHER REASON for object ma=SelfModifier,DsaName=MetaDir,ou=Applications,dc=Microsoft,dc=com

CAUSE

This behavior occurs because the CDIR_LDP program expects that the MA directory object that is identified by the "-dn=" parameter will contain certain attributes. The list of attributes that CDIR_LDP requires includes the following:

  • zcLdapServerAddr
  • zcLdapPort
  • zcLdapDiscoveryDomain
  • zcLdapLoginDn
  • zcLdapLoginPwd
  • zcLdapAttrList
  • zcLdapFilterBase
  • zcLdapMAType
  • zcLdapOcList
  • zcLdapOcUserList
  • zcLdapOcOrgList
  • zcLdapPersonRecordIsNotLeaf
  • zcLdapPerformSubtreeSearch
  • zcLdapAlwaysUseAntiTrawling
  • zcDsImportDelta
  • zcLdapForeignOU
  • zcLdapExcludedHierarchy

All of these attributes are configured on the forms that comprise the Configure MA action in an LDAP MA. On a generic MA, some of the forms in the Configure MA action are present, and some are missing, which is the case because it is assumed that in creating a custom MA, the Microsoft Metadirectory Service (MMS) administrator will also create custom forms to perfectly match the unique situation in which this MA operates. Because it is impossible to know beforehand the requirements of the custom situation in terms of forms, only the most general purpose ones are included in the generic MA.

RESOLUTION

To supply the required attributes to CDIR_LDP, use one of the following methods. The first method is recommended due to its simplicity.

Method 1

Replace the formset that is stored in the MA with the default LDAP MA formset. To do this, use either of the following methods:

  • Replace the Formset.frs file in an existing Exchange LDAP MA working directory and update the MA from its working directory.For additional information about how to update the MA from its working directory, click the article number below to view the article in the Microsoft Knowledge Base:

    255796 Updating a Management Agent's Templates from Its Working Folder

  • Use Form Designer to update the formset for the MA.For additional information about using Forms Designer to replace the generic formset with the standard LDAP MA formset, click the article number below to view the article in the Microsoft Knowledge Base:

    301095 Using Forms Designer to replace the formset in a Management Agent

Method 2

Push the missing attributes into the MA object by using an LDAP utility such as LDP.exe.

For additional information about how to connect to MMS by using LDP, click the article number below to view the article in the Microsoft Knowledge Base:

288193 How to Use LDP to Connect to an MMS Server



Additional query words: mms metadirectory zoomit

Keywords: kbprb KB300900