Microsoft KB Archive/154301

Knowledge Base

XCON: MTA X.400 Connector Problems on Slow Links

Article ID: 154301

Article Last Modified on 10/28/2006

---

APPLIES TO

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

---

This article was previously published under Q154301

SYMPTOMS

When an X.400 connector is used over a slow link, a number of different problems can occur. In some cases the message transfer agent (MTA) stops responding and a DRWATSON log is generated with exception e0020002 or Access Violation c0000005. One Application Event Log error is:

MTA error (Event ID = 9405):
An unexpected error has occurred which may cause the MTA to terminate.
Error: SBPDSCLS:CB TID=1,calling TID=0. [BASE TCP/IP DRVR 10] (16)

Other symptoms include the following socket errors:

A sockets error 10060
(WSAETIMEDOUT) event ID 9215, A sockets error 10051 (WSAENETUNREACH) event ID 9215, A sockets error 10054 (WSAECONNRESET) event ID 9224.

WORKAROUND

The problem only happens when there is insufficient bandwidth or a high number of network errors. One workaround is increase the bandwidth available to the MTA.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 4.0. This problem was corrected in the latest Microsoft Exchange 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: RPC X.25 ISDN

Keywords: kbusage KB154301

---

Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.