Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 2026 Source: MSExchangeMTA
An internal MTA error occurred. Contact Microsoft Technical Support. Unable to write to the message tracking log, error ''. [BASE XFER-IN 19 136] (16)
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the Exchange MTA Service?
How is message tracking enabled in Exchange 2000 server?
Event ID 5007 indicates that the current message tracking log file was locked by another process. The System Attendant must be able to write to the current message tracking log file that is found in the Exchsrvr\Tracking.log file. The Event ID 3016 from the Internet Mail Service is logged because the Internet Mail Service is dependent on the System Attendant to actually write to the message tracking log file. The same is true for this event. See ME198733 for details on this issue.
As per Microsoft: "The Microsoft Exchange Server disk could be full or a disk error could have occurred. The message transfer agent (MTA) service will stop if the disk is full". See MSEX2K3DB and the link to "EventID 3016 from source MSExchangeIMC" for additional information on this event.
See ME257348 and ME266383 below.
|Private comment: Subscribers only. See example of private comment|
|Links: ME198733, ME257348, ME266383, EventID 3016 from source MSExchangeIMC, MSEX2K3DB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated