Article ID: 842531
Article Last Modified on 5/21/2007
APPLIES TO
- Microsoft Identity Integration Server 2003 Enterprise Edition
Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
SUMMARY
Microsoft has released a cumulative hotfix package for Microsoft Identity Integration Server (MIIS). This article describes the following items about this hotfix package:
How to download the latest cumulative hotfix package
Prerequisites for applying this hotfix package
Whether you must restart your computer after you apply this hotfix package
The hotfix packages that this hotfix package replaces
INTRODUCTION
This article describes the Microsoft Identity Integration Server (MIIS) issues that are fixed in the latest MIIS hotfix rollup package. MIIS hotfix rollup packages are cumulative. Each build contains the hotfixes that are included with the earlier build. For example, build 3.1.1046.0 includes the hotfixes that are included in build 3.1.1042.0, 3.1.1036.0, 3.1.1030.0, 3.1.1026.0, 3.1.1020.0, in build 3.1.1016.0, and in release Service Pack 1 (SP1) (build 3.1.287.0).
Issues that the build 3.1.1046 hotfix package fixes
- After you apply cumulative update build 3.1.1036.0, password changes or password resets in Lotus Notes no longer function. This fix allows password changes to be successfully sent to Lotus Notes.
When you perform a Full Import in a SQL Server Management Agent-run profile step other than the first step, you may receive the following error message:
Event Type: Error
Event Source: MIIServer
Event Category: Server
Event ID: 6401
Date: 2/28/2006
Time: 12:19:09 PM
User: N/A
Computer: MIIS
Description: The management agent controller encountered an unexpected error. "ERR: MMS(2128): error.cpp(455): ErrorRecord: HResult: 0x80070057
Description: The parameter is incorrect. Source: Microsoft OLE DB Provider for SQL Server File: h:\nt\ds\mms\src\main\miis31_qfe\ma\oledb\import.cpp, Line: 2746
BAIL: MMS(2128): import.cpp(2746): 0x80070057 (The parameter is incorrect.)
BAIL: MMS(2128): import.cpp(1890): 0x80070057 (The parameter is incorrect.)
BAIL: MMS(2128): import.cpp(1116): 0x80070057 (The parameter is incorrect.)
ERR: MMS(2128): cntrler.cpp(2656): Unspecified MA error received: 80230808This issue may occur in the SQL Server management agent with certain run profiles. This fix corrects the issue.
- The CSEntry.ConnectionRule property may return "Unknown" or an error when it is referenced in the metaverse deletion rules or in the IMVSynchronization.ShouldDeleteFromMV method. This fix allows the CSEntry.ConnectionRule property to be called successfully from the ShouldDeleteFromMV method.
- The IBM Directory Server management agent cannot connect to IBM Directory Server when Anonymous access is disabled on IBM Directory Server. This change was made to enable the IBM Directory Server management agent to work in the best possible way when anonymous access is disabled on IBM Directory Server. The limitation of the fix is that SASL/Digest binding will not work if anonymous access is turned off. The following list includes background information:
- Bind functionality before this change: The IBM Directory Server management agent performs two anonymous reads before binding. The first read is to verify the vendor and the version of the LDAP server. The second read only occurs if digest binding is enabled and reads the realm value that is required to form the hash for the bind.
- Bind functionality after this change: When digest binding is not enabled, the first read occurs after the bind. The second read is not required at all. When digest binding is enabled, both reads still occur anonymously because the value are needed for authentication.
Issues that the build 3.1.1042 hotfix package fixes
The MIIS Key Management Utility (Miiskmu.exe) crashes on startup and generates the following event message:
Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 12/27/2005
Time: 11:59:44 AM
User: N/A
Computer: MIIS
Description: Application popup: miiskmu.exe - Common Language Runtime Debugging Services : Application has generated an exception that could not be handled.
Process id=0x8fc (2300), Thread id=0xf74 (3956).This issue may occur if some applications, such as antivirus software, are running. This fix corrects the issue and prevents the MIIS Key Management Utility from crashing.
- When a run profile has multiple steps, and each step has thousands of objects, the run histories take a long time to clear. This fix optimizes the "clear run history" query. Our testing has shown that this fix significantly improves performance.
- Consider the following scenario. You apply MIIS 2003 build 3.1.1036. Then, you run the Lotus Notes Management Agent (MA). In this scenario, reference values that are imported in non-canonicalized form are not imported correctly and remain unresolved placeholder objects. For example, group members that are not in "CN=
RefVal" format are not imported correctly. This fix restores the correct behavior. Reference values are correctly imported in both canonicalized form and non-canonicalized form. - This fix introduces the ability to specify a mail template file when you create a mail file during provisioning. To enable this functionality, we have added a new string attribute, _MMS_MailTemplateName, to the Lotus Notes MA schema. You can only set this attribute in the provisioning script. This attribute takes the name of an existing mail template file as its value. For example, this attribute may take the name mail50.ntf.
Notes- To use the _MMS_MailTemplateName attribute to set a mail template file, the template file must be located in the Domino\data directory. If the template file is located in a different directory, the export run fails, and you receive the following error message: This problem may occur even though the path specified in the provisioning script is actually relative to the Data directory.
- If an error occurs while an object is being created, and the mail template file has caused the error, the user object is created but the mail file is not created.
- IBM has added support for reparenting of leaf-node objects in their directory after you apply IBM Fix Pack 3 . We have also added support for importing and exporting such renames to leaf-node objects in this directory when supported by IBM.
- We have added support for the changelog format updates that were introduced by IBM Directory Server version 6.0.
- In Novell eDirectory, remote branches in the tree can run on a separate server and can use referrals from the main tree when MIIS searches for objects. Currently, if the query cannot connect to any one of the remote branch servers, the management agent (MA) stops processing the whole tree. This fix changes this behavior. The MA can continue to process the import against the tree. However, the MA logs the errors for the branches of the tree. Each container that has a search error is listed in the connection log. After the MA has tried to access all containers, the MA stops the search and returns a “stopped-connectivity” result to prevent unwanted obsoletion.
- When a Microsoft Active Directory Management Agent (ADMA) is configured to use partition-specific credentials, MIIS does not correctly parse and use the specified credentials when MIIS tries to contact a domain controller. In this configuration, when Microsoft Windows Management Instrumentation (WMI) makes a call to retrieve connector space object information by Account and by Domain, the lookup fails and not all WMI information is correctly filled in. This fix makes sure that MIIS uses the correct set of credentials for the partition.
Issues that the build 3.1.1036 hotfix package fixes
- Earlier versions of the Lotus Notes management agent use the document NoteID as the anchor attribute. However, the document NoteID is not unique across replica servers. Therefore, a Delete/Add operation occurs if the Lotus Notes management agent imports an object from a replica server other than the replica server from which the Lotus Notes management agent previously imported or from the replica server to which the Lotus Notes management agent previously exported. The fix changes the Lotus Notes management agent to use the document UNID as the anchor attribute. The document UNID is constant across all replica servers.
The fix does not support upgrading the connector space objects of an existing management agent to be UNID-based objects. However, existing management agent objects will continue to work correctly with their associated replica server. If you want the ability to fail over to replica servers, you must create a new management agent. For more information about how to build a management agent to replace the existing one, click the following article number to view the article in the Microsoft Knowledge Base:827117 How to build a new management agent to replace an existing management agent
- When the Lotus Notes management agent experiences a read error on an object, the management agent stops. When this problem occurs, you receive a "Stopped-Server" error message. This problem occurs if the Lotus Notes management agent encounters an entry that has a zero-length name field.
After you apply the fix, the management agent silently ignores the object. This behavior is the same as the behavior of the Lotus Notes client. The management agent will identify an object that has a zero-length name field and will not import the object. - The current implementation of the Lotus Notes management agent does not handle certain cases where the Lotus Notes client path value is added in the system path variable as a substring instead of as a path component. This behavior causes the management agent to set a path every time that the management agent runs. Eventually, the path value reaches the path size limit. When this problem occurs, the following error message is logged:
- When you use the Lotus Notes management agent to import groups that have memberships, the import operation takes longer than expected.
After you apply the fix, the performance of the import operation improves when you import group memberships. Individual management agent performance will vary. However, the performance improvement has been significant in our testing. - When the Lotus Notes management agent encounters data that contains duplicate attribute values, MIIS experiences a "Stopped-Server" error. This behavior is design. However, this behavior differs from the behavior of the Lotus Domino Administrator and of Lotus Notes. Lotus Domino Administrator and Lotus Notes are much less strict.
The original design implementation was to force critical errors in MIIS. This behavior caused the Lotus Notes management agent to clean up the data. If the management agent did not clean up the data, MIIS would treat the data as not valid. However, duplicates are allowed in Lotus Notes. This fix changes the way that MIIS treats this data. The new design implementation does not force critical errors.
The fix causes MIIS to treat duplicate attributes types as per-object read errors instead of as errors that cause "Stopped-Server" errors. - When you try to import the value of an attribute on the Corporate Hierarchy Information tab of a person document, and the attribute name contains a hyphen character (-), such as "Level6-2," the value is ignored. Therefore, the value is not imported into the connector space object. However, all other attribute values are imported as expected. In the management agent’s schema, the attribute names contain a hyphen character. But in the Lotus Notes directory, the corresponding field names contain an underscore character (_).
The fix corrects this issue by renaming the attributes in the management agent’s schema so that the attribute names match the corresponding field names in the Lotus Notes directory. - When you run the Lotus Notes management agent, and the Lotus Notes directory includes attributes values that contain certain characters, such as the pipe character (|), the Lotus Notes management agent generates a read error. This problem causes the Lotus Notes management agent to fail. When this problem occurs, the following error message is logged on the MIIS server: The fix causes MIIS to treat these read errors as per-object read errors instead of as errors that cause "Stopped-Server" errors.
- If the Lotus Notes management agent’s schema defines an attribute, such as the PasswordChangeInterval attribute, as Numeric, but the value appears in a Text field in the Lotus Notes directory, a "Stopped-MA" error may occur when you import the schema.
After you apply this fix, MIIS converts the Lotus Notes management agent’s schema definition from Text to Numeric when you import the schema. - The following error message is logged on the MIIS server when MIIS processes a password change notification:
This problem occurs when IIFP receives the new password. IIFP tries to look up the partition of the user object. However, the lookup operation fails. This problem typically occurs when placeholder objects appear in the connector space. These placeholder objects have the same anchor value as an incoming user object. This behavior causes MIIS to try to retrieve the domain context for the placeholder object. Therefore, MIIS returns the "Partition is NULL" error message.
Note Placeholder objects are special objects that IIFP uses only to reference other objects that IIFP will not own. You cannot use placeholder objects to synchronize password values.
This fix resolves this problem by causing MIIS to ignore the placeholder objects when MIIS processes password notifications.
- In MIIS 2003 Service Pack 1 (SP1), when you synchronize passwords for Novell eDirectory through the eDirectory management agent, the management agent uses the userPassword modify operation of the LDAP over SSL (LDAPS) protocol to set an eDirectory user’s password. The userPassword modify operation uses the credentials of the eDirectory management agent account, regardless of whether you use the Password Change Notification Service (PCNS) or the Password Management Web-based application.
However, the eDirectory management agent cannot set the PasswordExpirationTime and Grace Logins value for the user when the management agent resets the password. If the eDirectory password expiration policy is enabled, and you do not send the correct PasswordExpirationTime and Grace Logins values for the user, the passwordExpirationTime attribute value will always be some time in the year 1992. For example, the passwordExpirationTime attribute value may be 19920102000000Z. Therefore, the password is already expired when you set it.
This fix resolves this problem by making the following changes:- MIIS will set the passwordExpirationTime attribute value to the current time on the computer that is running MIIS. Additionally, MIIS will set the passwordExpirationInterval attribute value. However, MIIS will only set the passwordExpirationInterval attribute value if this attribute value is already set and the ForceChangeAtLogin attribute value is False or is not present in Microsoft Windows Management Instrumentation (WMI).
- MIIS will set the loginGraceRemaining attribute value to loginGraceLimit. However, MIIS will only set the loginGraceRemaining attribute value if this attribute value already set and the ForceChangeAtLogin attribute value is False or is not present in WMI. If the ForceChangeAtLogin attribute value is True, and if the Grace Logins option is enabled, the Grace Logins Remaining option will be set to 0.
- When you synchronize MIIS objects into the metaverse, an unexpected error message can be generated for an object during synchronization of the management agent. This problem may occur if a metaverse single-valued attribute lineage is present in the SQL Server database and the corresponding value column is set to a NULL value. When this problem occurs, the event log message may be different. However, the unexpected error message data will be similar to the following: After you apply this fix, the synchronization process will ignore the NULL attribute value until the import attribute flow tries to set that attribute. This behavior lets the synchronization process complete without generating an unexpected error message.
- MIIS may unexpectedly quit and may throw an application error message. This problem may occur if rules extensions try to access the LastContributingMA property and the management agent that is being accessed no longer exists in the system. When this problem occurs, the following error message may be logged in the Application log:
After you apply this fix, MIIS will not quit. However, because the operation is not valid, you receive the following error message:
The Lotus Notes management agent currently does not support provisioning of the AltFullName field for registered users.
This fix lets the Lotus Notes management agent provision the AltFullName field. However, because this fix requires changes to the schema, the new behavior only works on newly created management agents. Additionally, you cannot export the existing management agent and then import it again. You must re-create the management agent. For more information about how to re-create the management agent, click the following article number to view the article in the Microsoft Knowledge Base:827117 How to build a new management agent to replace an existing management agent
The lnschema.dsml file is the file contains the Lotus Notes schema. MIIS uses the lnschema.dsml file in the Lotus Notes management agent. This fix adds the following attributes to the lnschema.dsml file:
- _MMS_AltFullName
- This attribute is mandatory.
- The value of this attribute is only the name. Previously, this value used the full string.
- _MMS_AltFullNameLanguage
- This attribute is mandatory.
- The value of this attribute must match the language code that is registered in the Cert.id file that MIIS uses.
- _MMS_AltOU
- This attribute is optional.
- The value of this attribute is the OU value, without the "OU=" part of the code.
Note For these attributes to work correctly, the certifier ID that MIIS uses to create the user must be registered for the AltFullNameLanguage attribute and for the AltOU attribute that you are using. For more information about how to enable the AltFullName attribute, see the documentation for Lotus Notes.
The following code sample shows the added attributes that MIIS requires to provision the AltFullName field.//Try to provision the AltFullName field. //Replace the value with the data for the name in the alternate language. csentry["_MMS_AltFullName"].Value = mventry["sn"].Value + " " + mventry["givenName"].Value; csentry["_MMS_AltFullNameLanguage"].Value = "es"; csentry["_MMS_AltOU"].Value = "Spanish";
- _MMS_AltFullName
.
Issues that the build 3.1.1030 hotfix package fixes
- This fix extends the SetPassword WMI interface to accept two optional flags. The first flag requires that the user change the password at the next logon. The second flag unlocks the account if it is locked. If the flags are not specified, they use False, which is the current behavior. These changes affect only the Active Directory management agent. If any one of these flags are used for other management agents an option-not-supported message is returned by Windows Management Instrumentation (WMI).
boolean ForceChangeAtLogon
boolean UnlockAccount - The MIIS server would incorrectly report a "stopped-out-of-memory" error if a management agent was configured with a join rule that referenced a multi-valued metaverse attribute that contained hyphens in its name. With this fix, the MIIS server will now function correctly when it searches the metaverse using attributes that have hyphenated names.
- In order to successfully discover objects using the Lotus Notes management agent from a Lotus Notes server, both the Full Name and the objectType attributes must be present on the object. If either are missing, a discovery error will be generated. We had additional error details to provide the NotesID value for objects that had a missing ObjectType. However, for objects that had a missing Full Name we only generated a “DN Unavailable” error with no other details. We have now added additional error details to provide the NotesID for objects missing a Full Name.
- When writing updates to a DB2 table by using the DB2 management agent, with an anchor attribute that has Decimal or Numeric datatype, MIIS returns an error on each export object:
The problem was specific to how the DB2 database expects the format of the where cause. This fix changes the way we structure our where clause for the DB2 management agent for attributes of these datatypes.
Issues that the build 3.1.1026 hotfix package fixes
- When you run a full import with the management agent for Lotus Notes, certain placeholder objects return the following error message: This error creates a condition on the management agent to require a full run with a no-start-full-import-required message. Therefore, the customer cannot run a delta import. These placeholder objects are not considered to be real objects to MIIS because the placeholder objects must have a DN attribute and an Object Type attribute. Because the placeholder objects are not real objects, this hotfix will no longer treat the placeholder objects as errors. However, this hotfix does include the placeholder objects in the filtered object count. This hotfix also makes the delta import correctly work in the presence of these placeholder objects.
- Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.After you apply a SunOne update to the SunOne server so that the nsslapd-version in cn=config is no longer set to a supported directory string, both the created management agents and the existing management agents will not import. You receive an error message that states that the SunOne system is an unsupported version. MIIS SP1 currently supports SunOne 5.2 and expects the following version format:
Sun-ONE-Directory/5.2 B2003.143.0014
After you apply this hotfix, you can connect to the following version format:
Sun Java System Directory Server/5.2_Patch_3
Additionally, other update versions can be supported by making the following registry change:
- Click Start, click Run, type Regedt32, and then click OK.
- Locate the following registry key:
SYSTEM\CurrentControlSet\Services\miiserver\Parameters - Click New, and then click Multi-string Value.
Value name: iPlanetMASupportedServers
Value type: (REG_MULTI_SZ) - Set the value of the registry key to the following value:
Server/5.2_Patch_3 B2004.331.1125
- Restart the MIIS server and client.
- The Database (DB) management agent returns the following error message after you try to delete a reference attribute in the database: Examples of the DB management agent are the management agent for Microsoft SQL Server and the management agent for Oracle. This problem occurs when you update a reference attribute that has no values for an OLE DB management agent instance. The OLE DB management agent controller had erroneous logic that stripped out this attribute, thinking of this attribute as a transient DN attribute. However, this attribute is not a transient DN attribute. The result was that the management agent did not see the attribute change. Therefore, the management agent did not push out a change to the connected DB. On a subsequent import, the error message is returned. The hotfix stops the error message from occurring because an attribute that has no values cannot have a transient DN attribute.
- When you create a new LDIF management agent, the creation process does a sample sniff of the import file. Based on the first 100 objects of a file that is larger than 200 kilobyte (KB), this sniff detects the various object classes and attributes. In some larger configurations, this sniff is not sufficient to capture all the different object class value combinations. If this behavior occurs, the next run will fail with parsing errors. To resolve this issue, apply this hotfix, and then create an XML file to enable the customization of the sample batch size to be discovered. Name the XML file FileMAUIConfig.xml. The default value in the <analyze-limit> limit is 100. This value can be modified to account for a larger sample size.
To create the FileMAUIConfig.xml file, follow these steps:- Use Notepad to create a file that is named FileMAUIConfig.xml.
Paste the following contents in the file.
<file-ma-ui-config> <!-- Valid range of the analyze-limit: 1 to 2,147,483,647. Default analyze-limit is 100. --> <analyze-limit></analyze-limit> </file-ma-ui-config>Add the value that you want for the <analyze-limit> tag as in the following example.
<analyze-limit>500</analyze-limit>
- Save the file to the following directory:
%programfiles%\Microsoft Identity Integration Server\UIShell\XMLs
- The installation of MIIS now supports Microsoft SQL Server 2000 Service Pack 4 (SP4). Before this hotfix, the installation of later hotfixes or of the full version of MIIS was not successful, and you received the following error message: If you are installing MIIS for the first time by using SQL Server 2000 SP4, you must install a full version of MIIS SP1 with this hotfix. We are updating all the appropriate channels. If you have problems obtaining a full version through those channels, contact Microsoft Product Support Services for help.
back to top
Issues that the build 3.1.1020 hotfix package fixes
- When you are running a management agent in synchronization mode and you are processing group objects, you unexpectedly receive the following error message on a group object in the MIIS statistics pane:
Additionally, the following error messages will be displayed in the application event log on the MIIS server:
This problem occurs because reference attributes and renaming those reference attributes is mishandled. This hotfix improves this rename operation and helps avoid these error messages. - When an attribute is deleted during a delta import, the SunOne management agent does not discover the attribute deletion if the attribute deletion occurs when a replace operation is performed and no value is specified. This problem occurs with the way that the SunOne change log file is currently parsed. Any replace operation that has no value is ignored. This hotfix resolves this problem by changing the way that this particular condition is read from the changelog.
- This hotfix adds functionality to the SunOne management agent by enabling a registry key. The registry key is scoped to a particular management agent instance that is identified by name. If the registry key is set for a particular management agent, the import processing of the management agent will behave differently. With the new behavior, the management agent will still strip off suffixes from any attribute that it stages. Additionally, the management agent will also filter out any attribute that does not have a suffix that is equal to the value of the registry key. If the value of the registry key is the empty string, any attribute with any suffix is filtered out.
SunOne objects likely will have some attributes that have the option that you want and some attributes that have no option at all. If the user wants all attributes, they may have to create multiple management agents to pull in all data. For example, all attributes are suffix-less, except for "title", where each object has both "title;lang-eng" and "title;lang-fr". If the user must import both the suffix-less attributes and the English titles, they must create two management agents. The first management agent has the registry option set to the empty string to pull in all suffix-less attributes. The second management agent has the registry option set to "leng-eng" to pull in all attributes that have the suffix "lang-eng". Appropriate join and flow rules must be established to send the data from both management agents into the Metaverse.
To enable this functionality, you must follow these steps:- Apply this hotfix to the MIIS server.
- Add the following registry setting. The registry key to enable this behavior is located in a new parameter subkey that has been introduced to store per-management-agent-instance registry parameters. If the management agent name is "MyMA", the registry key would be the following:
Within this key, you must add a REG_SZ value that is named iPlanetMAOptionFiltering. This string value should be set to the suffix that you want. The string value should be set to the empty string if you want suffix-less attributes.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\miiserver\Parameters\PerMAInstance\MyMA
- Before this hotfix, the account joiner did not let you create "match" filters where both the CS and the MV attributes were multivalued. The account joiner did let you create filters where only one of the attributes was multivalued. After you apply this hotfix, combinations of attribute mappings that are based on multivalues versus single values are not blocked. However, some combinations are still blocked based on attribute type. Instead, a check is performed when you apply the filter and an error is reported if the CS attribute has more than one value. You experience the following behavior:
- Multivalued CS to Single-valued MV
If the CS attribute has more than one value, an error is reported. Otherwise, behavior is the same as the single-valued CS to single-valued MV case. - Multivalued CS to Multivalued MV
If the CS attribute has more than one value, an error is reported. Otherwise, behavior is the same as the single-valued CS to multivalued MV case.
- Multivalued CS to Single-valued MV
- This hotfix corrects an issue in multiple management agent types. This issue occurs when you select objects to process in the connected directory. The new selections may unintentionally cancel the objects that you had previously included.
- If "Full import" finishes with the status "completed-discovery-errors", a subsequent "Delta import" will stop with the status "No-start-full-import-required". This means that a delta import will not run until a "Full import" can run without generating this error message. This problem is caused by problems in the DN caching. This hotfix resolves the problem of a full import being required in this scenario.
- When the password management Web application initializes, it determines the list of systems on which the user can set passwords. The password management Web application does this by calling the GetServerStatus function. Before the Microsoft Exchange 5.5 export provider initializes the connection, the export provider detects that the object is a top level organization and returns an E_MMS_RUN_UNSPECIFIED_MA_ERROR error code. This behavior causes several error messages to appear in the event log. These errors are harmless. However, the error messages make MIIS management more difficult. This hotfix changes the return code to E_MMS_MA_EXPORT_READ_ONLY. Then, this return code is handled up the call stack so the errors are no longer thrown. When the GetServerStatus function is called, the result is that the server is down, and password management is disabled. From the point of view of the password management Web application, nothing has changed. From the point of view of the MIIS Administrator, two events are no longer generated every time that someone navigates to the password management Web page.
Issues that the build 3.1.1016 hotfix package fixes
- This hotfix enables the Lotus Notes management agent to provision certified person objects to AIX-based Domino servers.
- This hotfix enables the Notes management agent to set a mailbox quota in megabytes (MB) during provisioning.
- This hotfix enables the Lotus Notes management agent to set during provisioning an account lifetime value in days. When this value expires, the Lotus Notes ID file expires.
- This hotfix changes the way the Lotus Notes management agent processes objects that have non-unique native Notes hierarchical canonical names. These objects are named "conflict documents" and occur when you configure the Notes Address Book (NAB) to enable the Replication or Save Conflict Documents option. Previously, the Lotus Notes management agent flagged one of the duplicate objects as a transient. After you apply this hotfix, the management agent recognizes the duplication and skips all conflict documents. The management agent reports these conflict documents as duplicate object errors together with details that indicate that it is caused by a conflict with the Lotus Notes Distinguished name (DN). After the conflict is resolved, subsequent delta imports picks up the resolved changes.
- This hotfix enables certain distinguished name changes in imported objects to continue without error. Previously, some distinguished name changes would fail, you received the following error message:
- This hotfix corrects an issue in multiple management agent types. This issue occurred when you selected objects to process in the connected directory. The new selections might unintentionally cancel the objects that you had previously included.
- This hotfix now includes the following attributes:
- _MMS_UseAdminP
- _MMS_CertDaysToExpire
- _MMS_MailQuotaSizeLimit
- _MMS_MailQuotaWarningThreshold
- This hotfix expands the list of search operators that are available for Boolean attributes to include the following:
- Is present
- Is not present
- Is true
- Is false
- This hotfix changes the way the SunONE/IPlanet management agent reacts to incorrectly-encoded UTF-8 strings. After you apply this hotfix, the management agent reports an error when it encounters incorrectly-encoded data from IPlanet.
- This hotfix increases performance when large subtrees are deleted in the connector space.
- This hotfix addresses problems that are experienced by the Novell eDirectory management agent when anonymous access is disabled in the eDirectory server. When you apply this hotfix, the eDirectory management agent will now work with eDirectory servers where all anonymous access has been turned off as long as the Simple Authentication and Security Layer (SASL) option is not selected. If the SASL option is enabled, the management agent must continue to read the directoryTreeName attribute anonymously before binding to know what realm value to pass in during the bind.
- This hotfix corrects a problem where you cannot back up the system state when Password Change Notification Service (PCNS) is installed on a domain controller (DC). After you apply this hotfix, you can back up the system state successfully.
- This change removes support for the Lotus Notes 4.0 server and client from MIIS. This change follows IBM's deprecation of the Lotus Notes 4.0 server and client in 2004. The minimum Lotus client and Domino server version that is required for the Lotus Notes management agent is version 5.0.
For more information about the MIIS SP1, visit the following Microsoft Web site:
Download information
To obtain the hotfix package, visit the following Microsoft Download Center Web site:
Release Date: March 17, 2006
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
Note To verify that this hotfix package has been applied correctly, click Help, and then click About in MIIS. If this hotfix package has been applied correctly, the version number is 3.1.1042.0.
Prerequisites
When you apply this hotfix package, you are prompted for your MIIS 2003 installation media. Depending on how you originally installed MIIS 2003, insert the media in the See Comment or in the DVD drive, or specify a share location.
To apply this hotfix package, the currently logged-on user account must have the same SQL Server credentials as the account that was used to install the release version of MIIS 2003. Before you apply this hotfix package to your production environment, test this Service Pack in a Quality Assurance (QA) lab. Additionally, back up the MIIS 2003 SQL Server database and verify that you can fully recover your data from the backup version if this hotfix package does not apply correctly.
Restart information
Typically, you do not have to restart the server after you apply this Service Pack. However, the installer can determine whether you must restart the computer. If you must restart the computer, you are prompted to restart the computer. Frequently, you must restart the computer because the installer is trying to install a file that the computer is currently running.
Hotfix replacement information
This service pack replaces the following MIIS 2003 cumulative hotfix builds:
- SP1 (3.1.1036.0)
REFERENCES
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
Additional query words: MIIS setup SQL Server SP4
Keywords: kbqfe kbbug kbfix kbidintsvr2003entpresp1fix KB842531
