• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 298
  • Last Modified:

Exhange 5.5 - Cannot Join An Existing Site

I am trying to install a new Exchange 5.5 server on NT 4.0, to join an existing site.

During the setup, the directory replication process between the new server and the existing server failed, and the setup was interrupted and won't continue further.

The setup on screen error said:
<An internal error has occurred during directory replication. Stop then restart the directory service. Then try directory replication again. Microsoft Exchange Server setup. ID no: c1030b0d>

The NT Event Viewer error logs:

Source: MSExchangeDS
Category: Internal Processing
Event ID: 1171
<Exception e0010002 has occurred with parameters 9 and 0 (internal ID 30c0886). Contact Microsoft Technical Support for assistance.>

Source: MSExchangeSetup
Category: Replication Configuration
Event ID: 2013
<The error occurred adding replica of naming context '/o=ABC Pte Ltd /ou=CHICAGO /cn=Microsoft DMD' to server 'ServerB' from server 'ServerA'
0xc1030b0d - An internal error has occurred during directory replication. Stop and then restart the directory service. Then try directory replication again.>

My existing sever (ServerA) is running Exchnage 5.5 with service pack 4.

Please help.

  • 3
  • 3
1 Solution
I think you may have corruption in your directory database.

First make a good backup (you may need to take Exchange off line for this).

Verify your dir.edb (see the ESEUTIL for details).  IF corruption is found, make a copy of the dir.edb before attempting repairs.

Repeat the verify/repair cycle until you're clean.  Restart Exchange and attempt the addition of the new server again.

NOTE: I went thru this hell once and although the dir.edb came out clean, it contained an invalid back link that only MicroSquish could fix.  So I zipped and emailed the dir.edb to them and they sent it back repaired  (it cost me a per-call charge, but it worked).
peterhongAuthor Commented:
Is there any way without risking the database of my existing Exhange server.

I would not want to try anything disruptive to my existing Exchange server as it is my only production exchange server around.
It is working just fine for the time being. The availability of this server to the users is very critical.

Any suggestions or answers to my problem?
If there is corruption in your existing Exchanger server's directory database then you are already at risk.  You may be able to run like this for years and then BOOM - Exchange will stop running.

This verification should only take 15 minutes or so.  If repairs are needed, that should take an additional 15-20 minutes or so.

Remember the old computer/software maintenance adage:  Pay me now or pay me later.
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

peterhongAuthor Commented:
I have tried out the ESEUTIL tool, there is nothing wrong with my directory database, it is in consistent state.

Later, I tried out the AUTHREST on the existing server, using the command: authrest 1000 1000

But the new server installation still failed during the initial directory relication phase.

I am really running out of ideas on how to tackle this problem.
Suggest spending some dough and contact Microsoft Support (be sure to get the log number so you're not charged twice).

My DIR.EDB checked out fine too.  However, it did have a problem that Microsoft corrected and shipped back to me.
peterhongAuthor Commented:
Can anyone tell me if I am on the right track to solve this site joining problem by using the AUTHREST utility?

Seems that the problem still not solved with the authrest utility.
This question will be placed in PAQ, as it has been left without comment in quite a few months.

CS Amdin @ EE
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now