Consider the following scenario:
- You enable journaling in a Microsoft Exchange Server 2010 environment.
- An email message is sent to a journal recipient, and then a journal report is generated on a Microsoft Exchange Server 2010 Hub Transport server.
- The Hub Transport server does not successfully deliver the journal report.
- The journal recipient receives a non-delivery report (NDR) message for the journal report.
In this scenario, the Edgetransport.exe process crashes on the Hub Transport server. Additionally, the following event is logged in the Application log if the Windows Error Reporting tool is enabled:
Log Name: Application
Source: Windows Error Reporting
Date: Date
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Computer
Description:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: edgetransport.exe
P2: 14.16.123.0
P3: 4f1d1445
P4: KERNELBASE.dll
P5: 6.1.7601.17651
P6: 4e21213c
P7: e053534f
P8: 000000000000cacd
P9:
P10:
This issue occurs because the NDR message for the journal report causes an infinite loop of journaling. Therefore, a stack overflow occurs that causes the Edgetransport.exe process to crash.
To resolve this issue, install the following update rollup:
2746164
(http://support.microsoft.com/kb/2746164/
)
Description of Update Rollup 6 for Exchange Server 2010 Service Pack 2
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 2783772 - Last Review: Tuesday, 12 February 2013 - Revision: 1.0
Applies to
- Microsoft Exchange Server 2010 Service Pack 2, when used with:
- Microsoft Exchange Server 2010 Enterprise
- Microsoft Exchange Server 2010 Standard
| kbqfe kbfix kbexpertiseinter kbsurveynew KB2783772 |
