Exchange Transport Routing engine/service error

I get the following error every hour in my logs.

I have verified the current mail server is in the routing groups routing folder and is set as the master. That is the First administrative group, routing groups, first routing group and a members folder. My server name is mail and it is set as master.

I have also used ADSI to look at the lost and found container, Mail2 is not there. I also used the query function in ADSI to look for the information from the error, for computer names=mail2, exchange servers=mail2, containers=mail2 or queries for items starting with mail. All came up with nothing

In exchange system manager under administrative groups I also have Exchange administrative group, with a routing group, exchange routing group and a members folder. This members folder is empty, should it be? None of the information I have seen mentions two members folders.

Thanks for any ideas sent this way!

Event Type:      Warning
Event Source:      MSExchangeTransport
Event Category:      Routing Engine/Service
Event ID:      958
Date:            4/12/2010
Time:            6:12:34 AM
User:            N/A
Computer:      MAIL
Description:
Following master server DN appears to be pointing to a deleted object. This may prevent Exchange Routing Service from functioning properly. Please check your DS setting. <CN=MAIL2\0ADEL:e0885cf1-8c88-4400-9240-e77a2bdb41a9,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=BRSD,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=internal,DC=brsd,DC=org>
rmstewart70Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Shreedhar EtteCommented:
Hi,

Refer this article:
http://support.microsoft.com/kb/841666

Hope this helps,
Shree
0
Satya PathakLead Technical ConsultantCommented:
1. Go into ESM (Exchange System Manager).
2. Right click on the top-level node (org) and select properties.
3. In the dialog box, check "Display routing groups" and "Display administrative groups" (if they are not already checked).
4. If they were not already checked, you will be prompted that you have to restart ESM for the settings to take affect. Do so.
5. Click on Administrative Groups.
6. Click on First Administrative Group (or whatever you called it).
7. Click on Routing Groups.
8. Click on First Routing Group (or whatever you called it).
9. Click on Members.
10. The new machine will be listed (and the old one will not). Right click on the new machine and set it to be "master".
11. Restart the Exchange services on the new machine".

Sol2.
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_23229880.html
0
rmstewart70Author Commented:
No, been there done that a dozen times so far and each time the result is the same!

My understanding is (prior to me working here) A new 2008 Exchange server was brought on line, but it wasn't ever finished succesfully. That is where the mail2 name comes from. The current server, mail was the original server. Everything seems to be working fine except it logs these errors every hour. I am also concerned it may cause problems when I actually do migrate to a new exchange server this summer.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Shreedhar EtteCommented:
Hi,

Refer this article:
http://www.eggheadcafe.com/software/aspnet/32322114/removing-a-dead-exchange.aspx

Before making any changes perform backup of the Active Directory, by backing up the system state.

Hope this helps,
Shree
0
rmstewart70Author Commented:
Shree,
I have already tried the ADSIEDIT tool. However I have gone through the article you referenced and rechecked my steps, but unfortunately with the same results. However in researching further from the information you sent me, I have come up with the following observation and questions.
In an article on MSExchange.org (http://www.msexchange.org/tutorials/Remove-Exchange-server-entire-Exchange-organization.html) In one of the screen shots of Exchange Manager, I see in administrative groups, that there is only the First Administrative Group. In my Exchange Manager, I have the First Administrative Group and also have Exchange Administrative Group.

Using ADSIEDIT I right click on this group select properties, in the attribute editor I see createTimeStamp 7/28/2008. This date also shows up in whenCreated. In discussing with my coworker, it is about the time the other Exchange server (mail2) was put on line by an employee that is no longer here.

Using ADSIEDIT, I right click on First Administrative Group, select properties in the attribute editor I see createTimeStamp 12/28/2004. This date also shows up in whenCreated.

In Exchange Administrative Group/Routing Groups/Exchange Routing Group right click properties, in the attribute editor, I find Attribute=msExchRoutingMaster, Syntax=Distinguished Name, Value=CN=MAIL2\0ADEL:e0885cf1-8c88-4400-9240-e77a2bdb41a9,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=BRSD,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=internal,DC=brsd,DC=org. Mail2 being the offending server.

Looking for the same value of the First Administrative Group (the in use group) the value is CN=MAIL,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=BRSD,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=internal,DC=brsd,DC=org. This would be the correct value.

So long story short, could I delete the value or better yet delete the entire administrative group? It is the only reference to mail2 I have found to date.


Mike
0
Shreedhar EtteCommented:
Delete the Exchange Administrative Group. Restart the server.

However do backup the System State of the server for safer side.

This should fix the issue.

------------
Shree

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
rmstewart70Author Commented:
Shree,
Seems to have done the trick. Let me let it run over night and see what happens. Right now the errors have not shown for nearly three hours. The server is functioning as it should, maill is coming and going, in general life is good!
Mike
0
Shreedhar EtteCommented:
That's good
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

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.