Event ID 2937, 5015, 5016 - Referencing a decommissioned Exchange Server

Hey guys...

I am getting this warning and error messages in the event log. They are referencing a decommissioned Exchange 2007 server that was uninstalled a week ago.

The log says this for EVENT 2937:
   edgetransport.exe () 
   18964 
   [b][b][u]CN=Windows SBS Company Web Connector SERVER1[/u][/b][/b],CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=abbysonliving,DC=local 
   HomeMTA 
   abbysonliving.local/Configuration/Deleted Objects/Microsoft MTA DEL:888bbe54-dd5b-4b0b-b176-78925849b67b 

Open in new window


The bold underlined referenced to SERVER1 is the old SBS2008 server that was turned into a member server until we finish the data transfer. All of Exchange 2007 was removed and everything migrated to the new server correctly.

Now by researching on here I found that this may be due to the AdsiEdit having a reference in the connector group to the old server. This is what I found:

adsiedit.PNG
I should delete this reference in ADSI EDIT to fix this right?
Jonathan RoblesOwnerAsked:
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.

Rajitha ChimmaniCommented:
Yes, you can get rid of this entry (only if you are sure that the connector is not used anymore). But as only your server was migrated to new, this connector should be there somewhere.  Get-RoutingGroupConnector will give the list.

The safe way to get rid of this error is to change the homeMTA attribute to the new server. You can paste the distinguished name of new Exchange 2007 server here.
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
Jonathan RoblesOwnerAuthor Commented:
Thanks. I ran the command Get-RoutingGroupConnector and nothing was returned.
0
Rajitha ChimmaniCommented:
Then you can safely delete the AD entry. However, I suggest you to update the homeMTA and observe for couple of days.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Jonathan RoblesOwnerAuthor Commented:
Thank you. Do you have the correct procedure on how to do this? All of my research shows conflicting results.
0
Jonathan RoblesOwnerAuthor Commented:
To add, the homeMTA of all users is updated and pointing directly to the new Exchange 2010 server. I believe deleting this rogue entry should fix the issue.
0
Rajitha ChimmaniCommented:
Yes, you could do that as well.
0
Jonathan RoblesOwnerAuthor Commented:
Thanks!
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.