Solved

Cannot Decommission Exchange Server- Mail Queues Up

Posted on 2009-05-11
3
359 Views
Last Modified: 2013-11-30
Hello,
I created a new Exchange Administrative Group and server in order to fix a problem with outbound mail queuing up.  The whole scenario of that problem can be viewed at;
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_24366448.html

Ok, now I am at the point where I have created another new administrative group, which has only a single Exchange 2003 frontend server.  I want to use this as the server which sends and receives to/from the internet.  It is up and running.  However, I cannot get the special one I created first decommissioned.  I have tried everything I can think of..... whenever, I deleted the SMTP Internet Connector for that first server, mail starts queuing again.  I have deleted all the internet connectors and routing group connectors and tried numerous different things but nothing works.  Here is the basic topology of our exchange setup:

Exchange 2003 Administrative Group> Server #1 > Currently sending to internet...does not receive.  SMTP INTERNET CONNECTOR configured here.

Exchange (2003) Frontend Administratiive Group> Server #2> Currently receiving from internet...want to send, but cannot send.  SMTP INTERNET connector configure but does not get used.

Exchange 2007 Administrative Group> Server #3 > Does not send or receive internet mail

First Administrative Group> Server #4> primary Exhange 2003 server, receiving from internet

Have set up Routing Group Connectors from Server #4 (primary server) to Server #2 (frontend) and Server #1 (currnet sender).  When I delete Server #2 SMTP INTERNET connector, mail queus up on Server #4 (primary server).  Have tried routing group connectors to frontend server but mail still queues up.  

So, I need to wean us off of this special sending server (since it is an old PC) and get us sending thru our real frontend server, but cannot.  Can someone please help?  How exactly should the routing group connectors be set up?  How many? From each server to frontend?

Server 1,2 and 4 are running latest Windows 2003 server and Exchange 2003 software corrections.
0
Comment
Question by:rstuemke
  • 3
3 Comments
 

Author Comment

by:rstuemke
ID: 24356276
Correction...

Have set up Routing Group Connectors from Server #4 (primary server) to Server #2 (frontend) and Server #1 (currnet sender).  When I delete Server #1 SMTP INTERNET connector, mail queus up on Server #4 (primary server).  Have tried routing group connectors to frontend server but mail still queues up.  
0
 

Accepted Solution

by:
rstuemke earned 0 total points
ID: 24356970
Some additional information..... the frontend server is running Win2k3 R2.  Also, it is displaying this error message, which I have not been able to resolve:

Exchange detected that C.....\MAPI32DLL is not the correct version required to run Exchange System Manager of Exchange Server 2003.  This may cause failures.......

If this is causing the problem, how can I resolve it?  I reloaded Exchange 2003 SP1 and it did not correct the problem.  
0
 

Author Comment

by:rstuemke
ID: 24476011
Cancelled question due to lack of interest.
0

Featured Post

Why You Should Analyze Threat Actor TTPs

After years of analyzing threat actor behavior, it’s become clear that at any given time there are specific tactics, techniques, and procedures (TTPs) that are particularly prevalent. By analyzing and understanding these TTPs, you can dramatically enhance your security program.

Join & Write a Comment

Disabling the Directory Sync Service Account in Office 365 will stop directory synchronization from working.
Find out how to use Active Directory data for email signature management in Microsoft Exchange and Office 365.
In this video we show how to create an email address policy 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 Mail Flow…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

706 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

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now