| Event Id | 170 |
| Source | MSExchangeMTA |
| Description | The message <message id> contained too much internal trace information. The message was not delivered with reason code <error code> and diagnostic code <error code>. [<value> <value> <value> <value>] (14) |
| Event Information | According To Microsoft: Cause: The message transfer agent (MTA) determined that this message reached the X.400 limit for hop count and reroute attempts.Microsoft Exchange Server Application Protocol Data Unit (APDU) logs are binary representations of communication among MTAs in different sites, and between MTA and client applications within a site. These text logs are stored in the \Exchsrvr\Mtadata directory. The current log is always named Bf0.log. Prior logs are named Bfx.log, where x increases as the age of the log increases. Resolution: Use network Monitor to capture Network Traces, then view these traces from Network Monitor for any network issue. Verify that the routing is configured correctly and that there are no communication failures. To help Microsoft Product Support Services track the problem, create APDU and text event log files. For more information, see Knowledge Base article Q163032.On the Diagnostics Logging tab of the Server Properties dialog box, select MSExchangeMTA, and then enable the APDU logs by setting the logging levels of the X.400 Service and APDU categories to Medium or greater.You can enable text event log files (Ev*.log) by modifying the registry. Contact Microsoft Product Support Services for assistance. |
| Reference Links | Microsoft product: Exchange Version: 6.0 Event Source: MSExchangeMTA Event ID: 170 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.