[Last Call] Learn about multicloud storage options and how to improve your company's cloud strategy. Register Now

x
?
Solved

Exhange 5.5 - Cannot Join An Existing Site

Posted on 2002-04-23
7
Medium Priority
?
295 Views
Last Modified: 2012-06-21
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.



 
0
Comment
Question by:peterhong
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
7 Comments
 
LVL 4

Expert Comment

by:Nevaar
ID: 6966468
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).
0
 

Author Comment

by:peterhong
ID: 6976648
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?
0
 
LVL 4

Expert Comment

by:Nevaar
ID: 6976764
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.
0
Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

 

Author Comment

by:peterhong
ID: 6987658
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.
0
 
LVL 4

Expert Comment

by:Nevaar
ID: 6987663
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.
0
 

Author Comment

by:peterhong
ID: 6990760
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.
0
 

Accepted Solution

by:
ComTech earned 0 total points
ID: 7211260
This question will be placed in PAQ, as it has been left without comment in quite a few months.

Regards,
ComTech
CS Amdin @ EE
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article will help to fix the below error for MS Exchange server 2010 I. Out Of office not working II. Certificate error "name on the security certificate is invalid or does not match the name of the site" III. Make Internal URLs and External…
Know the reasons and solutions to move/import EDB to New Exchange Server. Also, find out how to recover an Exchange .edb file and to restore the file back.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…

650 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question