"554 5.6.0" NDR when you try to send messages that have attachments in an Exchange Server 2007 environment

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

Symptoms

Assume that you try to send a message that has an attachment to a distribution list in a Microsoft Exchange Server 2007 environment. However, the message is not delivered, and you receive a non-delivery report (NDR) that contains the following information:
#554 5.6.0 STOREDRV.Deliver; Corrupt message content ##
Additionally, if content conversion tracing is enabled, the following information is recorded in a content conversion tracing file:
Microsoft.Exchange.Data.Storage.ConversionFailedException: Content conversion: Corrupt summary tnef content.
at Microsoft.Exchange.Data.Storage.InboundMimeConverter.GetMimeMessageClass()
at Microsoft.Exchange.Data.Storage.InboundMimeConverter.ConvertToItemInternal(MimePromotionFlags promotionFlags)
at Microsoft.Exchange.Data.Storage.InboundMimeConverter.<>c__DisplayClasse.<ConvertToItem>b__c()
at Microsoft.Exchange.Data.Storage.ConvertUtils.CallCts(Trace tracer, String methodName, String exceptionString, CtsCall ctsCall)
at Microsoft.Exchange.Data.Storage.InboundMimeConverter.ConvertToItem(MimePromotionFlags promotionFlags)
at Microsoft.Exchange.Data.Storage.ItemConversion.InternalConvertAnyMimeToItem(Item itemOut, EmailMessage messageIn, InboundConversionOptions options, MimePromotionFlags promotionFlags, Boolean isStreamToStream)
at Microsoft.Exchange.Data.Storage.ItemConversion.ConvertAnyMimeToItem(Item itemOut, EmailMessage messageIn, InboundConversionOptions options, MimePromotionFlags flags)
InboundConversionOptions:
- preferredCharset: Charset
- trustAsciiCharsets: True
- isSenderTrusted: False
- imceaResolveableDomain: Domain 
- preserveReportBody: False
- clearCategories: True
- userADSession:
- recipientCache: Microsoft.Exchange.Data.Directory.Recipient.ADRecipientCache
- clientSubmittedSecurely: False
- serverSubmittedSecurely: False
- disableNewXHeaderMapping: True
- convertReportToMessage: False
- treatInlineDispositionAsAttachment: False
- preferredInternetCodePageForShiftJis: Code page 
- combineMixedContentBodies: True
ConversionLimits:
- maxMimeTextHeaderLength: Length 
- maxMimeSubjectLength: Length 
- maxSize: Size 
- maxMimeRecipients: Number 
- maxRecipientPropertyLength: Length 
- maxBodyPartsTotal: Number 
- maxEmbeddedMessageDepth: Number
- exemptPFReplicationMessages: True


Cause

This issue occurs because of a race condition when Exchange server submits messages. The race condition occurs when different threads process a message at the same time. Therefore, the categorizer treats the message as corrupted and blocks the message submission.

Resolution

To resolve this issue, install the following update rollup:
2655203 Description of Update Rollup 7 for Exchange Server 2007 Service Pack 3

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 how to manage content conversion tracing, visit the following Microsoft website:
How to manage content conversion tracing

Properties

Article ID: 2694566 - Last Review: March 1, 2013 - Revision: 2.0
Applies to
  • Microsoft Exchange Server 2007 Service Pack 3, when used with:
    • Microsoft Exchange Server 2007 Enterprise Edition
    • Microsoft Exchange Server 2007 Standard Edition
Keywords: 
kbqfe kbfix kbexpertiseinter kbsurveynew KB2694566

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