Microsoft KB Archive/928875

= The DirSync process is not completed, and a document is not imported into Active Directory in Exchange 2003 =

Article ID: 928875

Article Last Modified on 10/25/2007

-

APPLIES TO


 * Microsoft Exchange Server 2003 Standard Edition
 * Microsoft Exchange Server 2003 Enterprise Edition

-



SYMPTOMS
Consider the following scenario. You use the Microsoft Exchange Server 2003 Connector for Lotus Notes to connect a Lotus Notes organization and a Microsoft Exchange Server 2003 organization. You use Directory Synchronization (DirSync) services to fully reload a Notes-to-Exchange DirSync process. In the Notes &quot;Name and Address Book&quot; (NAB), a document has an object that does not contain the FullName attribute. In this scenario, you experience the following symptoms:
 * Symptom 1

The DirSync process is not completed. Additionally, the document is not imported into the Active Directory directory service.
 * Symptom 2
 * If an object contains the LastName attribute or the FirstName attribute, the attribute is not logged in the event log.
 * If an object does not contain the LastName attribute and the FirstName attribute, the ShortName attribute is not logged in the event log.
 * If an object does not contain the FullName attribute, the ShortName attribute, the FirstName attribute, or the LastName attribute, the Note-ID of the document is not logged in the event log.

Note An event will not be logged if an object in the document does not contain the FullName attribute.



CAUSE
These problems occur because of a problem in the Nnotes.dll file.



RESOLUTION
Note To work around the problem that is described in symptom 1 in the &quot;Symptoms&quot; section, see the &quot;Workaround&quot; section.

To resolve the problem that is described in symptom 2 in the &quot;Symptoms&quot; section, install the latest version of the Exchange Server 2003 Connector for Lotus Notes. To obtain the latest version of the Exchange Server 2003 Connector for Lotus Notes, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=5684160

This hotfix modifies the code that causes the problem. After you apply the hotfix, an event that resembles the following will be logged if an object in a document does not contain the FullName attribute: The User 'ID: ' has a blank FullName field. Therefore, the user will not be propagated.

You can easily locate the document that has this ID in the NAB.

Hotfix information
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Exchange 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites
Microsoft Exchange Server 2003 Service Pack 2 (SP2) and the Lotus Notes client version 6.5.4 or a later version of the Lotus Notes client must be installed before you apply this hotfix.

Restart requirement
You do not have to restart your computer after you apply this hotfix. However, if the Exchange Server 2003 Connector for Lotus Notes is running before you apply the hotfix, the Exchange Server 2003 Connector for Lotus Notes services will be restarted.

Hotfix replacement information
This hotfix replaces the Exchange Server 2003 Connector for Lotus Notes December 2006 updates and earlier updates.

File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.



WORKAROUND
To work around the problem that is described in symptom 1 in the &quot;Symptoms&quot; section, follow these steps:
 * 1) Use the method that is described in the &quot;Resolution&quot; section.
 * 2) Search for documents whose objects do not contain the FullName attribute, the ShortName attribute, the FirstName attribute, or the LastName attribute.
 * 3) Remove the documents as appropriate.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For more information about the terminology that is used to describe Microsoft software updates, 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

For more information about the naming schema for Exchange Server software updates, click the following article number to view the article in the Microsoft Knowledge Base:

817903 New naming schema for Exchange Server software update packages

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.

Keywords: kbexchcoexistmigration kbexpertiseinter kbqfe KB928875

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.