There was a failure when the local MTA initiated an RPC Send call to the remote MTA. It could be that when a message was sent from one Microsoft Exchange Server system to another via RPC, the message got stuck in the message transfer agent (MTA) queue.
Verify that the remote procedure call (RPC) service is running. Check network connectivity. If the error persists, stop and restart the message transfer agent service. If the error still persists, restart Microsoft Exchange Server. If necessary, use Network Monitor to capture network traces, then view these traces from Network Monitor for any network issue.
Error: 5 - access denied - A failure with the credentials provided at the time the MTA attempts to bind: check the permissions and account being used by the service. This issue can occur if there is a problem with the Exchange Server 5.5 service account or password that was specified when the Exchange 2000 server was installed in the Exchange Server 5.5 site and signifies that there is a security problem between the two servers. See ME217142
Error code 14
: This issue can occur if your computer does not have enough available Random Access Memory (RAM). See ME275468
Error code 1722
: "Similar to Event ID 9318 Source MSExchangeMTA Type Warning. Occurs when Exchange server is unable to locate another Exchange server on the network. I have received both 9318 and 9322 when one of the servers is offline or when using dual-homed Exchange servers and Netbios over TCP/IP. Problem on dual-homed exchange servers resolved by adding specific interfaces to be used by each server to each Exchange server''s HOST and LMHOST file." See ME266312
. Sometimes this is caused by improperly configured DNS. Use nslookup to verify that you can resolve the host by fully qualified domain name (FQDN).
Error 1726: The remote procedure call failed. RPC_S_CALL_FAILED
Error 1753: This problem is also usually DNS, but on the bind back. Verify that the host reporting this problem is able to resolve the remote host by FQDN.
Error 1783: "Bad Stub Data" - This Problem occurs when the number of messages in the outbound DRAS connector's Queue exceeds the DRAS connector's configured threshold. By default, the Threshold value is set to 50. When the queue exceeds this threshold, an Additional association is generated. However, the sending MTA passes an Invalid context handle to the receiving MTA, which terminates the Connection because the handle is invalid.
Error 1818 = The remote procedure call was cancelled. RPC_S_CALL_CANCELLED
Error 9260: "This may be because the Exchange Server computer's connection to the network infrastructure has changed". See ME225206
Error 20437 – no info
Error 20594 – no info
Error: 27516 - no info
Error 34375 – no info
See also the "MTA Troubleshooting Guide" link.