An RPC communications error occurred. No data was sent over the RPC connection. Locality table (LTAB) index: index name. Windows 2000 error: error code. The MTA will attempt to recover the RPC connection. [valuevaluevaluevalue] (12)

Details
Product: Exchange
Event ID: 9316
Source: MSExchangeMTA
Version: 6.5.0000.0
Message: An RPC communications error occurred. No data was sent over the RPC connection. Locality table (LTAB) index: index name. Windows 2000 error: error code. The MTA will attempt to recover the RPC connection. [valuevaluevaluevalue] (12)
   
Explanation
When a message is sent from one Microsoft Exchange Server system to another via RPC, the message might get stuck in the message transfer agent (MTA) queue.

There was a failure when the local MTA initiated an RPCSend call to the remote MTA.

   
User Action
At the Windows 2000 command prompt, use the Net Helpmsg command for an explanation of the Windows 2000 error. For example, if you want to get an explanation of Windows 2000 error code 3817, type “Net Helpmsg 3817” at the command prompt, and then press Enter.

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.

The most common error codes are listed with possible resolutions:

  • 5 – access denied – check the permissions and account being used by the service.
  • 1722 – this problem is usually DNS. Use nslookup to verify that you can resolve the host by fully qualified domain name (FQDN).
  • 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.

If necessary, use Network Monitor to capture network traces, then view these traces from Network Monitor for any network issue.

Related:

Leave a Reply