Article ID: 324413
Article Last Modified on 2/28/2007
APPLIES TO
- Microsoft Exchange 2000 Server Standard Edition
- Microsoft Exchange Server 5.5 Standard Edition
This article was previously published under Q324413
SYMPTOMS
When you install Exchange 2000 into an Exchange Server 5.5 site, an "Error code 0XC103798A" message may be logged. Specifically, the following data may be logged in the Exchange Server Setup Progress log:
[15:24:50] The command e:\setup\i386\exchange\adc -console -RO -CA "cn=Config CA_ ADC-RCA-NAME,cn=Active Directory Connections,cn=Microsoft Exchange,cn=Services,cn=Configuration,dc=svamain,dc=loc" -dc WIND2KDC -log 2 "C:\Active Directory Connector.Log" failed, returning error code -2147467259 (An unknown error has occurred.). ScCreateProcess (K:\admin\src\libs\exsetup\hiddenw1.cxx:1763)
Error code 0XC103798A (31114): An internal component has failed.
Additionally, the following data may be logged in the Active Directory Connector log:
[15:24:50] (2147491681) LDAP search result on directory WIN2KDC for entry 'cn= EXCHANGE55SERVERNAME,cn=Servers,ou=ORGNAME,o=SITENAME' was unsuccessful with error:[0x1] Operations Error. (Connection Agreement 'Config CA_ADC-RCA-NAME #308)*
[15:24:50] (3221233618) An operation on server 'WIN2KDC' returned [0x1] Operations Error. The Connection Agreement Config CA_ ADC-RCA-NAME stopped.*
[15:24:50] (1073749882) Stopped replication for Connection Agreement 'Config CA_ ADC-RCA-NAME.
This issue may also occur in a mixed Exchange 2000 and Exchange Server 5.5 environment. Config_CA may shut down and may not replicate any objects after a certain point. If you set logging to Maximum on Lightweight Directory Access Protocol (LDAP) operations on the Active Directory Connector (ADC), the following series of events are logged:
Event ID: 8033
Source: MSADC
Type: Warning
Category: LDAP Operations
LDAP search result on directory SAS0 for entry 'cn=INS4,cn=Servers,ou=CE,o=NOLTE' was unsuccessful with error:[0x1] Operations Error [ 000020D6: SvcErr: DSID-03100690, problem 5012 (DIR_ERROR), data 0 ]. (Connection Agreement 'Config CA_ ADCRCA-Name #1548)
Event ID: 8018
Source: MSADC
Type: Information
Category: LDAP Operations
Abandoning request '2475' on directory SAS0. (Connection Agreement 'Config CA_ADCRCA-Name #1548)
Event ID: 8146
Source: MSADC
Type: Error
Category: Replication
An operation on server 'SAS0' returned [0x1] Operations Error. 'Config CA_ ADCRCA-Name has stopped.
CAUSE
This issue may occur if Exchange 2000 cannot replicate Exchange Server directory objects to the Site Replication Service (SRS). In the scenario that is described in this article, the issue is caused by a specific object that is created by Praetor, an e-mail content security software program that is installed on the Exchange Server 5.5 server that you connected to for the Exchange 2000 installation. The Praetor software creates a Connector object in the Exchange Server Connections container that has an Active Directory Service Interface (ADSI) path that is not valid.
To view the object that causes the problem:
- Start Exchange Server in Raw mode, and then go to the site.
- Click Configuration Container, click Connections, and then click Praetor.
- Click File, and then click Raw Properties.
In the HOMEMDB attribute or the HOMEMTA attribute for the Praetor object, you see that the ADSI path is missing the CN=CONFIGURATION value. Because the ADSI path is not valid, Exchange Server cannot replicate the Praetor object to the SRS and the Exchange 2000 installation does not complete successfully.
WORKAROUND
WARNING: The procedure that is described in this section is recommended by Computer Mail Services, the publisher of Praetor. For information about how to contact Computer Mail Services, click the appropriate article number in the following list to view the article in the Microsoft Knowledge Base:
65416 Hardware and Software Third-Party Vendor Contact List, A-K
60781 Hardware and Software Third-Party Vendor Contact List, L-P
60782 Hardware and Software Third-Party Vendor Contact List, Q-Z
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
You do not have to use the Praetor connector if you want the Praetor software to run properly. You can safely delete the connector. After you do so, you can still use Praetor, but you must start the Praetor Administrator program either by using Control Panel or by using the Administrator program entry in the Start Menu program group.
How to Remove the Praetor Connector Object from the Connections Container
- Start the Microsoft Exchange Server Administrator program.
- Select the Praetor connector object in the Connections container, click Edit, and then click Delete.
If you cannot delete the Praetor object this way, you may have to delete it in Raw mode.
WARNING: If you use the raw mode of the Exchange Server Administrator program (admin /r) incorrectly, serious problems may occur that may require you to reinstall Microsoft Windows NT Server, Microsoft Exchange Server, or both. Microsoft cannot guarantee that problems that result from using raw mode incorrectly can be solved. Use raw mode at your own risk.
- Start the Microsoft Exchange Server Administrator program in Raw mode by typing the following command at a command prompt:
c:\exchsrvr\bin\admin /r
- Select the Connections container, click Edit, and then click Delete Raw Object.
NOTE: If you must move the Praetor software to a new server, you can save the rules that you have created. To do so, copy the Praetor.dat and PraetorScript.txt files from the EXCHSRVR\Connect\Praetor folder. After you install Praetor on the Exchange 2000 server, copy the two files into the Praetor folder that is located under C:\Program Files.
The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
Additional query words: PREATOR exch2kp2w
Keywords: kberrmsg kbprb KB324413
