XADM: POP-4 State Checks (4282, 4283, 4284, 4287)Last reviewed: April 21, 1997Article ID: Q152897 |
The information in this article applies to:
SYMPTOMSThe following errors will be logged in the Windows NT Event Viewer Application Log if the Microsoft Exchange Message Transfer Agent (MTA) gets backed up trying to deliver messages and the transport connection is lost. These errors will be from the MSExchangeMTA service.
ID 4282 Category X.400 Service An interoperability error occurred. Interface protocol 131 was violated. Error code=8453 [POP4 MAIN BASE 1 18] (14) ID 4283 Category X.400 Service Unable to recognize an internal message identifier. Internal connection handle (LP1) 1-3-14 Error code=8464 [POP4 POP4 UP 5 228] (14) ID 4284 Category X.400 Service An error has occurred during connection/disconnection. Error code=8511 [POP4 POP4 DOWN 4 179] (14) ID 4287 Category X.400 Service An internal MTA occurred. Contact Microsoft Product Support Services. Error code=8650 [POP4 POP4 DOWN4 18] (14) MORE INFORMATIONWhen a message enters the MTA queue, it is assigned a unique identifier (MTSID in the message details in the MTA queue) by the MTA. When the message leaves the queue, the identifier is stripped and it might be re- used for another message that enters the queue. With Microsoft Exchange Server version 4.0, there is an issue where multiple messages might be assigned the same MTSID number. This ID collision will then cause the transport session to shut down. This causes messages to hang in the queue until one of the messages with the duplicate ID leaves the queue.
STATUSMicrosoft has confirmed this to be a problem in Microsoft Exchange Server version 4.0. This problem was corrected in the latest Microsoft Exchange Server U.S. Service Pack. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K |
Additional query words: tcp x.25 tp4 warnings pop-4
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |