| Event Id | 141 |
| Source | MSExchangeMTA |
| Description | The MTA is unable to route a report for message C=US;A= ;P=Company;L=OrginateServer-020208210308Z-521102 to recipient DN:CN=Alias,CN=Name,OU=Site,O=Company -- C=US;A= ;P=Company;O=Site;S=SurName;G=GivenName;. MTA object at fault: 060009B3. Check the routing table for a possible incorrect routing configuration. (MTA DISP:ROUTER 16 40) (12) |
| Event Information | According to Microsoft: CAUSE: This problem typically occurs on the bridgehead servers. Also, if you monitor the Private Bytes counter of the MTA process, the counter shows a memory leak, and memory use by the MTA process is very high (sometimes up to 2 gigabytes [GB]). RESOLUTION: To resolve this problem, obtain the March 2003 Exchange 2000 Server Post-Service Pack 3 (SP3) Rollup. A supported fix is now available from Microsoft, but it is only intended to correct the problem. Apply it only to computers that are experiencing this specific problem. Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. |
| Reference Links | XCON: The Message Transfer Agent Generates Non-Delivery Reports for Messages Because of Too Many Link State Changes XCON: NDRs Can Be Lost if a More Restrictive Size Limit is Set on Remote MTA XCON: MTA Process Can Leak Memory Because of Excessive Rerouting Microsoft product: Exchange Version: 6.5.6940.0 Event Source: MSExchangeMTA Event ID: 141 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.