Messages not Being Delivered Over an Association

Article translations Article translations
Article ID: 181721 - View products that this article applies to.
This article was previously published under Q181721
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

SYMPTOMS

The Microsoft Exchange message transfer agent (MTA) has a backlog of messages (up to the default threshold) waiting to be delivered. The MTA makes an association with another LAN-MTA (RPC connection), but does not deliver mail over this connection.

Various errors may appear in the applications event log concerning RPC problems. These may include the following events and other similar errors that indicate RPC problems:

Event id = 9316
Category = Interface
Source = MSExchangeMTA
An RPC communications error occurred. No data was sent over the RPC connection. Locality table (LTAB) index: 53. Windows NT error: 1727. The MTA will attempt to recover the RPC connection. [BASE IL KERNEL 24 512] (12)

Event id = 9277
Category = Interface
Source = MSExchangeMTA
The MTA has issued an RPC Cancel call for thread 1, Locality Table Index: 160, Time (ms): 1275740, Cancel result: 0 [SLPS100 MtaBind ncacn_ip_tcp:100.5.51.16[1911] BASE IL] (14)

CAUSE

The Windows NT RPC component on the receiving computer puts the association in the wrong address space. Therefore, when the next bind arrives on the correct address, it cannot find the association and sends a Bind NAK.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

STATUS

Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.

MORE INFORMATION

The initiating MTA tries to send mail to the receiving MTA, but the receiving MTA does not believe it has an association with it because the RPC put the association in the wrong address. It will NAK the RPC Bind request.

After the message threshold has been reached (default value is 50) on one of the MTAs, it will make a new association and begin delivering messages again.

Properties

Article ID: 181721 - Last Review: October 7, 2013 - Revision: 3.2
APPLIES TO
  • Microsoft Windows NT Server 4.0, Terminal Server Edition
  • Microsoft Exchange Server 4.0 Standard Edition
  • Microsoft Exchange Server 5.0 Standard Edition
  • Microsoft Exchange Server 5.5 Standard Edition
  • Microsoft Windows NT Server 4.0 Standard Edition
Keywords: 
kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix kbqfe KB181721

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com