Event Id | 9224 |
Source | MSExchangeMTA |
Description | A sockets error <error code> on a send() call was detected. The MTA will attempt to recover the sockets connection. Control block index: <index name>. [<value> <value> <value> <value>] (12) |
Event Information | According to Microsoft: CAUSE: These problems are due to heap corruption when two or more threads in the MTA try to access the same data structures without proper synchronization. This problem has been particularly noted in networks in which there are a large number of associations being opened and closed between MTAs. Frequently, these MTA failures are associated with slow and unreliable links. For example, an ICMP Ping might return only one out of eight ping attempts. WORKAROUND: The problem only happens when there is insufficient bandwidth or a high number of network errors. One workaround is increase the bandwidth available to the MTA. |
Reference Links | XCON: MTA X.400 Connector Problems on Slow Links XCON: MTA Crashes Over Slow or Sporadic Network Connection Exchange (MSExchangeMTA) |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.