[Webinar] Streamline your web hosting managementRegister Today

x
?
Solved

Getting Operation Failed: 80004005 trying to update RUS Enterprise Configuration

Posted on 2008-01-24
11
Medium Priority
?
582 Views
Last Modified: 2008-01-30
I am having an issue updating the config of my RUS Enterprise Configuration object in Exchange. I can change the Exchange server but not the Domain Controller. When I click the browse button, it appears to be trying, and then I get a popup message indicating Operation Failed. ID: 80004005. Now I have already read through MS article 821465 and everything appears to be OK as far as permissions and the serverReference attribute. One thing I will say is the DC its pointing to was dcpromo'd down to a member server a few days ago, but when we realized there was a dependency in Exchange, we promoted it back up to a DC so it should be back to where it was. Of course, I have no idea if this problem was there before the DC demotion because I never tried to update this particular RUS until now. Has this happened to anyone else. I am thinking maybe I need to reboot the Exchange server but I have 4. Since this is at the Org level, which one do I reboot. There is nothing in the Event logs and all the searchng I have done points back to the above MS article.
0
Comment
Question by:osiexchange
  • 7
  • 4
11 Comments
 
LVL 25

Expert Comment

by:kieran_b
ID: 20738183
Is that DC that you DCPromo'd also a GC now?
0
 

Author Comment

by:osiexchange
ID: 20739592
Yes. Its also a GC just like it was before.
0
 

Author Comment

by:osiexchange
ID: 20760106
OK. No response. So let me ask this. Is it possible to simply point the RUS to another DC using ADSIEdit.
I found an attribute on the RUS object called msExchServer1NetworkAddress that points to the current DC in our environment. It looks like all I need to  do is modify this to point to another DC. The object I am talking about can be found in ADSIEdit under Configuration > Services > Microsoft Exchange > Org name> Address List Container > Recipient Update Service > Recipient Update Service (Enterprise Configuration) If you look at the properties of this object, you will see the attribute I am talking about. Just wondered if thats all there is to it.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 

Author Comment

by:osiexchange
ID: 20760909
Does anyone know what this particular RUS does and how would I test it just to make sure its doing what its supposed to? I read a technet article about this and it said the Enterprise Configuration is responsible for updating the email address of the System Attendant and MTA but I am not sure what they mean by that.
0
 
LVL 25

Expert Comment

by:kieran_b
ID: 20762757
Sorry, this one slipped through the cracks;

This is an explanation of what the RUS does -> http://www.msexchange.org/articles/Troubleshooting-Exchange-Recipient-Update-Service-RUS.html

The best test is to create a user called "a test" and see if they are assigned an email address automatically (use a name that starts with A, it is alphabetical)

Modifying the RUS attributes with ADSIEdit is *probably* going to be unsupported, but I don't know.  Before you go down that path, I would be calling MS PSS and paying their fee - $400 for a question before doing it is better than x amount of hours of downtime.
0
 

Author Comment

by:osiexchange
ID: 20762791
I saw that article. I tested the modification in a VM environment with no issue, but maybe I should contact MS support. Because the DC in question is a VM, they may not be supportive however.
0
 

Author Comment

by:osiexchange
ID: 20762816
Also, I have several RUS components. One for each Domain and they work just fine populating email addresses they way they are supposed to. It appears the RUS for the Enterprise is also working because I turned up logging and there are no errors in the app log when I force an update, but the RUS for the enterprise I don't think has anything to do with user email addresses.
0
 
LVL 25

Expert Comment

by:kieran_b
ID: 20762863
OK good, if you are in a VM environment then your backup and recovery options are a little better - if you have tested it, and it works, then I would consider doing it, but I am a bit of a cowboy like that...

As for the Enterprise RUS - test that by creating a mail enabled public folder (and see if it gets an address).

http://support.microsoft.com/kb/822794
"The Enterprise RUS only stamps objects in the Configuration naming context, such as public folder stores and site replication services. The Enterprise RUS does not stamp objects such as users, groups, contacts, or public folders."
0
 

Author Comment

by:osiexchange
ID: 20762909
Thanks for this article. Have not seen this one before. A little confused with your last post. You said test by creating a mail enabled Public Folder, but then state the Enterprise RUS does not stamp Public Folders with email addresses.
0
 
LVL 25

Accepted Solution

by:
kieran_b earned 1500 total points
ID: 20762985
Lol, I can see how that was confusing - I misread the article :)

There is no real way of testing the Enterprise RUS Policy, unless you have the enterprise version of exchange and want to create a new PF store.
0
 

Author Comment

by:osiexchange
ID: 20763230
Well, I do have the Enterprise version and I have a DR server to play with. I can create another Public Folder Store on this server, but, what do I check for after creating it. There is no email addresses tab on the properties of the Public Folder Store.
0

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!

Question has a verified solution.

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

In this post, we will learn to set up the Group Naming policy and will see how it is going to impact the Display Name and the Email addresses of the Group.
After a recent Outlook migration from a 2007 to 2010 environment, some issues with Distribution List owners were realized. In this article, I explain how that was rectified.
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an anti-spam), the admin…
Suggested Courses

590 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