Release Notes for Microsoft® Identity Integration Server (MIIS) 2003 Service Pack 1 (SP1)

• Password synchronization—Synchronizes user password changes and password resets from Active Directory domain controllers to other connected data sources. Deployment of password synchronization includes installing the password change notification service (PCNS) and a password filter on each Active Directory domain controller. Password changes are encrypted and sent by using remote procedure call (RPC) to the server running MIIS 2003, which pushes them out to the appropriate management agents.
• Management agent for IBM DB2 Universal Database—This new management agent supports data synchronization with IBM DB2 Universal Database version 7 or 8.1 running on a Microsoft® Windows Server™ 2003 operating system, IBM DB2 Universal Database version 8.1 running on a Linux operating system, and IBM DB2 version 5.1.5 running on OS/400.
• Management agent for IBM Directory Server—This new management agent supports data synchronization with IBM Directory Server version 4.1, 5.1, or 5.2 running on a Windows Server 2003 or Windows 2000 Server operating system.
• Management agent for extensible connectivity, the management agent software development kit (SDK), and the management agent packaging tool—This management agent and related tools can be used to synchronize data from any connected data source. The management agent for extensible connectivity can support either file-based or call-based data sources. The management agent SDK is a set of tools, interfaces, Help, and sample code that is needed to develop a management agent for extensible connectivity. MApackager.exe is used to customize an exported extensible management agent and create an XML file that can be imported into MIIS 2003 with SP1 as a packaged management agent. Packaged management agents then appear in the drop-down list of available management agents in Identity Manager.
• Support for Microsoft SQL Server™  2000 Standard Edition—In addition to SQL Server 2000 Enterprise Edition, MIIS 2003 now supports SQL Server 2000 Standard Edition or Developer Edition for its data store.
• Multivalued attribute and multiple object type support for database management agents—Import and export objects with multivalued attributes with the management agents for Microsoft SQL Server, Oracle Database, and IBM DB2 Universal Database.
• Deletion threshold setting—During import, this setting prevents accidental deletions by stopping a management agent if the specified threshold limit is reached. During export, the management does not start if the number of pending exports exceeds the threshold limit. The deletion threshold is set in the run profile configuration.
• Password extensions for management agents—Password extension support for password management and synchronization has been added to the management agents for:
  • Attribute-value pair text files
  • Delimited text files
  • Directory Services Markup Language (DSML)
  • Extensible connectivity
  • Fixed-width text files
  • IBM DB2 Universal Database
  • IBM Directory Server
  • LDAP Data Interchange Format (LDIF)
  • Microsoft SQL Server 2000
  • Oracle Database
  When the password extension is enabled, you can use these management agents to call an extension to perform password operations.
• String normalization for file-based management agents and the management agent for extensible connectivity—MIIS 2003 with SP1 has the option to automatically normalize (that is, force to uppercase and/or remove accents) string values that are flowed into the connector space by using direct export attribute flow. A new managed API has been added so that attribute flow rules can also perform the same string transformations as part of either a declarative rule or a rules extension.
• Remote Procedure Call (RPC) dependency removed from management agent for Active Directory—The management agent for Active Directory no longer requires a range of RPC ports to be opened for synchronization. However, RPC ports are required if password synchronization is enabled.
• Management agent for Novell eDirectory now supports version 8.7.3
• Added support for Sun ONE Directory Server 5.2.

For product overviews, case studies, and other news about MIIS 2003 SP1, including newsgroup information, see the Microsoft Identity Integration Server 2003 Web site at http://go.microsoft.com/fwlink/?LinkId=6999. For the latest technical documentation, see Microsoft Identity Integration Server (MIIS) 2003 at the Microsoft Web site(http://www.microsoft.com/).

At the time of this release, the following are known issues.

Installation

• If you are installing a new build of MIIS 2003 and are using a existing MIIS 2003 database that has password synchronization enabled, the installation process will disable password synchronization. You must enable password synchronization again after installation is complete.
• If SQL Server 2000 is unavailable on the network during the installation of MIIS 2003, you may receive an error stating that you do not have the correct version of SQL Server 2000 installed. When troubleshooting this error, be sure to check for both the correct version of SQL Server 2000 and the network availability of the server hosting SQL Server 2000.
• During Setup, a security audit may be written to the Security log if the Integration Server service account is created with the default, or minimal, permissions. While this will not affect the functionality of MIIS 2003 SP1, you should review this security audit to ensure that it meets your network security requirements.
• If you make any changes to the MIIS 2003 service account, for example changing the account to a domain account, you will need to stop and start the MIIS 2003 service for the new credentials to take effect.
• MIIS 2003 does not support Domain local groups for the five default security groups. The groups must be local machine groups or global groups. If password synchronization is enabled, they must be global groups. The following correction should be noted in the Help topic "Using security groups":
  • All instances of "Domain local groups" should read "global groups".

Management agent for IBM DB2 Universal Database

• To use the management agent for IBM DB2 Universal Database, IBM DB2 Connect must be installed on a server that is running MIIS 2003. It is recommended that you use IBM DB2 Connect 8 with FixPak 3.
• If MIIS 2003 is connecting to a computer that is running IBM DB2 Universal Database version 7 on Windows or Unix, you must install IBM DB2 Connect 7 on the server that is running MIIS 2003 SP1.
• MIIS 2003 SP1 does not support the export or import of long string and binary attribute value data by using IBM DB2 Connect 7. You must upgrade to IBM DB2 Connect 8 if you need support for this functionality.
• The IBM DB2 Connect client sends passwords by using plaintext. Therefore, it is recommended that you install IBM DB2 Connect 8 with FixPak 3 on the server running MIIS 2003 SP1 by using the "Server Authentication" option instead of the "Client Authentication" option.
• To create a management agent for IBM DB2 Universal Database, the Identity Integration service account must have Full Control permission to the IBM DB2 folder, including its subfolders and files. Use the Properties dialog box of the IBM DB2 folder to grant permissions to the Identity Integration service account.
• If you are connecting to a database that is hosted on an IBM AS/400 computer, non-delimited column names can only contain uppercase characters, alphanumeric characters, and the characters @, #, $, and _. Column names that use any other characters may cause the management agent to fail to start.
• The IBM DB2 Connect client does not support installation on a Windows Server 2003 64-bit system. Therefore, MIIS 2003 SP1 does not support the management agent for IBM DB2 Universal Database on a Windows Server 2003 64-bit system.

Management agent for extensible connectivity

• When a management agent for extensible connectivity is configured to export through a drop file, it will be unable to write the anchor attribute back to the connector space.
• The ClassDescription class that was available in MIIS 2003 SP1 Beta 2 has been renamed to TypeDescription in MIIS 2003 SP1. As a result, DLL's using this class that were compiled and working correctly in Beta 2 will not work correctly in MIIS 2003 SP1, and will result in the error message "stopped-extension-dll-missing-dependency". To correct this scenario after installing MIIS 2003 SP1, you should edit and recompile all connected directory extensions that use this class.
• If you are configuring a management agent for extensible connectivity to use distinguished name as the anchor attribute, you must select the Use distinguished name as anchor attribute check box. Do not select distinguished name from the Available attributes list.
• Do not use the Set log file options when you are creating a run profile for a management agent for extensible connectivity.

Management agent for Lotus Notes

• Because password set operations cannot be written while the management agent for Lotus Notes is running, password set operations may fail during a long management agent run. This happens when a management agent run is longer than the password set retry time. If you encounter this problem, you will need to adjust the Maximum Retry Count and Retry Interval in the password synchronization target settings for the management agent. It is recommended that you adjust the Retry Interval first. Increasing the Maximum Retry Count will increase the size of your database over time, as retry information is stored for each object. If you do increase the Maximum Retry Count, be sure to clear the password history more frequently.

Global Address List Synchronization (GALSync) scenario

• Changes have been made for MIIS 2003 SP1 to the GALSync code installed with the product. To update your code:
  • If you have not modified the original GALSync code and recompiled it, copy the new source files from the SourceCode\GALSyncSP1 folder in the MIIS 2003 installation directory to the Extensions folder.
  • If you have modified the original GALSync code, you will need to compare your current code with the new files in the SourceCode\GALSyncSP1 folder, identify and incorporate the changes, and recompile.

Password Synchronization

• Two new password change notification service (PCNS) schema attributes have been added since MIIS 2003 SP1 Beta 3 was released. If password synchronization was enabled on MIIS 2003 SP1 Beta 3, you will need to extend the Active Directory schema before enabling password synchronization again.
• The password change notification service (PCNS) is only supported on Active Directory domain controllers that are running on x86-based or x64-based computers. PCNS is not supported on Itanium-based computers.
• If PCNS is installed on domain controllers in a different forest than the forest where MIIS 2003 is installed, there must be a 2-way trust set up between the forests in order for synchronization to complete successfully.
• SetSPN.exe, the tool used to set the service principal name (SPN) during password synchronization setup, cannot be used with the -D option to remove an SPN. To remove an SPN from the service account, use ldp.exe or ADSIEdit.exe, which are available in the Support Tools folder on the Windows Server 2003 Enterprise product CD.
• The following corrections should be noted in the Help topic "Pcnscfg: Password change notification service (PCNS) configuration utility":
  • The description of the /WL: parameter for pcnscfg addtarget and pcnscfg modifytarget should read as follows:
    
    "Logs a warning level when the number of objects in the queue reaches or exceeds nn. Must be an integer in the range from 0 to 4294967295. The default setting is 0, which disables the warning level."
  • The description of the /WI: parameter for pcnscfg addtarget and pcnscfg addtarget should read as follows:
    
    "The interval, in minutes, that the warning level is logged. This parameter has no effect if the /WL: parameter is not specified, or is set to 0. Must be an integer in the range from 0 to 4294967295. The default value for /WI: is 30. To disable periodic notifications, set the value to 0. When the value is set to 0, notifications will still be logged whenever the level threshold defined in /WL: is crossed, either up or down."

This service pack contains fixes for the following issues:

• The Oracle management agent may return a "success" message even though the management agent has not yet discovered all objects. This behavior may cause objects in the connector space to become obsolete incorrectly. This problem occurs if occasional problems are occurring at the Oracle end of the network. These occasional problems prevent the management agent from validating a bad connection.

  This service pack changes the way the management agent discovers objects by moving from a client cursor to a server cursor. This behavior appears to be more reliable because it minimizes the opportunity for network failure to occur and for Oracle not to report the failure. Additionally, after you install this service pack, the Oracle management agent counts rows to detect when MIIS 2003 does not have the full data set. This behavior is required because Oracle does not specifically return this information.

• When you use Identity Manager to import a server configuration that includes a management agent for Lotus Notes, and the management agent for Lotus Notes has extended attributes, the import process does not succeed, and you receive the following message:

  An error was encountered while trying to update the metaverse configurations. The import attribute flow rules XML defines an invalid/incomplete rule. Import attribute flow rules update FAILED.

  However, when you import an export of the same management agent, the import process succeeds.

  This service pack resolves the issue so that the server configuration can complete successfully.

• When you try to discover objects in a Lotus Notes database, you receive the following error message in Identity Manager:

  DN is unavailable : missing-object-class

  Additionally, the following error messages are logged in the application event log:

  Source: MIIServer
  Category: Server
  EventID=6401
  The management agent controller encountered an unexpected error.
  "ERR: MMS(448): libutils.cpp(8006): Unusual error code reported 0x80004005 Microsoft Identity Integration Server 3.0.1023.0"
  
  
  Source: MIIServer
  Category: Server
  EventID=6401
  The management agent controller encountered an unexpected error.
  "BAIL: MMS(448): import.cpp(325): 0x80004005 (Unspecified error) ERR: MMS(448): cntrler.cpp(2527):
  Invalid import error code received: 80004005 Microsoft Identity Integration Server 3.0.1023.0"
  
  

  This problem occurs when the run discovers data that is not valid from Lotus Notes.

  This service pack lets MIIS 2003 handle invalid data by logging an error for the objects that are not valid and allowing the run to continue to process data.
• When you try to create a new management agent for a computer that is running Sun ONE Directory Server 5.2, and the computer's data and schema settings have been migrated from iPlanet Directory Server 4.x, the connection to the Sun ONE Directory Server computer may not be successful. When this problem occurs, you may receive the following error message:
  
  Identity Manager: The management agent run was terminated as there were unspecified management agent errors.
  
  Note Sun ONE Directory Server 5.2 was formerly known as iPlanet Directory Server.
  
  This problem occurs when the Sun ONE Directory Server schema is changed from an iPlanet 4.x schema format to a Sun ONE Directory 5.2 schema format. This scenario creates an element that the MIIS 2003 schema parser cannot successfully parse.
  
  After you apply this service pack, the parser successfully reads the Sun ONE Directory Server 5.2 schema.
• Multiple management agents for Microsoft SQL Server or management agents for Oracle may be configured to run at the same time by using a script or by using the MASequencer.exe Resource Toolkit tool. In this scenario, you may receive an application fault, and the following event message may be logged in the application event log.
  
  Note You can run the management agents sequentially without experiencing any errors.
  
  Event Type: Error
  Event Source: MIIServer Event
  Category: Server
  Event ID: 6309
  Date: Date
  Time: Time
  User: N/A
  Computer: Server Name
  The server encountered an unexpected error while performing an operation for a management agent.
  BAIL: MMS(3352): config.cpp(886): 0x80004005 (Unspecified error)
  BAIL: MMS(3352): oledbclass.cpp(204): 0x80004005 (Unspecified error)
  BAIL: MMS(3352): cntrler.cpp(466): 0x80004005 (Unspecified error)
  BAIL: MMS(3352): ma.cpp(2680): 0x80004005 (Unspecified error)
  
  After you apply this service pack, you can run the multiple management agents at the same time.
• When you run a delta import against a computer that runs Sun ONE Directory Server, problems in the Sun ONE change log cause the management agent to return an exception. This problem may occur if the following conditions are true:
  • Sun ONE Directory Server writes out ADD entries to the change log.
  • The ADD entries specify the name of the attribute, but the ADD entries do not contain a corresponding value.
  When this problem occurs, the following event message may be logged:
  
  Event Type: Error
  Event Source: MIIServer
  Event Category: Server
  Event ID: 6401
  Date: Date
  Time: Time
  User: N/A
  Computer: Server Name
  Description: The management agent controller encountered an unexpected error.
  ERR: MMS(4276): ipmaimport.cpp(4560): Invalid changelog: attribute modification of employeeStatus does not match name of attribute replace
  BAIL: MMS(4276): ipmaimport.cpp(4563): 0x80070057 (The parameter is incorrect.)
  BAIL: MMS(4276): ipmaimport.cpp(3753): 0x80070057 (The parameter is incorrect.)
  
  After applying this service pack, the exception will not occur.
• With the management agent for Microsoft SQL Server 2000, when you import fields that contain more than 4,000 characters, you may receive the following error message in the Discovery Error section of the Management agent statistics pane:
  
  invalid-attribute-value
  Error Details: Import could not retrieve the attribute value from the database.
  
  After you apply this service pack, you can import fields that contain more than 4,000 characters.
  
• You may receive staging errors that report duplicate objects on uniquely imported objects. If you receive more than 5,000 of these errors, the run stops because the error limit is reached. This problem may occur in the following management agents:
  • Microsoft SQL Server
  • Microsoft Windows NT 4.0
  • All file-based management agents
  After you apply this service pack, these staging errors no longer occur.
• When MIIS 2003 tries to disconnect and to reprovision the same object during the same synchronization run, you may receive an "extension DLL exception" error message in the Flow Errors section of the management agent run profile type statistics. You may also receive an "object already exists" error message in the synchronization error information for the object.
  
  After you apply this service pack, these objects will not appear as a pre-existing object.
• When you run a delta synchronization or a full synchronization, the provisioning rules may delete an object and then add the object back. You may receive an "unexpected error" error message in the Flow Errors section of the Operational Statics pane. The following event message may also be logged in the Application log:
  
  Event Type: Error
  Event Source: MIIServer
  Event Category: Server
  Event ID: 6301
  Date: Date
  Time: Time
  User: N/A
  Computer: Server Name
  Description: The server encountered an unexpected error in the synchronization engine: "MMS(3932): Pre: HRESULT: 0x0<entry dn="CN=dlobject,OU=groups,OU=test,DC=Fabrikam,DC=com">
  
  If a preview is generated on the object, you may receive the following error message:
  
  "The dimage has an anchor that is different than the image".
  
  After you apply this service pack, you no longer receive this error message. However, it is a good idea to verify that the delete-add operation that occurs during the provision is expected behavior for the scenario. If it is not expected behavior, evaluate the provisioning logic.
• Earlier versions of MIIS 2003 support connections to Novell eDirectory versions 8.6.2 and 8.7. This service pack extends the support to include connections to Novell eDirectory version 8.7.3
• MIIS 2003 stops responding while running a delta import. The management agent appears to stop responding, and then the following error message is logged in the Application log:
  
  Application popup: miiserver.exe - Application Error : The instruction at 0x01076f77 referenced memory at 0x00000000. The memory could not be read.
  
  This event is logged because an exception error occurs while the management agent is running in Delta mode.
  
  This service pack prevents this exception error.
• Objects become corrupted in the connector space, and errors are returned when MIIS 2003 runs the management agent. The following event is logged when the following conditions are true:
  • You run MIIS 2003 to synchronize any management agent that modifies a metaverse object.
  • That metaverse object is joined to a connector space object that has become corrupted.
  Note This corruption occurs because the tower has a distinguished name (DN) that is different from the name of the Microsoft SQL Server store. (A tower is also known as a hologram.)
  
  Event Type: Error
  Event Source: MIIServer
  Event Category: Server
  Event ID: 6312
  Date: Date
  Time: Time
  User: N/A
  Computer: Server Name
  Description: The server encountered an unexpected error while performing an operation for a rules extension.
  ERR: MMS(3576): tower.cpp(521): DN mismatch for phantom export: row (DN=CN=Mike Smith (Central Financial Services),OU=Disabled Users,OU=MIIS,DC=Fabrikam,DC=com), tower(old DN=CN=Mike Smith,OU=Disabled Users,OU=MIIS,DC=Fabrikam,DC=com)
  BAIL: MMS(3576): tower.cpp(522): 0x8023031c (The tower has a distinguished name that is different from that of the store.)
  
  When you process an Export run profile to export objects to the connected directory, the following event message may be logged if the objects have become corrupted:
  
  Event Type: Error
  Event Source: MIIServer
  Event Category: Server
  Event ID: 6301
  Date: Date
  Time: Time
  User: N/A
  Computer: Server Name
  Description: The server encountered an unexpected error in the synchronization engine:
  BAIL: MMS(3576): scripthost.cpp(10075): 0x80230703 (The extension threw an exception.) Microsoft.MetadirectoryServices.Impl.InternalError: 0x8023031c at Microsoft.MetadirectoryServices.Impl.ScriptHost.ThrowExceptionFromHRESULT(Int32 hr)
  
  This service pack prevents the DNs of the tower and of the store from becoming different, and this behavior in turn prevents this type of corruption of the connector space objects. However, existing corrupted objects in the connector space are not changed. This service pack only prevents existing objects from becoming corrupted. Therefore, you must delete the connector space under that management agent. In many cases, it is faster to rebuild the existing management agents by renaming the existing management agent and then creating a new management agent. If the management agent has many connectors under it, you may want to just rename the management agent and wait to delete it on the weekend or at a specific scheduled downtime. For additional information about how to build a new management agent to replace the existing management agent, see the following article in the Microsoft Knowledge Base:
  
  827117 How to build a new management agent to replace an existing management agent
• When you run a management agent for Microsoft Exchange Server 5.5, the management agent may stop while it is importing objects from the connected directory. This problem occurs when the management agent for Microsoft Exchange Server 5.5 imports objects into the connector space or drops a file and stops the run. When this problem occurs, the following event message is logged in the event log:
  
  Event ID: 6401
  
  The event message includes the following information:
  
  ERR: MMS(4764): cntrler.cpp(2532): Unspecified management agent error received: 80230808 - LDIF and DSML file-based management agent export attribute data with a NULL terminator at the end of strings.
  
  Some programs that use the exported files to update directories on other servers process the NULL terminator. When this behavior occurs, the data contains a trailing space. This behavior may cause a character that cannot be printed to appear in the data of the directories that use the exported files.
  
  This service pack removes the NULL terminator at the end of strings in the exported files that the LDIF file-based management agents and the DSML file-based management agents produce.
• If you are running a management agent for Oracle and lose connectivity between the server running MIIS 2003 and the Oracle database during the run, obsolete connectors may be processed incorrectly. The Oracle OLE database provider does not return an error when you lose the connection. Instead, it returns an "end-of-rowset" message. Because the Oracle OLE database provider returns an "end-of-rowset" message, previously existing connectors become obsolete.
  
  This service pack adds processes that detect lost network connectivity. If you lose a network connection, the existing Oracle OLE database connection is immediately terminated and then reconnected. If the reconnection succeeds, the import run succeeds. If the reconnection does not succeed, the management agent returns a connectivity failure, and then the management agent stops and logs a connectivity failure.
• When you use a management agent for Microsoft Exchange Server 5.5 to stage an import in MIIS 2003, you may experience a staging error. This problem occurs if a data flow operation exists, and that data flow operation includes a delete-add operation that has a rename operation. When this problem occurs, the following event message may be logged in the event log:
  
  Event ID: 6301
  Description: The server encountered an unexpected error in the synchronization engine: "MMS(2440): SE: CS image begin........ "
  
  This service pack no longer truncates event logging for staging issues.
• When you attempt to create a management agent for Microsoft Exchange Server 5.5, you may receive the following error message if the organization name or the site name for the computer that is running Microsoft Exchange Server 5.5 contains an ampersand character (&):
  
  An error occurred while parsing EntityName. Line x, position y.
  
  Note In this error message, x and y are numeric values.
  
  For example, you experience this problem if the name is "o=CompanyA & Co."
  
  After applying the service pack, the & character will be processed without errors.
• When you attempt to create a management agent for Active Directory Global Address List (GAL), and you try to use a DN that contains an ampersand character (&) to set the destination container for the contacts, you may be unable to save the management agent. For example, you try to use the following:
  
  OU=Contacts & Things,DC=Fabrikam,DC=com
  
  When you do this, you can complete the management agent configuration. However, when you click Finish, nothing occurs, and you cannot create the management agent.
  
  After applying the service pack, the & character will be processed without errors.
• When you try to modify a management agent for Active Directory Global Address List (GAL) by changing the DN of the destination container to a DN that contains an ampersand character (&), such as "OU=Contacts & Things,DC=Fabrikam,DC=com," you may receive the following error message after you click OK in the Management Agent Designer properties dialog box:
  
  An unhandled exception has occurred in your application.
  If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will be shut down immediately.
  An error occurred while parsing EntityName. Line x, position y.
  
  Note In this error message, x and y are numeric values.
  
  After applying the service pack, the & character will be processed without errors.
• A an object provisioned by a management agent for Microsoft Exchange Server 5.5 that contains a comma is imported again as a delete-add operation. The delete-add statistics appear under Staging in the Synchronization Statistics section. When you click the link for the objects that are staged with a delete-add operation, a comma appears in the DN.
  
  After you apply this service pack, the comma will not appear in the DN.
• 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 2003 does not trigger the obsolescence, and objects may remain in the metaverse.
  
  After you apply this service pack, the obsolescence is retained even if a failure occurs in the synchronization.
• Unexpected errors occur during an export of provisioned user objects in Active Directory when you set the initial passwords. When this problem occurs, a 6401 error message is logged in the event log. This message includes the following 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.
  
  After applying the service pack, provisioned user objects will be processed without errors.
• You may receive unexpected error messages when you export a rename add operation on an object. When this problem occurs, you receive an 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=Enterprise,DC=Fabrikam,DC=com), tower(old DN=CN=User2,OU=TargetUsers,OU=Enterprise,DC=Fabrikam,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.)
  
  After applying the service pack, rename add operations will be processed without errors.
• 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 (that is, the change) to miss reference attributes that are in the import file.
  
  After applying the service pack, out-of-order imports will be processed without errors.
• When you import a rename operation on a connector space object, and the connector space object has a delete-add operation in escrow in an unapplied state, a staging error occurs. Additionally, an event message is logged in the Application log. The event message contains the following text and error code 0x80230306:
  
  E_MMS_ENTRY_ANCHOR_MISMATCH
  
  After applying the service pack, rename operations will be processed without errors.
• You may receive a "server stopped" error message when you are provisioning group objects that use Auxiliary Object Class definitions. When this problem occurs, you receive the following 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.
  
  After applying the service pack, provisioning group objects will be processed without errors.
• This service pack provides improvements in error reporting for connectivity issues that you experience when you use a management agent for Microsoft Exchange Server 5.5. In earlier versions, if you have a connection problem with the server during an import, you receive an unexpected error message on each object. For example, you receive a "Server 5.5 management agents are implicit" error message.
  
  The retry logic has been changed to make sure that the export of objects to the directory stops if a connectivity error occurs. Code has also been added to make sure that per-object errors are stamped on the objects more specifically. For example, after you install this service pack, you receive a "cd-connectivity-error" error message instead of an "unexpected-failure" error message.

© 2004 Microsoft Corporation. All rights reserved.

Microsoft, MS-DOS, Windows, Windows NT, and Visual Studio are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.