Could not read the root entry on directory


I am receiving the error at the bottom in the Application log of my exchange server.

Here is some history on my environment:

HISTORY: About 6 months ago we had a 2000 domain with 2 domain controllers.  I will call them DC1 and DC2.  We also had 1 2000 exchange server (EX1). We upgraded DC1, DC2 and EX1 to 2003 server and Exchange 2003.

As part of the DC upgrade we used the 2003 rename tool to rename our first domain controller (DC1).  This machine held all of our FSMO roles.  After the rename we noticed some strange problems.  As a result we have built a new DC (DC3) and transferred all FSMO roles to that machine.  Everything appears to be working correctly with the new DC (DC3).  We have not yet run DCPROMO on DC1 to demote it.  We are planning on doing that soon.

Our current Exchange 2003 environment is configured with one front end server running OWA and 2 back end servers with mailboxes and public folders.

PROBLEM:  So the error message below indicates that Exchange cannot reach our original DC (DC1).  It has the FQDN of the DC before we used the rename tool to rename the system.  This name no longer appears in DNS or WINS, the new name of the system appears in both places.  The error below is being generated every 5 minutes.

REQUEST:  Does anyone know where this name may be coming from?  Any ideas on how to fix this issue?

Thank You,


Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      Service Control
Event ID:      8063
Date:            4/29/2005
Time:            3:13:42 AM
User:            N/A
Computer:      MAILKA
Could not read the root entry on directory <FQDN OF DC1 PRIOR TO UPGRADE>. Cannot access configuration information.  DC=<DOMAIN NAME>,DC=com

For more information, click

Who is Participating?
marc_nivensConnect With a Mentor Commented:
Yes, that should take care of the error.
Notice the event source is MSExchangeAL, that means the Recipient Update Service is generating this error.  Open Exchange System Manager, go to recipients, recipient update services.  Check the properties of each RUS and make sure none of them point to the old server.  If they do, change them.
brownmattcAuthor Commented:
I took a look and had two entries in there both refering to the old computer name.  I have changed these to our primary DC.  Is that correct and all I should need to do?
brownmattcAuthor Commented:
It has.  The error is no longer being logged.  Also my Outlook clients are no longer having issues reciving updated Address list information.  That is a very nice side effect of fixing this.

Thank You for your help,

Komal_UpadhyayCommented: is the only issue i found in my organization. MY DC no longer exists and my exchange server reports that old DC. I changed to new DC and waiting for result.
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.

All Courses

From novice to tech pro — start learning today.