Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 9202 Source: MSExchangeMTA
A sockets error 0 on an accept() call was detected. The MTA will attempt to recover the sockets connection. Control block index: 1. [BASE IL TCP/IP DRVR 8 256] (12)
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the Exchange MTA Service?
As per Microsoft: "This event can occur when there is insufficient bandwidth or there are many network errors. It could be due to heap corruption when two or more threads in the message transfer agent (MTA) try to access the same data structures without proper synchronization". See MSEX2KDB for additional information about this event.
This event indicates a problem with the connectivity over X400 connections. This could be due to network or name resolution problems. See ME193380, ME197378, ME254909 and ME300445 for some of the conditions that may trigger this event. Sometimes this event can occur due to misconfiguation of the remote server. ME276222 describes an occurrence of this event due to a bug in the ExchangeMTA - a fix is available from Microsoft.
|Private comment: Subscribers only. See example of private comment|
|Links: ME193380, ME197378, ME254909, ME276222, ME300445, MSEX2KDB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated