Microsoft KB Archive/296871

= ADC does not correctly replicate public folders with same name that contains trailing spaces =

Article ID: 296871

Article Last Modified on 2/20/2007

-

APPLIES TO


 * Microsoft Exchange 2000 Server Standard Edition

-



This article was previously published under Q296871





SYMPTOMS
When you use Microsoft Outlook 97, Microsoft Outlook 98, or Microsoft Outlook 2000 (but not Microsoft Outlook 2002 or the Microsoft Exchange Client version 5.0) to create public folders with names that are the same and that contain a trailing space, problems with Active Directory Connector (ADC) replication may occur. The replicated folders may contain a backslash character where the trailing space was located. For example, if you create the following public folders
 * Toplevel1\Second level\Deliverables
 * Toplevel2\Second level\Deliverables

after replication, only one folder is displayed in the Users and Computers snap-in:

Deliverables\

The following messages are also logged in the event logs:

Event 8021

Source MSADC

Category LDAP Operations

Description: LDAP Add on directory USBB-NADC1 for entry 'cn=R3 Deliverables\ -1,cn=Microsoft Exchange System Objects was unsuccessful with error:[0x40] Naming Violation [ 0000209E: UpdErr: DSID-030502FA, problem 6001 (NAME_VIOLATION), data 0 ].

Event 8270

Source MSADC

Category LDAP Operations

Description: LDAP returned the error [40] Naming Violation when importing the transaction dn: cn=R3 Deliverables\ -1,cn=Microsoft Exchange System Objects



CAUSE
This behavior occurs because Outlook 2000 and Outlook 98 allow for spaces at the end of folder name.



RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

301378 How to obtain the latest Exchange 2000 Server service pack

The English version of this fix should have the following file attributes or later:

Component: ADC



STATUS
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 2.

Additional query words: XCCC

Keywords: kbbug kbexchange2000presp2fix kbexchange2000sp2fix kbfix KB296871

-

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

© Microsoft Corporation. All rights reserved.