When a message is sent from one Microsoft Exchange Server system to another via RPC, the message could 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.
At the command prompt, use the Net Helpmsg command for an explanation of the Windows error. For example, to get an explanation of Windows 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 (MTA) 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.
For more information about MSExchangeMTA event 9316, see:
Target | Microsoft.Exchange.Routing.MTA | ||
Category | EventCollection | ||
Enabled | True | ||
Event_ID | 9316 | ||
Event Source | MSExchangeMTA | ||
Alert Generate | True | ||
Alert Severity | Warning | ||
Alert Priority | Normal | ||
Remotable | True | ||
Alert Message |
| ||
Event Log | Application |
ID | Module Type | TypeId | RunAs |
---|---|---|---|
EventDS | DataSource | Microsoft.Windows.EventProvider | Default |
GenerateAlert | WriteAction | System.Health.GenerateAlert | Default |
<Rule ID="A_remote_procedure_call__RPC__communications_error_occurred__No_data_was_sent_over_the_RPC_connection" Enabled="onEssentialMonitoring" Target="Exch2003Core!Microsoft.Exchange.Routing.MTA" ConfirmDelivery="false" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>EventCollection</Category>
<DataSources>
<DataSource ID="EventDS" TypeID="Windows!Microsoft.Windows.EventProvider">
<ComputerName>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<LogName>Application</LogName>
<Expression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>Channel</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>Application</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>MSExchangeMTA</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>9316</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</Expression>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="GenerateAlert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>1</Severity>
<AlertOwner>$Data/PublisherName$</AlertOwner>
<AlertMessageId>$MPElement[Name="A_remote_procedure_call__RPC__communications_error_occurred__No_data_was_sent_over_the_RPC_connection.AlertMessage"]$</AlertMessageId>
<AlertParameters>
<AlertParameter1>$Data/EventDescription$</AlertParameter1>
</AlertParameters>
<Suppression>
<SuppressionValue/>
</Suppression>
</WriteAction>
</WriteActions>
</Rule>