Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Journal report is not delivered to a journaling mailbox in an Exchange Server 2010 environment


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You create a journaling mailbox that is used for collecting journal reports in a Microsoft Exchange Server 2010 environment.
  • You create a journal rule to enable journaling for the email messages that are sent to a user’s mailbox. The rule sends journal reports to the journaling mailbox.
  • The user receives a read-only email message that is delivered by using Simple Mail Transfer Protocol (SMTP).
In this scenario, the journal report is not delivered to the journaling mailbox and remains in the Retry message queue on the Hub Transport server. Additionally, you receive the following error message in the Queue Viewer tool:
400 4.4.7 The server responded with: 554 5.2.0 STOREDRV.Deliver.Exception:PropertyErrorException; Failed to process message due to a permanent exception with message Property: [0x67480014] FID, PropertyErrorCode: AccessDenied, PropertyErrorDescription: . PropertyErrorException: Property: [0x67480014] FID, PropertyErrorCode: AccessDenied, PropertyErrorDescription: .. The failure was replaced by a retry response because the message was marked for retry if rejected.

↑ Back to the top


Cause

This issue occurs because the Exchange server throws an AccessDenied exception. This exception is thrown when the server tries to read an undefined property of the Transport Neutral Encapsulation Format (TNEF) attachment in the journal report. 

Note The original email message is encapsulated as a TNEF attachment in the journal report.

↑ Back to the top


Resolution

To resolve this issue, install the following update rollup:
2706690 Description of Update Rollup 4 for Exchange Server 2010 Service Pack 2

↑ Back to the top


Status

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

↑ Back to the top


More Information

For more information about journaling, go to the following Microsoft website:For more information about how to create a journal rule, go to the following Microsoft website:For more information about the transport journaling feature in Exchange Server 2007, go to the following Microsoft website:For more information about the PR_TNEF_CORRELATION_KEY property in the TNEF attachment, go to the following Microsoft website:

↑ Back to the top


Keywords: kbqfe, kbfix, kbsurveynew, kbexpertiseinter, kb

↑ Back to the top

Article Info
Article ID : 2686540
Revision : 1
Created on : 1/7/2017
Published on : 8/14/2012
Exists online : False
Views : 378