Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 4287 Source: MSExchangeMTA
An internal MTA occurred. Contact Microsoft Product Support Services. Error code=8650 [POP4 POP4 DOWN4 18] (14)
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
Who are Microsoft Product Support Services and how to contact them?
What is the role of the Exchange MTA Service?
As per Microsoft: "If your Exchange Server computer encounters a network disconnection or disruption while there are messages queued in the MTA for delivery, the MTA may fail to properly recover active associations". See ME232602 for details on this event.
See ME254818 and MSEX2K3DB for additional information about this event.
As per Microsoft: "These errors may be caused by network problems, such as a WAN connection being temporarily down. This does not necessarily indicate a problem with Exchange Server or the Message Transfer Agent (MTA)". See ME175354 and ME152897 for more details.
When two Exchange Server computers are connected with an X.400 Connector, mail may queue up in both X.400 queues and not flow in either direction. The error occurs if the message transfer agent (MTA) becomes backed up while it is trying to deliver messages, and the transport connection is lost.
According to Microsoft: "This behavior can occur if you use Fully Qualified Domain Names (FQDN) or NetBIOS names to configure the connectors. To resolve this behavior, on both Exchange servers, configure the X.400 Connector to use the IP address of the remote MTA, and then restart both MTAs." See ME306959.
|Private comment: Subscribers only. See example of private comment|
|Links: ME152897, ME175354, ME232602, ME236586, ME254818, ME306959, MSEX2K3DB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated