Recipient Update Services (RUS) pointing to offline Domain Controller
We are in the process of removing some old domain controllers. One of them had a hardware failure and was forced off the domain because is could not be demoted. Unfortunately, it was the one the Exchange was pointing to for RUS. Now, I am trying to point it to one of the two new domain controllers and it will not let me do the Enterprise one. When I try to browse, I immediately get the operation failed. ID no: 800004005 Exchange System Manager.Now, any of the changes we are making in AD are not showing up in the GAL Please help! You can reply directly to my work email address as well as the forum. djaquez at heihotels dot com. Thanks in advance!
March 10th, 2009 12:53am

Hi Which exchange version are you running..If it is exchange 2003 change dns servers to working domain controllers..make sure that server is Global Catalog.Exchange Server need to contact GL Server to update GAL, if it is not able to contact GL in the domain, GAL won't get updated.If it is exchange 2007, using management shell you can explicitly tell exchange server to use mentioned domain and global catalog server.Hope this helps....Abhishek
Free Windows Admin Tool Kit Click here and download it now
March 10th, 2009 9:55am

I am running Exchange 2003. All DNS settings are correct. I was able to change the domain level RUS but when I attempt to make the change to the enterprise one it fails with the mention error code.
March 10th, 2009 3:12pm

Hello Soulo,Looks like permission issue, do you have proper permission to change the properties of RUS? Check below article if it helps...You receive error ID 80004005 when you use Exchange System Manager to try to change the domain controller that is specified in the properties dialog box for the Recipient Update Service in Exchange 2000http://support.microsoft.com/kb/821465Amit Tank | MVP - Exchange | MCITP:EMA MCSA:M | http://ExchangeShare.WordPress.com
Free Windows Admin Tool Kit Click here and download it now
March 10th, 2009 4:08pm

Here's an update - I was able to make the change by forcing it in ADSI editor but I still get the error when I click on the browse for the server and I'm not sure the change took since I've forced an update and the GAL still looks the same. I am logged on as a domain admin so the permissions should be fine. Not sure where to go from there.
March 10th, 2009 5:01pm

OK, another update. Moved the Offline Address book settings and now the GAL is updating everywhere correctly. I am still getting the error when I try to browse for the proper server and I'm not sure if that is an underlying problem that will resurface later. Any ideas are appreciated. I'd like to get this cleaned up.
Free Windows Admin Tool Kit Click here and download it now
March 10th, 2009 6:04pm

Hi, Firstly, please let me know whether I understand the current situation correctly. If I am off base, please let me know. You are able to use Adsiedit.msc to modify the serverReference of all the DC servers according to KB821465. Nevertheless, when attempting to browse DC in Enterprise RUS, you are still receiving the 80004005 error. I suggest you ensure the serverReference attribute of all the DC servers have been configured correctly. In addition, please perform the following steps to troubleshoot the issue: 1. I suggest you user Adsiedit.msc tool to manually configure the Enterprise RUS to use a DC: a.Run Adsiedit.msc tool by connecting it to a DC b.Expand Configuration Container [Server_Name.Your_Domain.com] c.Expand CN=Configuration,DC=Domain d.Expand CN=Services e.Expand CN=Microsoft Exchange f.Expand CN=organization g.Expand CN=Address Lists Container h.Select CN=Recipient Update Services, on the right panel, please right click Recipient Update Service (Enterprise Configuration) and click Properties i.Please modify msExchServer1NetworkAddress attribute value to new DC which you would like to use by the Enterprise RUS. j. After that, please force AD replication and ensure no AD replication issue exists 2. If the 80004005 error still persists after the issue, I suggest you clear the original DC information: How to remove data in Active Directory after an unsuccessful domain controller demotion http://support.microsoft.com/kb/216498/en-us 3. I also suggest you run DCDiag /v /a and NetDiag /v to check the health of DC and connection to DC from the Client/Exchange which runs the ESM tool. Dcdiag Overview http://technet2.microsoft.com/WindowsServer/en/library/f7396ad6-0baa-4e66-8d18-17f83c5e4e6c1033.mspx?mfr=true Netdiag Overview http://technet2.microsoft.com/windowsserver/en/library/cf4926db-87ea-4f7a-9806-0b54e1c00a771033.mspx?mfr=true Mike
March 13th, 2009 9:47am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics