Journal reports are expired or lost when the Microsoft Exchange Transport service is restarted in an Exchange Server 2010 environment

Article translations Article translations
Article ID: 2509306 - View products that this article applies to.
Expand all | Collapse all

SYMPTOMS

Consider the following scenario:
  • You configure the message expiration time-out interval on a Microsoft Exchange Server 2010 server.
  • Journal reports are queued past the message expiration time-out interval.
  • The Microsoft Exchange Transport service is restarted.
In this scenario, the journal reports are expired or lost.

CAUSE

This issue occurs because the MustDeliver flag is not set for the journal reports after the Microsoft Exchange Transport service is restarted. 

RESOLUTION

To resolve this issue, install the following update rollup:
2582113 Description of Update Rollup 5 for Exchange Server 2010 Service Pack 1

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about journaling, visit the following Microsoft website:
General information about journaling
For more information about transport queues, visit the following Microsoft website:
General information about transport queues
For more information about how to configure message expiration time-out interval, visit the following Microsoft website:
How to configure message expiration time-out interval

Properties

Article ID: 2509306 - Last Review: August 24, 2011 - Revision: 1.0
APPLIES TO
  • Microsoft Exchange Server 2010 Service Pack 1, when used with:
    • Microsoft Exchange Server 2010 Enterprise
    • Microsoft Exchange Server 2010 Standard
Keywords: 
kbqfe kbfix kbhotfixrollup kbexpertiseinter kbsurveynew KB2509306

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com