| Event Id | 2026 |
| Source | MSExchangeMTA |
| Description | An internal MTA error occurred. Contact Microsoft Technical Support. Unable to write to the message tracking log, error <error code>. [<value> <value> <value> <value>] (16) |
| Event Information | According to Microsoft: CAUSE: This problem can occur when the system attendant writes to the message tracking log (located in the Tracking.log folder under Exchsrvr). When the message transfer agent (MTA), Internet Mail Service, or other service sends these messages to the system attendant, the system attendant holds the messages in a buffer and only writes to the log if a number of messages that is specified in the registry (the LogFlushFreq registry value) is reached. The system attendant spends less time waiting for disk input/output to finish if you increase this buffer, which reduces or eliminates the 2026 and 3016 event IDs. RESOLUTION: To resolve this problem, increase this buffer by changing the LogFlushFreq registry value: 1. Start Registry Editor (Regedt32.exe). 2. Locate the LogFlushFreq value under the following key in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MsExchangeSA\Parameters 3. On the Edit menu, click DWORD, type 100, and then click OK. 4. Quit Registry Editor. Stop and restart all of the Exchange Server services so that this change takes effect. |
| Reference Links | XCON: 2026 and 3016 Warnings During Periods of High Server Use XCON: MTA 2026 and Internet Mail Service 3016 Logging Error Messages During Periods of High Server Use When Message Tracking Is Enabled |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.