XCON: MTA X.400 Connector Problems on Slow Links

Last reviewed: April 15, 1997
Article ID: Q154301

The information in this article applies to:

Microsoft Exchange, versions 4.0 and 4.0a

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 : kbbug4.00 kbfix4.00.sp3 kbusage XCON
Version : 4.0
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 15, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.