Microsoft KB Archive/822581

= Setup error when you reinstall Exchange Server =

Article ID: 822581

Article Last Modified on 10/25/2007

-

APPLIES TO


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

-



Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
If you install Exchange Server on a computer where Exchange Server was previously installed and then removed, Setup may stop responding when it tries to create the Site Replication Service (SRS). Then, the following error is logged in the Setup.log file:

Error code 0XC1030B0C (2828): Le nom unique existe déjà. Recommencez l'opération. Si l'erreur persiste, essayez d'arrêter le service Annuaire et le programme Administrateur, puis relancez-les.

The following is an English translation of this error message:

Error code 0XC1030B0C (2828): The distinguished name already exists. Try the operation again. If the error recurs, try stopping the directory service and the Administrator program and then restarting them.



CAUSE
There are several potential causes for this problem. They are listed as follows:
 * This issue may occur if the SRSDATA folder is not deleted when Exchange Server is removed. When the Exchange Setup program reruns on the computer, it tries to replicate the naming context. However, the context already exists in the SRSDATA folder. This generates the error message that is mentioned in the &quot;Symptoms&quot; section.
 * This issue may occur if there were previous unsuccessful installations and the unsuccessful installation was not completely removed, or it was prevented from being completely removed.
 * This issue may occur if the Exchange 2000 computer appears in the directory on the Exchange Server 5.5 computer. If there is an Exchange 2000 computer object in the Exchange Server 5.5 directory, delete it.

Note If you delete the Exchange 2000 computer from the Exchange Server 5.5 directory, the unsuccessful installation may still not be completely removed if the Exchange Server 5.5 computer cannot run a Knowledge Consistency Check (KCC).
 * This issue may occur if the Exchange 2000 computer is a replication partner of the Exchange Server 5.5 computer. If there is no Exchange 2000 computer object in the Exchange Server 5.5 directory but the installation is still unsuccessful, verify that the Exchange 2000 computer is not a replication partner of the Exchange Server 5.5 computer.



WORKAROUND
To work around this problem, use one of the following methods:

Method 1
Manually remove the SRSDATA folder before you rerun Exchange Server Setup.

Method 2
Reinstall Exchange Server to a different folder than was used for the first installation.

Method 3
If you cannot run the KCC, follow these steps.

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.  Open the Exchange Server 5.5 Administrator program in raw mode. To do this, click Start, click Run, type :\exchsrvr\bin\admin.exe /r, and then press Enter.

In this command,  is the drive where Exchange is installed. For example, type c:\exchsrvr\bin\admin.exe /r . Click the Organization object, click File, and then click Raw Properties. In the List attributes of type list, click All. In the Object attributes pane, locate Reps-To and Reps-From. Examine the Attribute values of these objects.

If the Exchange 2000 computer is listed in either of these objects, you may be able to remove the objects by running a KCC. The Exchange Server 5.5 computer should periodically run the KCC to determine the state of the site and to validate known replication partners.

If you manually force KCC to run, the process may fail. Additionally, you may receive the following error message:

Error code 0Xc1030B0D (PID): An internal error has occurred during directory replication. Stop and then restart the directory service.

If you perform the recommended step of restarting the Directory Service, this may not resolve the issue. Quit Exchange Administrator. Open Registry Editor. To do this, click Start, click Run, type regedit, and then click OK. Locate and then click the following subkey:

 

</li> In this subkey, verify that the following values match their respective Exchange Server 5.5 directory names: <ul> Enterprise</li> Site</li> Server</li></ul>

Note These values may be different because of an improper rebuild of this server that occurred some time in the past. If the registry values are different, you must modify them to reflect the correct values.

Important Export the MSExchangeSA key before you make any changes.

Modify the Enterprise, Site, and Server values to reflect the corresponding names in the Exchange Server 5.5 directory. Stop and restart the System Attendant service and all other required Exchange Server 5.5 services.</li> If you have to, make sure that all the steps in the following Microsoft Knowledge Base articles have been followed to correctly remove an unsuccessful Exchange installation from Active Directory and from the computer where the installation attempt occurred:

273478 How to completely remove Exchange 2000 or Exchange 2003 from Active Directory

260378 How to manually remove an Exchange 2000 installation

After all traces of the unsuccessful installation of Exchange 2000 have been removed, rename the Exchange Server Setup Progress.log file, and then try to reinstall Exchange 2000.</li></ol>

<div class="status_section">

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

Additional query words: XADM

Keywords: kbnofix kbbug KB822581

-

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

© Microsoft Corporation. All rights reserved.