Solved

Exchange transport error - pointing to deleted server

Posted on 2013-01-22
4
585 Views
Last Modified: 2013-01-24
We recently got rid of an old Exchange (2003) server which was hosed.  There was a routing group set up between the old Exchange server and the other Exchange 2003 server in our organization.  I now see the following error in the Event Log of the Exchange server

Event Type:      Warning
Event Source:      MSExchangeTransport
Event Category:      Routing Engine/Service
Event ID:      958
Date:            1/22/2013
Time:            8:01:37 AM
User:            N/A
Computer:      Current Exchange Server
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=Old Exchange Server\0ADEL:ffcc9621-042d-4dd0-918c-a83f9c9f78d8,CN=Servers,CN=DOMAIN,CN=Administrative Groups,CN=Organization name,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=mydomain,DC=com>

How do I delete the object referenced above so that this error goes away?

Thanks!
0
Comment
Question by:jmerulla
  • 2
  • 2
4 Comments
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 38807488
Do you have any routing group connectors in place?

get-routinggroupconnector

Was the Exchange 2003 server removed correctly? The installer shouldn't have let you uninstall with routing information in place.

Simon.
0
 
LVL 2

Author Comment

by:jmerulla
ID: 38809784
We have routing group connectors in place.  The Exchange 2003 server was not removed correctly because the server died so there was no way to uninstall.
0
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
ID: 38812613
You need to remove the routing group connectors.

get-routinggroupconnector | remove-routinggroupconnector

As that is the cause of some of the problems. Have you done any cleanup of the Exchange environment to account for the removal of the server? One option if nothing has been done would be to recover the Exchange 2003 server (using a new installation of Windows) so the migration can be completed correctly.

Simon.
0
 
LVL 2

Author Comment

by:jmerulla
ID: 38815374
I've removed the connectors using the command you listed above.  Error messages have disappeared.

Thanks!
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

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

This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
Read this checklist to learn more about the 15 things you should never include in an email signature.
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…

679 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