Microsoft Identity Integration Server 2003 Cumulative Hotfix Build 1010 (824338)

MORE INFORMATION

This update fixes the following issues:

• Exchange 5.5 Management Agents (MAs) Provisioned objects with commas are re-imported as a delete/add. The delete/add statistics appear in the Synchronization Statistics under Staging. When you click the link for the objects stage with a delete/add, a comma appears in the Distinguished Name.
• Typically, after you move an authoritative object outside the organizational units (OUs) that are configured for discovery, the object becomes obsolete. However, if you experience errors during the synchronization, MIIS does not trigger the obsolescence, and objects may remain in the metaverse. After you apply this update, the obsolescence is retained even if a failure occurs in the synchronization.
• Unexpected errors occur during an export of provisioned user objects into Active Directory when you set the initial passwords. When this problem occurs, you receive a corresponding event Log error message 6401 that contains the following error message in the event text: "Failed to get SamAccountName."
  This problem occurs because a domain controller other than the one where the user account was originally created replies when the CN lookup occurs before the user's password is set.
• You may receive unexpected error messages when you export a rename add on an object. In these cases, you receive an Event ID 6301 event message that contains the following text:The server encountered an unexpected error in the synchronization engine:
  DN mismatch for phantom export: row
  (DN=CN=User1,OU=TargetUsers,OU=BigEnterprise,DC=microsoft,DC=com), tower(old DN=CN=User2,OU=TargetUsers,OU=BigEnterprise,DC=microsoft,DC=com) The following error code appears in the event text:

  0x8023031c

  (The tower has a distinguished name that is different from that of the store.)
• Reference attributes, such as a manager attribute, are randomly missing during the Import staging of a file-based Management Agent. This behavior occurs because you receive an out-of-order import. The out-of-order import causes the staged delta to miss reference attributes that are in the import file.
• When a rename is imported on a connector space object with a delete-add in escrow, and there is a delete in unapplied, a staging error occurs. Additionally, you receive an event message in the program log that contains the following text and Error code 0x80230306: "E_MMS_ENTRY_ANCHOR_MISMATCH"
• You may receive a "Server Stopped" error message when provisioning group objects that use Auxiliary Object Class definitions. As a result, you receive the following Event ID: 6301 event message: The server encountered an unexpected error in the synchronization engine: (The parameter is incorrect.)
  " ERR: MMS(3260): expbase.cpp(1861): PutAnchorWithDnInternal failed on CS object {3A1BEB07-4023-442E-B14C-3CA66800534F} with 0x80070057.

This update makes the following product enhancements:

• Previously, Microsoft supported connecting to the following Netscape and Sun ONE Directories:
  • Sun ONE Directory Server 5.0 or 5.1 (formerly iPlanet Directory Server).
  • Sun ONE Directory Server 4.12 or 4.13.
  • Netscape Directory Server 4.1 or 6.01.
  This update adds support for Sun One 5.2 (formerly known as iPlanet Directory Server).
• This update also provides improvements in error reporting for connectivity issues that you experience with Microsoft Exchange 5.5 MAs. Previously, if you had a connection problem with the server during an import, you received an unexpected error message on each object. For example, you may have received a "Server 5.5 MAs are implicit" error message. Microsoft changed the retry logic to make sure that if there is a connectivity error, the export of objects to the directory stops. Microsoft also added code to make sure that per-object errors are stamped on the objects more specifically. For example, you receive "cd-connectivity-error" instead of "unexpected-failure".

Hotfix information

The issues that this article describes are fixed in the latest Microsoft Identity Integration Services 2003 cumulative hotfix package. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: