Microsoft Identity Integration Server 2003 Cumulative Update Build 1017 (828751)

MORE INFORMATION

This cumulative update fixes the following issues:

• When you run an Microsoft Exchange management agent (MA), it may stop while it imports objects from the connected directory. The problem occurs when it imports into connector space or drops a file and stops the run. When the problem occurs, you receive the following Event 6401 event message in the event log:Event ID: 6401
  The event text will include the following information:
  ERR: MMS(4764): cntrler.cpp(2532): Unspecified MA error received: 80230808
• LDIF and DSML file-based MA export attribute data with a "NULL" terminator at the end of strings. Some programs that use the exported files to update foreign directories process the "NULL" terminator. As a result, the data contains a trailing space. Because of this behavior, other directories where the data is imported may show an nonprintable character in the data. This fix removes the "NULL" terminator at the end of strings from the exported files that the LDIF file-based and the DSML file-based MAs produced.
• If you lose connectivity between an MIIS server that is running the Oracle MA and the Oracle database part way through the run, obsoletes may be processed incorrectly. The Oracle OLE database provider does not return an error when you lose the connection. Instead, it returns end-of-rowset. End-of-rowset leads to the subsequent obsolescence of previously existing connectors. This update adds additional processes to detect for lost network connectivity. If you lose a network connection, it immediately terminates the existing OLE database connection and then reconnects. If the reconnection succeeds, the import run succeeds. If the reconnection does not succeed, it returns a connectivity failure, and the MA stops and logs a connectivity failure.
• When you use the Exchange 5.5 MAs to stage an import into MIIS, you may generate a staging error. This problem occurs when there is a data flow operation that includes a delete-add that has a rename. When this problem occurs, you may receive the following Event 6301 event message in the event log:Event ID: 6301
  Description: The server encountered an unexpected error in the synchronization engine:
  "MMS(2440): SE: CS image begin........ "
• Microsoft improved the event logging for staging issues where the data is truncated in the event description.

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:

Prerequisites

When you apply this update, you are prompted for your MIIS 2003 media. You must have the software media in the CD-ROM drive or you must have a share location, depending on how you installed MIIS 2003.

To install the update, the currently logged-on user account should have the same SQL server credentials as the account installed the MIIS 2003 released version. Test in a lab before you apply the update to your production environment. Additionally, back up and verify the MIIS 2003 SQL database. As a result, you can fully recover your data if the update does not apply correctly.

Restart Requirement

Typically, you do not have to restart your server when you install this update. However, the installer can determine when the user must restart the local computer. If the user must restart the computer, the installer prompts the user to do so. Frequently, a user must restart the computer because the installer is trying to install a file that the computer is currently running.

Update Replacement Information

This update replaces MIIS 2003 Cumulative Update Build 1012 (3.0.1012.0).

For additional information MIIS 2003 Cumulative Build 1012, click the following article number to view the article in the Microsoft Knowledge Base:

Note To verify that this update has installed correctly, click Help, and then click About. If the update installed correctly, the version number reads "3.0.1017.0."