Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Exchange 5.5 MTA Major problem

Posted on 2006-11-02
5
Medium Priority
?
410 Views
Last Modified: 2008-01-09
I have 4 Exchange 5.5 servers, one main server that has the IMS installed.  Suddenly today the MTA on the main Exchange 5.5 server started failing.  The MTA service would stop.  I noticed its creating hundreds of .dat files of varying size, but when opening with notepad, they just have a solid black block at the top left corner.  They don't appear to be valid files.  This is our main server, incoming and outgoing mail is routed through this one server.  Its important I get it back online ASAP.  I've run the MTACHECK tool and it finds nothing wrong.  The MTA service will run but the MTADATA folder has over 10,000 files in it over 3GB of data.  Every time I start the MTA service, it creates hundreds of files per minute and is going nuts.  I'm down to 300MB of freespace on this machine.  Any ideas or suggestions?

This is a mixed org with Exchange 2003 and the ADC as well.  I've already checked internet connectivity and DNS confg.  Everything seems to be working fine, except for the MTA service.

thanks
JOe
0
Comment
Question by:MCPJoe
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
5 Comments
 
LVL 9

Author Comment

by:MCPJoe
ID: 17861234
Update: After a few reboots, disabling and re-enabling my AV software, and doing any little troubleshooting here and there I could think of; Exchange 5.5 is finally processing mail in the MTADATA Folder.  At last reboot I had 100MB of free disk space due to this issue.  I am now at almost 1GB of freespace, so I'm about 1/3 of the way back to normal.  The MTA seems to be processing mail now but slowly.  I'm afriad that when I re-enable mail flow from external incoming messages back to this server, we will run into the same issue again.  Seems that the issue was really only for internal mail, as I just sent a test from telnet through the failing server and received it very quickly at my mailbox on an Exchange 2003 server.  So the thousands of messages queued in the MTADATA folder are for internal mail?  How can that be?  Outgoing and incoming over SMTP seem to be ok, just need to make sure the MTA folder doesn't consume more disk space than it has available.  Its currently only on a 9GB partition, which should be enough, does anyone have any idea what would cause the MTA to generate so much internal activity?

I am going to recommend at this point, that we move remaining mailboxes on this box to one of the other Exchange 5.5 boxes, move public folders, etc, to another box as well.  We could also install a new IMC on one of the other Exchange 5.5 boxes and route all outgoing mail to one of the Exchange 2003 machines or directly to the internet.  We are urgently trying to migrate away from Exchange 5.5 as quickly as we can.  

Any tips on this process.  Especially for the following:

1. Remove IMC on failing Exchange 5.5 server
2. Install new IMC on either a different Exchange 5.5 machine or on one of the Exchange 2003 machines

Thanks
Joe
0
 
LVL 11

Expert Comment

by:NetoMeter Screencasts
ID: 17861331
DISCLAIMER From the Moderators: the links in this thread require a paid registration to view.

Hi!
I would suggest starting with reapplying SP4 for Exchange 5.5. There is a chance that this will fix your problem.
Here are examples (screencasts) of moving/restoring exchange 5.5 services to a different machine:
http://www.netometer.net/video/tutorials/move55/index.html

http://www.netometer.net/video/tutorials/replace55/index.html

http://www.netometer.net/video/tutorials/restore55/index.html

Dean



0
 
LVL 9

Author Comment

by:MCPJoe
ID: 17880956
UPDATE: The problem was not with the MTA itself, but rather a disk space issue.  Just before I experienced this problem, I had enabled a replica of one of the public folders on the server in question, to replicate to another server, running Exchange 2003.  Since Exchange 5.5 uses the X.400 connector over the MTA to transfer messages, even public folder replication, Exchange 5.5 had dumped thousands of files into the MTADATA folder.  Rather than stream the information real time to the new replica server, Exchange 5.5 dumped copies of each message into the MTA for transfer to Exchange 2003.  Since I only have 2GB or so of free space on this partition, and was transferring over 4GB of public folder data, needless to say this caused an issue.  Fortunately, at one point, we reached a critical point, Exchange 5.5 had sent enough public folder data so it would now leave 100MB free on the partition the MTA is on.  From there on, the free space started to increase, as Exchange 5.5 delivered the public folder data to exchange 2003.  The problem worked itself out and both systems are working normally.  I now know not to replicate public folders larger than a few GB from this server to another server without keeping a close eye on the MTA partition free space.  Whew!!!
0
 
LVL 1

Accepted Solution

by:
Computer101 earned 0 total points
ID: 18082128
PAQed with points refunded (500)

Computer101
EE Admin
0

Featured Post

On Demand Webinar: Networking for the Cloud Era

Ready to improve network connectivity? Watch this webinar to learn how SD-WANs and a one-click instant connect tool can boost provisions, deployment, and management of your cloud connection.

Question has a verified solution.

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

This article lists the top 5 free OST to PST Converter Tools. These tools save a lot of time for users when they want to convert OST to PST after their exchange server is no longer available or some other critical issue with exchange server or impor…
New style of hardware planning for Microsoft Exchange server.
how to add IIS SMTP to handle application/Scanner relays into office 365.
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 antispam), the admini…

670 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