Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

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.
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.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.