Microsoft KB Archive/306959

From BetaArchive Wiki
Knowledge Base


XCON: Mail Not Flowing Through X.400 Connectors and Events 4282, 4283, 4284, 4287, 1209, and 1198 Occur

Article ID: 306959

Article Last Modified on 10/28/2006



APPLIES TO

  • Microsoft Exchange Server 4.0 Standard Edition
  • Microsoft Exchange Server 5.0 Standard Edition
  • Microsoft Exchange Server 5.5 Standard Edition



This article was previously published under Q306959

SYMPTOMS

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. If the message transfer agent (MTA) becomes backed up while it is trying to deliver messages, and the transport connection is lost, the following error messages may appear in the Windows NT Event Viewer Application log:

Event ID: 4282
Source: MSExchangeMTA
Category: X.400 Service
Description: An interoperability error occurred. Interface protocol 131 was violated. Error code=8453 [POP4 MAIN BASE 1 18] (14)

Event ID: 4283
Source: MSExchangeMTA
Category: X.400 Service
Description: Unable to recognize an internal message identifier. Internal connection handle (LP1) 1-3-14 Error code=8464 [POP4 POP4 UP 5 228] (14)

Event ID: 4284
Category: X.400 Service Source: MSExchangeMTA
Description: An error has occurred during connection/disconnection. Error code=8511 [POP4 POP4 DOWN 4 179] (14)

Event ID: 4287
Category: X.400 Service
Source: MSExchangeMTA
Description: An internal MTA occurred. Contact Microsoft Product Support Services. Error code=8650 [POP4 POP4 DOWN4 18] (14)

Event ID: 1209
Category: X.400 Service
Source: MSExchangeMTA
Description: Unable to recognize an internal message identifier (LPI) from entity x.500 name. The incorrect LPI is %1 - % 2 - %3. Control block index %4.

Event ID: 1198
Category: X.400 Service
Source: MSExchangeMTA
Description: An error occurred while processing an association to entity. Presentation error: state check failure. Current state 0, service type 20, service flavor 2 Control block index 3. The association will be terminated and restarted if necessary. [PLATFORM KERNEL 27 108] (14)

CAUSE

This behavior can occur if you use Fully Qualified Domain Names (FQDN) or NetBIOS names to configure the connectors.

For additional information about why this behavior can occur, click the article number below to view the article in the Microsoft Knowledge Base:

193380 XCON: Mail Does Not Flow over X.400 Connector; Event 9301


RESOLUTION

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.

Keywords: kbprb KB306959