Active Directory cannot replicate the object to the Lotus Notes directory when you configure the Exchange Connector for Lotus Notes to use the "Immediate update" mode in the Exchange System Manager in Exchange 2000 Server or in Exchange Server 2003 (902459)
The information in this article applies to:
- Microsoft Exchange Server 2003 Standard Edition
- Microsoft Exchange Server 2003 Enterprise Edition
- Microsoft Exchange 2000 Server
- Microsoft Exchange 2000 Enterprise Server
SYMPTOMSConsider the following scenario:
- You have a server that is running IBM Lotus
Notes.
- You have a server that is running Microsoft Exchange Server
2003 or Microsoft Exchange 2000 Server.
- You install a new Microsoft Exchange Server server to point
to a different global catalog server.
- You migrate all the files to the same path of the new Exchange Server
server to the Conndata folder on the new Exchange Server server.
- Active Directory directory services replicates the object
to the Lotus Notes directory by using Microsoft Exchange Connector for Lotus
Notes.
In this scenario, Active Directory cannot replicate the object
to the Lotus Notes directory when you configure the Exchange Connector for Lotus Notes
to use the Immediate update mode in the Exchange System
Manager on an Exchange Server server. Additionally, if you change the
diagnostics logging level to the Maximum option, you may see
the following message in the connector logs under the
drive:\Program Files\Exchsrvr\Conndata folder.
Directory Synchronization Export is complete.
MS.DXAMEX successfully exported 0 entries, and had problems exporting 0
entries. However, Active Directory can replicate the object to
the Lotus Notes directory in the Immediate full reload mode on
the Exchange Connector for Lotus Notes. CAUSEThe local directory assigns the USN-Changed attribute for the latest change. In other words, the USN-Changed attribute is maintained by each global catalog server. When the
directory synchronization process checks for any changes from Active Directory,
the directory synchronization process compares the value of the USN-Changed attribute and the USN record in the Usn.tbl file.
If the value of
the USN-Changed attribute is higher, the directory synchronization process will synchronize the object of
the Active Directory. Otherwise, the directory synchronization process will not synchronize the object. Because
the USN record in the USN.tbl file is much higher than the value of the USN-Changed attribute, the directory synchronization process behaves as
if the object should not be updated.
In this scenario, the new
Exchange Server server and the original Exchange Server server are not using the same global catalog
server. Because all the files in the Conndata folder are copied from the original
Exchange Server server to the new Exchange Server server, the Usn.tbl file does not match the USN-Changed attribute of the current global catalog server. This behavior is the root cause of the issue. RESOLUTIONYou can manually change the number in the Usn.tbl file to
match the USN-Changed attribute of the current global catalog server. To do this, follow these
steps:
- Locate the Usn.tbl file in the
drive:\Program Files\Exchsrvr\Conndata folder on the
Exchange Server server.
- Change the value of the USN record in the Usn.tbl file to
0
- Save the value of the USN record that you changed in step 2, and then run the Immediate
update mode on the Exchange System Manager snap-in again.
Modification Type: | Major | Last Reviewed: | 4/10/2006 |
---|
Keywords: | kbprb KB902459 kbAudITPRO |
---|
|