Exchange 2003 generating event ID 8270 after remove and reinstall

Hi Experts,

I have two exchange servers, one is on the parent domain. The other is on the child domain. I uninstalled then reinstalled the Exchange Server on child domain. The exchange server on the child domain now generating the error message below in the event viewer every 5 mins. The exchange servers are able to send and receive email without any problems.

4/25/2005      8:22:01 PM      MSExchangeAL      Error      LDAP Operations       8270      N/A      MX1PH      "LDAP returned the error [32] Insufficient Rights when importing the transaction
dn: CN=Recipient Update Service (PH),CN=Recipient Update Services,CN=Address Lists Container,CN=XPERTALK,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=xpertalk,DC=com
changetype: Modify
msExchServer1LastUpdateTime:20050425122201.0Z
msExchServer1HighestUSN:82718
msExchReplicateNow:FALSE
msExchServer1HighestUSNVector:DC1PH:82718


I have checked the domain controllers and i dont see any error. I have also checked the exchange server on the parent domain and it is also clean. I have setup a test lab and have replicated the problem on the lab. On the lab i was able to resolve this by uninstalling exchange and demoting the domain controller for the child domain. After that I promotted it back to DC for the child domain and reinstalled exchange. I dont want to do this for our live network.

Please help.

Thanks
LVL 5
lapukmanAsked:
Who is Participating?
 
eatmeimadanishConnect With a Mentor Commented:
The problem seems to be stemming from the old Exchange server entries conflicting with the new Exchange server entried in AD.  
http://support.microsoft.com/default.aspx?scid=kb;en-us;254030

Is a step in the right direction.  You may need to manually remove the Exchange server entries in AD (ADSI Edit ) and reinstall exchange.  
0
 
lapukmanAuthor Commented:
Hi eatmeinadanish,

I tried the link above, and the error still pops up after reinstalling exchange. Have looked at other microsoft papers event ID 8270 , but almost all point to error 34.

Out of frustration we have just reinstalled the OS and Exchange from scratch. It is a crude solution but  everything is OK now.
0
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.