Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 1209 Source: MSExchangeMTA
Unable to recognize an internal message identifier (LPI) from entity x.500 name. The incorrect LPI is %1 - % 2 - %3. Control block index %4.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the Exchange MTA Service?
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 ME225206 and ME232602 for additional information about this event.
As per MSEX2K3DB, the OSI stack encountered an unexpected condition during communication with the transport layer. This usually indicates that a timing window closed during a connection.
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: ME152901, ME225206, ME232602, ME306959, MSEX2K3DB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated