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

Exchange 5.5 - MTA fills up application log - Filed Engineering Event ID's 3267,3200,3279,9159 etc...

Unexpectedly, our event log is filling up rapidly with MSExchangeMTA events with various categories ranging from Interface, Operating System and Field Engineering. Diagnostic logging is not enabled for the MTA.  Exchange server is working well and messages seem to be going in and out as expected, just a bit slower.  

Below is a standard series of entries:
 
Event ID 3280 - Source: MSExchangeMTA  Type: Information  Category: Interface
====================================================
A MA_WAIT message was sent to the /o=Parr + Associates Management Services/ou=PARRASSOC/cn=Configuration/cn=Servers/cn=PASRV1/cn=Microsoft Public MDB application on session index 7. [XAPI APPLICATION 37 138] (8)

Event ID 9159 - Source: MSExchangeMTA  Type: Information  Category: Operating System
====================================================
(BASE IL INCOMING RPC(37) Proc 0)           Thread exiting, type = 6 (see SBCDERR.H) (4)

Event ID 3268- Source: MSExchangeMTA  Type: Information  Category: Interface
=====================================================
A MA_WAIT message was received from the /o=Parr + Associates Management Services/ou=PARRASSOC/cn=Configuration/cn=Servers/cn=PASRV1/cn=Microsoft Public MDB application on session index 7. [XAPI APPLICATION 37 100] (8)

Event ID 3200- Source: MSExchangeMTA  Type: Information  Category: Field Engineering
=====================================================
A timer started with the timeout value set to 10. [XAPI APPLICATION 37 138] (6)



These entries fill up the log files rapidly and seem to repeat themselves ever 10 seconds.

Any help would be appreciated.  Thank you.
0
deros_32
Asked:
deros_32
1 Solution
 
David WilhoitSenior Consultant, ExchangeCommented:
Did you tune any parameters on the MTA? something had to change....tried restarting the mta?
0
 
eatmeimadanishCommented:
Do you have multiple exchange servers?
0
 
deros_32Author Commented:
found the solution myself - logging WAS turned on for the MTA at the server level - right click the server and select properties, then diagnostic loging and selected MTA and changed it from level high to medium and it stopped filling up the event log files with the above messages.

This whole time I was looking in the wrong place - in the connections> internet mail > diagnostic logging. Had no idea/never thought that you could enable diagnostics at the server level...thought it was all done at the connection level.

Thanks for trying to assist me anyway....
0
 
CetusMODCommented:
PAQed with points refunded (500)

CetusMOD
Community Support Moderator
0
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