Hi matheson
Do you have at 10MB of free space or more? If not, the MTA shuts itself down automatically.
Main Topics
Browse All TopicsHey all, here's my config....
Windows 2003 enterprise - Exchange 2003 enterprise,
2003 ad domain connected to an NT4 domain...
My installs of Exchange 2003 and ADC worked grand but the Mta stack service won't start on any of my exchange 2003 servers?
When i try to manually start it is says it started but stopped again because it was not doing anything...
Here are the errors in from the event log:
Product: Exchange
ID: 9405
Source: MSExchangeMTA
Version: 6.0
Component: Message Transfer Agent
Symbolic Name: MTA09405
Message: An unexpected error has occurred which may cause the MTA to terminate. Error: {error code}. [{value}{value}{value}] (16)
roduct: Exchange
ID: 137
Source: MSExchangeMTA
Version: 6.5.0000.0
Message: A fatal directory error occurred. Change to the maximum logging level for more details. [valuevaluevaluevalue] (16)
Product: Exchange
ID: 9406
Source: MSExchangeMTA
Version: 6.0
Component: Message Transfer Agent
Symbolic Name: MTA09406
Message: There is not enough Performance Monitor memory to display the MTA Connections information. Stop attached Performance Monitors and re-start the MTA. [{value}{value}{value}] (14)
Any help would be extreemly appreciated as i cannot find any documents relating to this.
Thanks,
Matt
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
A fatal directory error occurred. Change to the maximum logging level for more details. [MTA MAIN BASE 1 12] (16)
For more information, click http://www.microsoft.com/c
there are only 2 error msgs,
There are a load of warnings saying that the MTA service had not shut down proberly, cleaning the mta database, database cleaned, starting mta then those two errors and then this warning:
There is not enough Performance Monitor memory to display the MTA Connections information. Stop attached Performance Monitors and re-start the MTA. [BASE MAIN BASE 1] (14)
My last idea :(
XCON: Deleting the MTA from a Routing Group in Active Directory Can Result in MTA Not Starting
http://support.microsoft.c
If that isn't it, I hope someone else can help!
no didn't change anything
kidego:OWA will only work for 2003 users on 2003, and 5.5 OWA cannot contact a 2003 mailbox
i know that i have an administrator account on ex2003 but i cannot connect to owa on http://server/exchweb/bin/
that's a different issue. get on the console of the 2003 BE, and go to http://localhost/exchange
Is message tracking enabled on the 2003 server? If so, turn it off, and restart the 2003 Exchange services (just a test)
D
i just Realised there is 2 Internet Mail SMTP Connections In The Exchange 5.5 Administrator That Aren't Showing in System Manager,
These Connections belong to 2 Servers that were there previously from an old exchange 2003 Install, But I cannot delete them from exchange 5.5 because It gives me an invalid handle error, And they are not shown in the connections/routing groups of exchange 2003.
Is there anywhere where i can manually delete them.?
wait...on the Exchange 2003 server, you have no exchange virtual dirs under IIS, is that what you're telling me? And 2 orphaned connectors showing in the 5.5 admin, that belonged to 2 other Exchange 2003 servers previously installed?
Maybe you should give the full details of how we got to this spot, cause there's a lot going on that wasn't told in this thread.
D
Ok here we go.....
A while back we did a test install of exchange 2003, everything worked perfectly but the managers didn't like the configuration. So we uninstalled it. Now while we were uninstalling it one of the servers in atlanta was offline (unknown to us) and had the information of the 2003 connections in it. We fininshed uninstalling 2003 and ADC and everything was grand.
So we left it for a while to make sure everything was ok. Then we proceded to do our next text upgrade. But I noticed that there were the two orphaned connections due to the ofline Exchange 5.5 Server Replicating Back into The site, I thought Ex2003 would fix this during the ORGPREP part of the installation, but I guess I was wrong.
So now We have Installed -
In the NT 4 Domain:
6 x Exchange 5.5 Servers
In the Active Directory Domain:
2 x Back End Exchange 2003 Enterprise Servers (Windows 2003 Enterprise Server)(one has Active Directory Connector Installed)
1 x Front End Exchange 2003 Server (Windows Server 2003 Standard)
1 x Active Directory Domain Controller seperate to the one of the EX2003 Servers.
All of the user replication seems to be ok, I can move mailboxes etc,
but i moved my own mailbox today and I could log on etc but I could not send/recieve mails, neither from internal or external sources.
I followed it up by checking all of the MTA que's and noticed the The MTA Stack Service was not working on any of my ex2003 servers.
Now we are here,
Also just noticing that the IIS section is not working!
Should I just Uninstall and try again from scratch???
i started from scratch with a lot of help from kidego (thanks man! were live now!)
I completly rebuilt my domain and exchange systems, making sure to format them completly,
Also I checked every mailbox and made sure that each one had its own individual nt 4 account which matched the exchange 5.5 alias.
from then on everything went by the book.
Use the Exchange 2003 deployment and administration guide from microsoft.
they can be found here:
Deployment Guide:
http://www.microsoft.com/t
Admin Guide:
http://www.microsoft.com/t
thanks,
Matt
Workiing on our Front-End 2003 Exchange box after numerous hours with MS support...
Performing the various trouble shooting tasks such as:
1) Uninstall and reinstall "SMTP service" per KB840469
2) Uninstall and reinstall entire IIS service via Windows Component
3) Reinstal Exchange 2003 on the Front End
4) Apply Exchange SP2
the quick and simple fix for our circumstance, for starting the MS MTA Stacks service, was to create a dummy Mail Store within the First Administrative Group (on the Front-End server) called "Test"
Once this store was mounted (no mailboxes created), the MTA Service Stacks service was started, and stayed ON!
Business Accounts
Answer for Membership
by: mathesonPosted on 2004-01-20 at 07:12:02ID: 10155340
Increasing the points I am needing help and stuff