• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 225
  • Last Modified:

Exchange 2000 MTA won't start. Do I care? (Someone else asked this question too!)

I have an Exchange 2000 server, it is a stand alone server it does not connect to other Exchange servers and it especially does not connect to an Exchange 5.5 server although at one time it did.
I am getting a warning message in my application log with an Event ID of 2000. The description is "Verify that the Microsoft MTA service has started. Consecutive ma-open calls are failing with error 3051".
I do have the Microsoft Exchange MTA service disabled because I did not believe I needed it after I removed the Exchange 5.5 server from our network and because I could not start the service after I removed the Exchange 5.5 server from our network. So my question is can I just leave it off and if so how do I get rid of the warning messages in the log i.e. how do I get Exchange to stop sending ma-open calls.

1 Solution
I'd go ahead and turn it on.  The MTA still has some hooks in Exchange 2000 even in native mode (move mailbox wizard for example needs the MTA).  Plus, you're just going to fill your event log with those warnings if you leave it off.
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.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Tackle projects and never again get stuck behind a technical roadblock.
Join Now