Article ID: 306360 - Last Review: February 27, 2007 - Revision: 6.1 Event ID 8270, 1171, and 8146 error messages from Active Directory Connector and Site Replication ServiceThis article was previously published under Q306360 SYMPTOMS On an Exchange 2000 server that has joined an Exchange
Server 5.5 site, after you install or upgrade to the Active Directory Connector
(ADC) for Exchange 2000 Server Service Pack 1 (SP1), the following error
messages may be logged in the Exchange 2000 server's Application event log:
Event Type: Error Event Source: MSADC Event ID: 8270 Description: LDAP returned the error [10] No Such Attribute when importing the transaction dn: CN=Public Folders,CN=Microsoft Exchange,CN=Services,CN=Configuration,<domain name>; changetype: Modify msExchPfCreation: Event Type: Error Event Source: MSADC Event ID: 8270 Description: LDAP returned the error [10] No Such Attribute when importing the transaction dn: CN=Public Folders,CN=Microsoft Exchange,CN=Services,CN=Configuration,<domain name>; changetype: Modify msExchPfCreation: Event Type: Error Event Source: MSExchangeSRS Event ID: 1171 Description: Exception e0010006 has occurred with parameters 2 and 1 (internal ID 40406e4). Event Type: Error Event Source: MSADC Event Category: (1) Event ID: 8146 Date: 7/26/2001 Time: 5:09:35 PM User: N/A Computer: SRSSP00 Description: An operation on server 'SRSSP00' returned [0x2] Protocol Error. The Connection Agreement Config CA_SEGSP_SRSSP00 stopped. IMPORTANT: Even though the preceding event ID 8270, 1171, and 8146 error messages are logged in the Exchange 2000 server Application event log, no incorrect data is entered in Active Directory. No data is lost or corrupted. The only symptom that occurs is the logging of the event ID 8270, 1171, and 8146 error messages in the Exchange 2000 server Application event log. CAUSEThe issue is that the ADC is trying to add an empty
attribute to the Public Folder object. This causes LDAP to fail. This problem
can occur when all three of the following conditions exist:
RESOLUTION You can resolve this problem three ways:
STATUS
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.
MORE INFORMATION The ADC logs the error messages in the "Symptoms" section
of this article because the ADC cannot accurately replicate public folder
hierarchy information from the Exchange Server 5.5 Information Store Site
Configuration object to the Active Directory Public Folders object. The
attributes that specify who can and cannot create top-level public folders
cannot be mapped to Active Directory accounts unless a user Connection
Agreement has created those accounts in Active Directory. The ADC tries to add
an empty attribute to the Public Folders object. Because of this, Lightweight
Directory Access Protocol (LDAP) does not work, and the error messages in the
"Symptoms" section are logged. NOTE: The Exchange 2000 SP1 version of the ADC logs error messages more aggressively than the Exchange 2000 ADC. The underlying problem (adding an empty attribute to the Public Folders object when there is no recipient Connection Agreement) exists in the initial release (RTM) of the Exchange 2000 ADC, but an error message is not logged. To view the mailboxes and DLs that are explicitly allowed to create top-level public folders or explicitly not allowed to create top-level public folders on the Exchange Server 5.5 computer:
202265
(http://support.microsoft.com/kb/202265/
)
Unable to create top level folders in Exchange Server
For a mixed mode administrative group, Microsoft
recommends that you create a user Connection Agreement and allowing that
Connection Agreement to replicate fully before you install Exchange 2000. For
additional information about Exchange 2000 deployment, refer to the following
Microsoft Web site: http://technet.microsoft.com/en-us/exchange/default.aspx
(http://technet.microsoft.com/en-us/exchange/default.aspx)
| Article Translations
|
Back to the top
