There Is a Foreign User Export Limitation in Delta Mode (290390)



The information in this article applies to:

  • Microsoft Metadirectory Services 2.1
  • Microsoft Metadirectory Services 2.2

This article was previously published under Q290390

SUMMARY

When you export Foreign Users or Custom Recipients (such as in Microsoft Exchange) to the connected directory, you should be aware of how the configuration of Inclusion/Exclusion rules impacts the exported users if the computer is running the Management Agent (MA) in Delta mode.

In Delta mode, you can send updates to the connected directory in the form of Adds, Modifies and Deletes without exporting all of your Foreign Users upon each run. This limits network traffic and only sends the necessary updates to the connected directory. However, if you have a user in the metaverse that you have previously excluded from export that is based on your Inclusion/Exclusion rule configuration, and this user now meets the conditions of these rules and is no longer excluded from Foreign User export, MMS attempts to send that user to the connected directory as a modification rather than an addition. The connected directory rejects the modification request because the Foreign User does not exist in the connected directory.

In Exchange, an error message that is similar to the following one is logged in the MA logs:
Error was encountered in function : HrDoImport calling DAPIWrite.. Error message :
DAPIWrite for Mailbox /o=Org1/ou=Site1/cn=Custom Recipients/cn=Test User failed with DAPI error 0xc0000120. The HRESULT code was 0x80004005.

MORE INFORMATION

The behavior of the user being processed as a modification as apposed to an addition occurs as a result of the Importt.exe process that scans the transaction stack and that looks for new transactions since its last run. During the Importt.exe scanning, only a modification request for this user object is found. This is correct because the user object existed before the last export run. Importt.exe attempts to process the modification as requested.

To work around this behavior, use delta foreign exports that you mix periodically with full foreign exports. For example, try to run deltas throughout the day, and then run a full export in the evening when the network is quiet.

Modification Type:MinorLast Reviewed:1/25/2006
Keywords:kbinfo KB290390